-
Epic
-
Resolution: Won't Do
-
Medium
-
None
-
None
-
Single logback.xml in OOM onap parent chart
Discussion with pau2882 and shanedaniel - I should just be using a single logback.xml
key off single pattern developed with lorraineawelch in
https://wiki.acumos.org/display/OAM/Log+Standards
Also lowers config map size issue
Requirements
- R1: single logback.xml from the 20+ currently in oom - with parameterized inputs
- R2: retain existing separate in-image logback.xml for heat deployments and local development
- R3: single logback pattern standard across all onap components
20180823 Notes
(in progress : https://gerrit.onap.org/r/#/c/62405/)
- application.log will be error.log from now on
- missing
{p_log}
for logger field
- missing marker field and mdc field
Discussion (Mandeep, Mike)
- single logback.xml option: all key/value pairs are parameterized as env variables
see wiki
https://wiki.onap.org/display/DW/Logging+Developer+Guide#LoggingDeveloperGuide-Logback.xml
- blocks
-
LOG-480
Static Log checking tool - part of CI/CD pipeline - per onap project
-
- Closed
-
- relates to
-
OOM-1061 ConfigMap size limit exceeded
-
- Closed
-
-
LOG-600
Align with Portal/SDK logging library - investigate/run/modify to comply with MDC spec
-
- Closed
-
-
PORTAL-348
Investigate/Run/Use/Modify Portal/SDC Logging library to align with Spec
-
- Closed
-
-
AAI-1477 Mount a logback.xml file in champ charts
-
- Closed
-
-
-
- Closed
-
-
DCAEGEN2-567
PM-Mapper Collector Service
-
- Closed
-
-
DCAEGEN2-758
review/fix logging pattern for casablanca release
-
- Closed
-
-
OOM-1174 Integrate AAF to Clamp
-
- Closed
-
-
-
- Closed
-
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-