One challenge with using this to alert on outages is that polling the API will fail when there is an internet outage, and we generally won't have a record of it because we are only capturing the 'current state' of the monitors.
It would be great if we could leverage the logs feature of the getMonitorsendpoint to capture past or missed outages.
There is an example implementation of this approach in a javascript solution which leverages influxdb instead of prometheus.
Is such a thing even possible with prometheus style metrics collection? It would be great if we could persist outage information as well as the other metrics.
One challenge with using this to alert on outages is that polling the API will fail when there is an internet outage, and we generally won't have a record of it because we are only capturing the 'current state' of the monitors.
It would be great if we could leverage the
logsfeature of thegetMonitorsendpoint to capture past or missed outages.There is an example implementation of this approach in a javascript solution which leverages influxdb instead of prometheus.
Is such a thing even possible with prometheus style metrics collection? It would be great if we could persist outage information as well as the other metrics.