Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Instrument metrics via the otel_sdk instead of prometheus_client #121

Open
a-thaler opened this issue Nov 18, 2024 · 1 comment
Open

Instrument metrics via the otel_sdk instead of prometheus_client #121

a-thaler opened this issue Nov 18, 2024 · 1 comment

Comments

@a-thaler
Copy link
Collaborator

a-thaler commented Nov 18, 2024

Description

As in future we want to use OTLP for metric exposure, we should migrate already to the OTEL SDK for metric instrumentation before adding new metrics.

Goal: Operational metrics are exposed as before, but relies on the OTEL SDK allowing to switch to a different exporter in future

Criterias:

  • Switch to the OTEL SDK with prometheus exporter, no prometheus dependency is in the code
  • Align metadata of the existing metrics by using the same labels as for the central monitoring setup
  • Align metric naming to OTEL conventions
  • Re-design existing metrics if needed
  • Adjust existing dashboards and alerts to the changes
@a-thaler a-thaler changed the title MIgrate to otel_sdk instead of prometheus_client Migrate to otel_sdk instead of prometheus_client Nov 18, 2024
@a-thaler a-thaler changed the title Migrate to otel_sdk instead of prometheus_client Instrument metrics via the otel_sdk instead of prometheus_client Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants
@a-thaler and others