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
When one of the collectors defined in grafana-agent goes down or hangs, it would be nice to have an alert, for it. Some collectors are generating such rules on it's own like hardware observer charm. Others are not. Also this apply to collectors provide by grafana-agent itself. For example node_exporters send node_scrape_collector_success metrics which is 1 when the last attempt was successful and 0 if it is not. So this is an obvious rule, however some in depth research is needed here
To Reproduce
Deploy grafana-agent, for now it will install snap without --classic option.
Check node_scrape_collector_success metrics
This applied to other exporters, but I wasn't able to identify a good metric for them. Some kind of grafan-agent scrape error counter could be used for that. But I wasn't able to find one
Environment
Relevant log output
-
Additional context
No response
The text was updated successfully, but these errors were encountered:
We should find the analogue of node_scrape_collector_success to all the "enabled by default" collectors.
We should also document somewhere that we need to add those self checks when enabling "disabled by default" collectors.
Bug Description
When one of the collectors defined in grafana-agent goes down or hangs, it would be nice to have an alert, for it. Some collectors are generating such rules on it's own like hardware observer charm. Others are not. Also this apply to collectors provide by grafana-agent itself. For example node_exporters send
node_scrape_collector_success
metrics which is 1 when the last attempt was successful and 0 if it is not. So this is an obvious rule, however some in depth research is needed hereTo Reproduce
node_scrape_collector_success
metricsEnvironment
Relevant log output
Additional context
No response
The text was updated successfully, but these errors were encountered: