-
Epic
-
Resolution: Won't Do
-
Medium
-
None
-
None
-
LOG Sprint 8, LOG Sprint 11
Card
As an ONAP developer, I want a reference example for non-EELF logging.
Conversation
We want a minimal, coherent, compliant example which shows:
- Logging via SLF4J.
- Two components, A and B, where:
- Tests call A via REST.
- A calls B via REST.
- Initialization/propagation/logging of transaction ID.
- Initialization/propagation/logging of invocation ID.
- Propagation of other MDCs including (but not limited to) FromAppId and PartnerName.
- Testcases which:
- Initiate a (dummy) request.
- Parse and verify output from components A and B.
This will exercise canonicalized provider configuration, and will probably assist in its development and/or refinement.
EELF and non-EELF examples should be equivalent.
- blocks
-
LOG-117
Logging RI - Containerization
-
- Closed
-
-
LOG-507
POMBA as RI/Demo of Casablanca Logging spec/library compliance - deployment/helm and runtime
-
- Closed
-
-
LOG-596 logging unit test expects unix line endings - fails on win64 systems
-
- Closed
-
- relates to
-
LOG-116
Logging RI - EELF
-
- Closed
-
-
LOG-126
Validate JDK 11
-
- Closed
-
-
LOG-128 Investigate new JEP-158/271 unified logging in JDK 9-11
-
- Closed
-
- links to
- mentioned in
-
Page Loading...
-
-
-
-
-
1.
|
Handle EMPTY_STRING for serviceName MDC as well as a null value |
|
Closed | pau2882 |
2.
|
Entry/exit marker formatting delimiters - logback.xml uses tabs currently |
|
Closed | michaelobrien |
3.
|
add entry for this log4j library jar into the manifest |
|
Closed | pau2882 |