Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Current »


Standards

Please read pre-requisite from ONAP Logging Standards 

MDCGroupDescription

Applicable

(per log file)

Marker Associations

Required?

Y/N/C

(C= context dependent)

N = not required


Use Cases

Code References

RequestID


UUID to track the processing of each client request across all the ONAP components involved in its processing



Y

InvocationID

UUID correlates log entries relating to a single invocation of a single component



Y

InstanceUUID

UUID to differentiate between multiple instances of the same (named) log writing service/application



Y

ServiceName

The service inside the partner doing the call - includes API name



Y

PartnerName

The URI that the caller used to make the call to the component that is logging the message.



Y

StatusCode

This field indicates the high level status of the request - one of (COMPLETE, ERROR)




Y

ResponseCode
This field contains application-specific error codes.

Y



ResponseDescription
This field contains a human readable description of the ResponseCode

Y



Severity

Logging level by default aligned with the reported log level - one of INFO/TRACE/DEBUG/WARN/ERROR/FATAL



Y

ServerFQDN

The VM FQDN if the server is virtualized. Otherwise the host name of the logging component.



Y



ClientIPAddress

This field contains the requesting remote client application’s IP address if known. Otherwise empty.



Y



EntryTimestamp


UTC Date-time that processing activities being logged begins - if part of an ENTRY marker



C

InvokeTimestamp


Timestamp on invocation start - if part of an INVOKE marker



C

TargetEntity

The name of the ONAP component or sub-component, or external entity, at which the operation activities captured in this metrics log record is invoked.



C

TargetServiceName

The name  of the API or operation activities invoked (name on the remote/target application) at the TargetEntity.  



C

TargetElement

VNF/PNF context dependent - on CRUD operations of VNF/PNFs

The IDs that need to be covered with the above Attributes are

       -        VNF_ID OR VNFC_ID : (Unique identifier for a VNF asset that is being instantiated or that would generate an alarms)

       -        VSERVER_ID OR VM_ID (or vmid): (Unique identified for a virtual server or virtual machine on which a Control Loop action is usually taken on, or that is installed  as part of instantiation flow)

       -        PNF : (What is the Unique identifier used within ONAP)



C
SolutionID



C

ActiveYN





C

ToolkitTypeCD





C
UserID



C
DownloadID



C

DeploymentID





C

DepStatusCD





C
Status



C
State



C

AccessTypeCD





C
UserName



C
ModelName



C
Message



C

Specification

Links

ONAP Casablanca release logging specification is the common log spec for MDC's and Markers between ONAP and Acumos - except for extensions on this Acumos project.

ONAP/Acumos Logging specification collaboration epic - https://jira.onap.org/browse/LOG-416

ONAP/Acumos Logging weekly meeting (last 30 of 1130 EDT GMT-4) - https://lists.onap.org/pipermail/onap-discuss/2018-June/010156.html

  • No labels