Skip to end of metadata
Go to start of metadata

Platform application logging

All application and microservices that follow the ECOMP Platform application logging guidelines have the following common types, location, and syntax. Each message includes a unique ID to capture the flow of requests across OpenECOMP components and enable the tracing, understanding, and troubleshooting of performance across the ECOMP platform.

The ONAP Application Logging Guidelines v1.1 page is the official source for logging details.

Log types


Audit

Captures the high-level activities carried out by OpenECOMP components as a result of incoming requests, including API requests, job executions, and messages received. Required.

Metric

Captures the detailed activities required to carry our the activities recorded by the Audit logs, specifically outbound messages and activities. Required.

Error

Captures error conditions for the application. There are four error severity levels (info, warn, error, fatal). Required.

Debug

Captures data required to correct abnormal conditions. Optional.


Log files

Each type of log is stored in a separate file. A full directory path is not specified, but all log directories have the following structure:

<log-directory>/<ecomp-component>/<ecomp-subcomponent>/[audit.log | metric.log | error.log | debug.log]

Logging frameworks

Java components use EELF (Event and Error Logging Framework).

Log fields

See the ONAP Application Logging Guidelines v1.1 page for descriptions of all fields for each log type.

  • No labels