Prometheus as TSDB on medical device

22 views
Skip to first unread message

Marco Bransch

unread,
Jul 31, 2020, 5:49:14 AM7/31/20
to Prometheus Users
Dear All,

is Prometheus a good solution to record sensor data on an embedded system (medical device) and use the alert mechanism to switch on hardware components e.g. LEDs or inform other software components on the embedded system?

Do have anyone experience with such a scenario?

Thanks for your cooperation.

Best regards,
Marco

Stuart Clark

unread,
Jul 31, 2020, 6:00:10 AM7/31/20
to Marco Bransch, Prometheus Users
On 2020-07-31 10:49, 'Marco Bransch' via Prometheus Users wrote:
> Dear All,
>
> is Prometheus a good solution to record sensor data [1] on an embedded
> system (medical device) and use the alert mechanism to switch on
> hardware components e.g. LEDs or inform other software components on
> the embedded system?
>
> Do have anyone experience with such a scenario [2]?
>
> Thanks for your cooperation.

Maybe.

Is this sensor always on and connected to the network, or is it an IoT
type device not easily/reliably contactable?

Prometheus is designed to scrape metrics from network attached devices
on a frequent basis (no less than once every 2 minutes), with no
mechanism for "offline" usage - any missed scrapes result in gaps in the
data, rather than a way to ingest data later on.

Also, Prometheus isn't a "billing quality" database - occasionally you
might miss metrics and will generally be working on approximate values
(e.g. the use of interpolation for counters). For the alerting/state of
the world type dashboards this is fine, but for billing/scientific
analysis this might not be suitable.

There is nothing otherwise preventing storing sensor data otherwise.
Indeed many people will be ingesting HVAC sensor data in datacenters for
example.

>
> Best regards,
> Marco
>
> --
> You received this message because you are subscribed to the Google
> Groups "Prometheus Users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to prometheus-use...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/prometheus-users/34b64f38-183d-4112-94fd-8b22801375e7o%40googlegroups.com
> [3].
>
>
> Links:
> ------
> [1] https://www.dict.cc/englisch-deutsch/sensor.html
> [2] https://www.dict.cc/englisch-deutsch/scenario.html
> [3]
> https://groups.google.com/d/msgid/prometheus-users/34b64f38-183d-4112-94fd-8b22801375e7o%40googlegroups.com?utm_medium=email&utm_source=footer

--
Stuart Clark

Ben Kochie

unread,
Jul 31, 2020, 6:22:41 AM7/31/20
to Marco Bransch, Prometheus Users
It also depends on how embedded you mean. Prometheus, while pretty efficient, does have a minimum footprint of about 100MiB of memory. It's dynamic, in that it will consume memory and resources as needed.

--
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-use...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages