I'm working in the IIoT domain too. Your workflow is interesting towards the end. Any particular reason, why you don't write it to some db like Timescale or Influx at the end without any prometheus conversion?
Victoria Metrics is a Prometheus compatible time series database and was being used before I joined the company. I haven’t had any issues with it so I didn’t see a reason to pull it from our stack. Are you saying Timescale or Influx can natively ingest MQTT messages?
Similar to your mqtt converter you can make them ingest via Kafka or some other adapter in between. EMQX broker can directly write into TSDB but did not research into others whether they can or not.
Not the OTEL "telemetry" but sensors sending measurements from the field "telemetry". IT tech is, as usual, stealing perfectly defined engineering words and making them something else.
TimescaleDB is perfect if you also have relational data that you need to join with field data to the point that there no pros of using anything else for this use case, say you have 100000+ sensors and you need to group them by the customer site relations while aggregating per day statistics.
doctoboggan|11 months ago
unknown|11 months ago
[deleted]
ilayn|11 months ago
dengolius|11 months ago
ilayn|11 months ago
TimescaleDB is perfect if you also have relational data that you need to join with field data to the point that there no pros of using anything else for this use case, say you have 100000+ sensors and you need to group them by the customer site relations while aggregating per day statistics.