-
Epic
-
Resolution: Unresolved
-
Highest
-
None
-
Logs Management in ONAP
-
Best Practice (global - all code)
-
Not yet performed
-
Original Scope
-
M
-
GO
Description of Use Case / Requirement:
All ONAP applications shall generate logs that can be collected by Kubernetes via STDOUT and STDERR.
Owners (one of these should be the Assignee - use @ notation): zwarico , Pawel_P
Link to HLD/LLD (if any):
Dependency Relationships with Other Projects:
Project Impact (Test Only (TO), Code (C)): C **
Support Status for each Affected Project (Supported (S); Partially Supported (P); Not Supported (N)):
Note: for any affected projects labeled 'P' or 'N', please document the resulting gaps.
Integration Leads (use @ notation):
Company Engagement:
- is blocked by
-
ONAPARC-655
(Honolulu-R8) - NF - LOGS MANAGEMENT - PHASE 1: COMMON PLACE FOR DATA
-
- Open
-
-
REQ-475 (Honolulu-R8) - NF - LOGS MANAGEMENT - PHASE 1: COMMON PLACE FOR DATA
-
- To Do
-
-
REQ-1344 LOGS MANAGEMENT - PHASE 1: COMMON PLACE FOR DATA - LONDON RELEASE
-
- To Do
-
- relates to
-
REQ-1072
Standardized logging fields
-
- To Do
-
-
REQ-374
ONAP shall use STDOUT for logs collection
-
- Done
-
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-