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

Consider supporting additional OpenMetrics types to the datamodel #2409

Closed
dashpole opened this issue Mar 8, 2022 · 0 comments · Fixed by #3868
Closed

Consider supporting additional OpenMetrics types to the datamodel #2409

dashpole opened this issue Mar 8, 2022 · 0 comments · Fixed by #3868
Assignees
Labels
area:data-model For issues related to data model spec:metrics Related to the specification/metrics directory

Comments

@dashpole
Copy link
Contributor

dashpole commented Mar 8, 2022

What are you trying to achieve?

There are a few OpenMetrics types which are currently round-tripped from OM -> OTel -> OM to different types:

  • Info
    • Round-tripps to OM Gauge
  • StateSet
    • Round-tripps to OM Gauge
  • Unknown
    • Round-tripps to OM Gauge

One option to consider is to add types to our datamodel explicitly.

Another option is to add a metric attribute which identifies the original type (open-telemetry/wg-prometheus#69 (comment)).

Additional context.

Suggested in #2380 (review).

@bogdandrutu @Aneurysm9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:data-model For issues related to data model spec:metrics Related to the specification/metrics directory
Projects
None yet
3 participants