esphome / esphome/feature-requests
In prometheus everything is exposed as a gauge.
- Dominant language
- No language data
- Stars
- 450
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the problem you have/What new integration you would like**
Currently if you have a counter and expose metrics via prometheus it's exposed as gauge, where better choice would be to expose total count as counter.
**Please describe your use case for this integration and alternatives you've tried:**
We're using counter component to measure power usage, since it's a gauge, there is possibility to miss some points and I think that in fact we are missing some of them:
**Additional context**
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by tracing how the counter component is represented when exposed to Prometheus, then compare the current gauge output with Prometheus counter semantics and the power-usage use case. Done means the intended metric type and behavior are defined and verified without losing relevant counter data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- prometheus
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100