mirror of
https://github.com/hikhvar/mqtt2prometheus.git
synced 2026-05-20 07:12:57 +00:00
be4af9ff5e
This commit allows to extract the metric name from the topic path. Now it can be configured if all metrics are in a object in a certain topic or if every topic contains exactly one metric. However, currently these modes can not be mixed. This should solve !26 TODO: * Update documentation * Add unit tests
21 lines
757 B
YAML
21 lines
757 B
YAML
mqtt:
|
|
server: tcp://mosquitto:1883
|
|
topic_path: shellies/+/sensor/+
|
|
device_id_regex: "shellies/(?P<deviceid>.*)/sensor"
|
|
metric_per_topic_config:
|
|
metric_name_regex: "shellies/(?P<deviceid>.*)/sensor/(?P<metricname>.*)"
|
|
qos: 0
|
|
cache:
|
|
timeout: 24h
|
|
metrics:
|
|
- prom_name: temperature
|
|
# The name of the metric in a MQTT JSON message
|
|
mqtt_name: temperature
|
|
# The prometheus help text for this metric
|
|
help: shelly temperature reading
|
|
# The prometheus type for this metric. Valid values are: "gauge" and "counter"
|
|
type: gauge
|
|
# A map of string to string for constant labels. This labels will be attached to every prometheus metric
|
|
const_labels:
|
|
sensor_type: shelly
|
|
# The name of the metric in prometheus |