Details
-
Epic
-
Status: Closed
-
High
-
Resolution: Won't Do
-
None
-
Logging guidelines alignment
Description
Go through all the components in onap and identify and fix any logging compliance code (Java, Python and Go)
And also verify that the 4 log files are being written to properly - debug in debug for example, no info in error.log
Help the teams by doing the work for them and submitting small patches per microservice for the goal of helping out the teams.
prioritize
aai, sdc, so, sdnc, appc
including logging and eelf versions https://wiki.onap.org/display/DW/Logging+Reference+Implementation#LoggingReferenceImplementation-ExistingEELFimplementations
For AAI/Clojure work with shwetank.dave@amdocs.com on AAI-797
Attachments
Issue Links
- blocks
-
LOG-877
S3P: Logging streaming/format alignment for dublin - China Telecom, Deutsche Telekom, Vodafone
-
- Closed
-
- is blocked by
-
LOG-487
LOG Pipeline Integrity: Docker to Filebeat to Logstash to ElasticSearch to Kibana
-
- Closed
-
-
LOG-880 NetworkDiscovery Context builder does not log any information
-
- Closed
-
-
LOG-137 Logging RI: Code OOM kubernetes template/values yamls for RI microservice and filebeat container
-
- Closed
-
- relates to
-
AAI-797 Introduction of Chameleon and Gallifrey to ONAP
-
- Closed
-
-
-
- Closed
-
-
SDC-1530
Add Logging support for WF
-
- Closed
-
-
LOG-47
ONAP Log Locations Summary
-
- In Progress
-
-
LOG-876
S3P: Logging for Core Service/VNF state and transition model - Deutsche Telekom and Vodafone
-
- Closed
-
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-