Agenda
- Refactoring the patterns in logback.xml - (ONAP and Acumos) - plus implications for teams
- Lorraine and I started aligning the patterns in logback.xml last thursday in the acumos meeting - however we all need to discuss this and the implications
- https://gerrit.onap.org/r/#/c/62405/
- onap and acumos teams are looking for a standard logback.xml - see https://gerrit.onap.org/r/#/c/63235/
- However we have the following considerations
- Moving MDC attributes to standard attributes (defined in logback.xml)
- pipe/tab delimited - portal and a lot of onap is still pipe
- implications for the pipeline yml in elasticsearch
- implications for our and other logging libraries in use - setting these field as mdcs or standard attributes
- A single pattern for all 4 log files (debug, error, metrics, audit)
- What to do with application.log (it is the default for a lot of components
- Do we make error.log the default (info logs)
- migration story
- default log level
- default debug state true/false
- single logback.xml for all of OOM - is this feasible - LOG-630 - Getting issue details... STATUS
- parameterized values for logDirectory, debug, level
- currently
<property name="pattern" value="%nopexception${p_tim}|%X{EntryTimestamp}|%X{InvokeTimestamp}|%X{RequestId}|%X{InvocationId}|%X{InstanceUUID}| %X{ServiceInstanceId}|%thread|%X{ServiceName}|%X{PartnerName}|%X{StatusCode}|%X{ResponseCode}|%X{ResponseDesc}|%.-5level|%X{Severity}| %X{ServerIPAddress}|%X{ElapsedTime}|%X{ServerFQDN}|%X{ClientIPAddress}|%X{VirtualServerName}|%X{ContextName}|%X{TargetEntity}| %X{TargetServiceName}|%X{TargetElement}|%X{User}|${p_log}|${p_mdc}|${p_msg}%n" /> |2018-08-27T14:08:47.233Z|||1ff4ba60-4b23-4e81-a5fc-0b8055bbf1de||http-apr-8080-exec-4|/logging-demo/rest/health/health|||||INFO||||dev.onap.info|10.42.0.1|||||||org.onap.demo.logging.ApplicationService|InstanceUUID=1ff4ba60-4b23-4e81-a5fc-0b8055bbf1de, RequestID=7ddbb889-0c6d-418e-b59a-df0450e57d76, ServiceName=/logging-demo/rest/health/health, InvocationID=e16e8b3e-01c6-4578-a3fc-d802ab31d91a, InvokeTimestamp=2018-08-27T14:08:47.233Z, PartnerName=, ClientIPAddress=10.42.0.1, ServerFQDN=dev.onap.info|Running /health
- JIRA board - https://jira.onap.org/secure/RapidBoard.jspa?rapidView=143
- review state of Logging Casablanca Scope
- need to fix ciritical CLM issues (library versions) to remove instability flag on CLM job -
LOG-604
-
Getting issue details...
STATUS
- versions approved being fixed https://lists.onap.org/g/onap-discuss/topic/logging_m3_template_ready/24828468?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,24828468
- some fixes (guava) are in oparent now - INT-619 - Getting issue details... STATUS
- pending commits (none 2 merged)
- Collaborations
- Portal/sdk library usage (EELF based) - PORTAL-348 - Getting issue details... STATUS
- Acumos log standardization - single logback.xml https://jira.acumos.org/browse/ACUMOS-1584
- SDC logging issue (fixed?) - OOM-1311 - Getting issue details... STATUS and https://gerrit.onap.org/r/#/c/58267/
- Still need to incorporate templating LOG-560 - Getting issue details... STATUS
- review changes in ONAP Application Logging Specification v1.2 (Casablanca)#StandardAttributes (standard and required) - expected as in
- fix spec table for mdc to standard attributes changes ONAP Application Logging Specification v1.2 (Casablanca)
- fix RI code log/portal for MDC changes
- finish 4 logback.xml pattern examples for 4 logs
- Start enumerating uses cases and verify MDC propagation flows inside and outside a microservice - distributed transactions inside/outside
- between microservices
- inside a microservice
Notes
oparent
clamp
logback.xml rework