-
Story
-
Resolution: Done
-
High
-
None
-
None
-
LOG Sprint 2, LOG Sprint 3
Agree transaction ID conventions.
- Fixes to X-TransactionID (MDC RequestID) propagation and initialization.
- Improving the use of X-FromAppID, to indicate who called who.
- Addition of invocationID (to indicate a call from one ONAP component to another), and logging the association with transactionIDs, to allow an accurate call graph to be constructed from the Elastic Stack index.
- Using Markers to indicate entry and exit for components that don't use EELF.
- Using audit and metric logs to indicate entry and exit for components which use EELF.
Next steps:
- Update logging guidelines.
- Retrofit EELF audit/metric behavior. (Markers NOT added to EELF contract).
- blocks
-
LOG-5
Transaction ID propagation - SO
-
- Closed
-
-
LOG-6
Transaction ID propagation - APPC
-
- Closed
-
-
LOG-7
Transaction ID propagation - SDNC
-
- Closed
-
-
LOG-8
Transaction ID propagation - SDC
-
- Closed
-
-
LOG-9
Transaction ID propagation - A&AI
-
- Closed
-
-
LOG-10
Transaction ID propagation - Portal
-
- Closed
-
-
LOG-11
Transaction ID propagation - Vid
-
- Closed
-
-
LOG-12
Transaction ID propagation - DCAEGEN1
-
- Closed
-
-
LOG-13
Transaction ID propagation - Policy
-
- Closed
-
-
LOG-14
Transaction ID propagation - DMaaP
-
- Closed
-
- is blocked by
-
SO-78 SO calling A&AI REST API with its newly created Request ID instead of propagating the existing one
-
- Closed
-