Acumos platform logging is based upon the ONAP standard ELK stack services, and a set of logging standards that define what "Mapped Diagnostic Context" (MDC) items (i.e. logged event fields/data) are mandatory and optional in logs. Acumos may modify/extend this, but it's expected to be as aligned as possible in the core elements.
The logging service will be provided by a set of components, including:
It's assumed that all Acumos core platform components will implement the logging standards as users of Java-based or python-based logging API libraries from ONAP. The Acumos core components are:
Deployed solution components:
Beyond the Acumos core components, other components may support these standards if there is a compatible library for the programming environment that the components run under. The non-core components are:
Following is an example of this logging configuration file, which Acumos components can use to help standardize their implementation; all four log files will used the same format:
Specific methods of invoking the logging service are covered in the ONAP Application Logging Specification v1.2 (Casablanca), with examples. See the Log Standards page on this wiki for the standards to be adopted in Acumos, including Acumos-specific aspects.
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
Platform-OAM and Logging Subsystem
Following are the current Jira items for the logging stack components and the Platform-OAM component.
Other Components etc
Following are the current Jira items for components that use the logging stack to create log entries.