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

When scraping OpenMetrics, we don't have count to associate with value #133

Closed
Tracked by #111
flyingmutant opened this issue Jan 11, 2023 · 1 comment
Closed
Tracked by #111
Labels
A-prom Area: Prometheus / OpenMetrics / PromQL compatibility A-sh Area: statshouse (agent / aggregator) C-question Category: question or discussion, not a real issue

Comments

@flyingmutant
Copy link
Contributor

This makes gauges scraped via Prometheus/OpenMetrics pull a bit second-class compared to our native values, where we always have both value and counter data.

@flyingmutant flyingmutant added A-prom Area: Prometheus / OpenMetrics / PromQL compatibility C-question Category: question or discussion, not a real issue labels Jan 11, 2023
@flyingmutant flyingmutant added the A-sh Area: statshouse (agent / aggregator) label Jan 11, 2023
@flyingmutant
Copy link
Contributor Author

Things where approximate distribution (or at least count) is important should usually be exposed as Prometheus histograms.

@flyingmutant flyingmutant closed this as not planned Won't fix, can't repro, duplicate, stale Jan 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-prom Area: Prometheus / OpenMetrics / PromQL compatibility A-sh Area: statshouse (agent / aggregator) C-question Category: question or discussion, not a real issue
Projects
None yet
Development

No branches or pull requests

1 participant