Versions Compared

Old Version 111

changes.mady.by.user Michael O'Brien

Saved on

compared with

New Version 112

changes.mady.by.user Michael O'Brien

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Align ONAP c v111 with Acumos v30 athena release - any logback.xml field changes go into the dublin spec as code freeze is 20180920

...

ThreadLevelCLoggerCMdcMarkerC
Pipe OrderNameTypeGroupDescription

Applicable

(per log file)

Marker Associations

Moved

MDC

to


standard

attribute


Removed

(was in

older

spec)

Required?

Y/N/C

(C= context dependent)

N = not required

L=Library provided


DerivedAcumos
ref		Use Cases

Code References

1LogTimestamplog system
use %d field - see %d{"yyyy-MM-dd'T'HH:mm:ss.SSSXXX",UTC}



L



2EntryTimestampMDC
if part of an ENTRY marker log



C



3InvokeTimestampMDC
if part of an INVOKE marker log



C



4

RequestID

MDC

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





Y


In general

https://git.onap.org/logging-analytics/tree/reference/logging-slf4j-demo/src/test/java/org/onap/logging/ref/slf4j/demo/component/AbstractComponentTest.java

5InvocationIDMDC

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





Y



6InstanceUUIDMDC

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





Y



7ServiceInstanceIDMDC





C



8threadlog system
use %thread field



L



9ServiceName

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





Y



10PartnerName

unauthenticated = The part of the URI specifying the agent that the caller used to make the call to the component that is logging the message.

authenticated = userid





Y
user

11StatusCode

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






Y


20180807: expand from 2 fields to add "INPROGRESS"

addresses Chris Lott question on https://wiki.acumos.org/display/OAM/Log+Standards

12ResponseCode

This field contains application-specific error codes.



Y





13ResponseDesResponseDesc

This field contains a human readable description of the ResponseCode



Y





14level

%level



L



15Severity

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





Y
level (but numbers)

16ServerIPAddress






C



17ElapsedTime






C



18ServerFQDN

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





Y





19ClientIPAddress

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





Y





20VirtualServerName






C



21ContextName






C



22TargetEntity

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



23TargetServiceName

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





C



24TargetElement

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



25UserMDC
User - used for %X{user}  



C



26p_loggerlog system
The name of the class doing the logging (in my case the ApplicationController – close to the targetservicename but at the class granular level - this field is %logger



L



27p_mdclog system%mdcC

allows forward compatability with ELK indexers that read all MDCs in a single field - while maintaining separate MDCs above.


The key/value pairs all in one pipe field (will have some duplications currently with MDC’s that are in their own pipe – but allows us to expand the MDC list – replaces customvalue1-3 older fields - this field is %mdc





L



28p_messagelog system
The marker labels INVOKE, ENTRY, EXIT – and later will also include DEBUG, AUDIT, METRICS, ERROR when we go to 1 log file - this field is %marker



L




28Messagelog system%msgC29RootExceptionlog system
%rootException - Dublin spec only



CL30



29p_markerlog system%marker
The marker labels INVOKE, ENTRY, EXIT – and later will also include DEBUG, AUDIT, METRICS, ERROR when we go to 1 log file - this field is %marker



L




Logging

Via SLF4J:

Code Block
languagejava
linenumberstrue
import java.util.UUID;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.slf4j.MDC;
// ...
final Logger logger = LoggerFactory.getLogger(this.getClass());
MDC.put("SomeUUID", UUID.randomUUID().toString());
try {
    logger.info("This message will have a UUID-valued 'SomeUUID' MDC attached.");
    // ...
}
finally {
    MDC.clear();
}

...