-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
OTEL metrics data model
-
Security & Compliance
-
False
-
-
False
-
Not Selected
-
NEW
-
To Do
-
NEW
-
83% To Do, 17% In Progress, 0% Done
OCP/Telco Definition of Done
Epic Template descriptions and documentation.
<--- Cut-n-Paste the entire contents of this description into your new Epic --->
Epic Goal
- Document the de-facto data model for metrics provided by OCP components out of the box.
- Document how the data model relates to the OpenTelemetry standards.
Why is this important?
- Customers want to understand how the OCP metrics are structured and how they can be integrated with solutions compatible with the OTEL standards.
Scenarios
- ...
Acceptance Criteria
- Current model documented in https://github.com/rhobs/observability-data-model
- Mapping to the OTEL semantic conventions documented in https://github.com/rhobs/observability-data-model
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
