You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been looking at your project, and it's looking great!
I'm currently pulling temperature values from Shelly1 hardware with temperature module. The hardware module can have up to three temp sensors attached.
I've implemented it as three separate metrics, because i have yet to figure out how to put it all in the same one. (Is this possible?)
The current data processing model of mqtt2prometheus doesn't allow to extract multiple instances of the same time series from the same mqtt event 🤔
I think with the implementation of #74 one could consider to implement something like this. Meanwhile one could try to change the __name__ label during relabeling in Prometheus.
Hi,
I've been looking at your project, and it's looking great!
I'm currently pulling temperature values from Shelly1 hardware with temperature module. The hardware module can have up to three temp sensors attached.
I've implemented it as three separate metrics, because i have yet to figure out how to put it all in the same one. (Is this possible?)
The documentation for this hardware and module can be found here: https://shelly-api-docs.shelly.cloud/gen1/#shelly1-1pm-mqtt
here's some JSON example data on the topic "shellies/shelly1-C45BBE77777B/ext_temperatures" is this:
The config i'm using is roughly this:
Metrics are repeated prom_names "shelly_temperature_1 and 2, as well as mqtt_names: 1.tC and 2.tC
I'm greatful for any assistance.
The text was updated successfully, but these errors were encountered: