Thanks, Brian and Brian! I'm running this as a container so I'm avoiding using the node_exporter, but it's only a couple hundred lines of code for me to do it from scratch using the Python client. I was going back and forth, though, on making the API calls asynchronously and updating a set of Gauges, versus using a custom collector and hitting the API synchronously. Sounds like I should go with something more like the former. On Tuesday, September 22, 2020 at 11:37:24 AM UTC-4 [email protected] wrote:
> On Tuesday, 22 September 2020 16:21:41 UTC+1, Dan Rice wrote: > > Exporter caches the remote API data and reports the values back to > Prometheus as current. > > A simple way to implement this is to write the metrics to a file, to be > picked up by node_exporter's textfile collector. It exposes a metric which > is the modification timestamp of the file, so you can determine when the > data was last updated, and alert if it becomes too stale. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/aea61572-76f9-4f3f-a1a9-22fc0c686eabn%40googlegroups.com.
