-
Feature
-
Resolution: Unresolved
-
Undefined
-
None
-
RHOSO FR2
-
None
-
False
-
None
-
False
-
Not Selected
-
0
-
OBSDA-613Add OpenTelemetry Collection into OpenStack
-
50% To Do, 50% In Progress, 0% Done
Proposed title of this feature request
Collecting OTEL Formatted Metrics in RHOSO
What is the nature and description of the request?
[Please describe]
Why does the customer need this? (List the business requirements)
As an OpenStack RHOSO user, I want my metrics to be labeled using the OpenTelemetry semantic conventions. I plan to use the existing RHOSO Telemetry Operator to collect and store these metrics. Collecting these metrics in the OTEL data model will potentially enhance my operations by enabling edge use cases. In addition, partners are also potentially using OTEL for metrics, so having RHOSO metrics in an OTEL format will enable advanced analytics because both the partner and the RHOSO metrics will be in the same data model.
List any affected packages or components.
RHOSO Telemetry Operator, OpenTelemetry Collector, osProfiler
Open questions
- What metrics should be collected
-
- usage metrics
- e.g vms used
- disk usage
- memory used
- service health metrics
- e.g. Time spent in certain functions of the services (does this belong here or is it related to traces (https://issues.redhat.com/browse/OBSDA-612) ?
- API response time
- Number of api calls
- statistics on the services themselves
- usage metrics