3e0e9e54bf
* Fix duplicate metrics in prometheus * Fix duplicate prometheus metrics for entities with multiple labelsets - Move friendly_name detection to state_changed event - Add additional test case * Add review suggestions for prometheus friendly name update * Remove commented out code in prometheus * Update prometheus tests for deleted metrics * Add review suggestions for prometheus - Remove unnecessary firendly_name check in handle_entity_registry_updated - Add assert in test |
||
|---|---|---|
| .. | ||
| README.md | ||
| __init__.py | ||
| manifest.json | ||
README.md
Prometheus integration
This integration exposes metrics in a Prometheus compatible format.
Metric naming guidelines
Please follow these guidelines while defining metrics.
- Metric and label names should conform to Prometheus naming guidelines.
- Domain-specific metrics should have the domain (
sensor,switch,climate, etc.) as a metric name prefix. - Enum-like values (e.g. entity state or current mode) should be exported using a "boolean" metric (values of 0 or 1) broken down by state/mode (as a metric label).