search

grafana / alloy

OpenTelemetry Collector distribution with programmable pipelines
https://grafana.com/oss/alloy
Apache License 2.0
1.3k stars 179 forks source link

Grafana Agent dashboards do not show Prometheus Discovered targets #314

Open Paul424 opened 10 months ago

Paul424 commented 10 months ago

Request

When running Grafana Agent in clustering mode (and clustering is enabled in Podmonitors / ServiceMonitor components) then there isn't a single overview of the discovered targets any more making it difficult to find out if targets have scrape errors.

Some metrics are made available by Grafana Agent that can be used to setup a dashboard. Some could be reused from the static mode dashboards.

Use case

This feature is required to monitor state of discovered targets.

github-actions[bot] commented 9 months ago

This issue has not had any activity in the past 30 days, so the needs-attention label has been added to it. If the opened issue is a bug, check to see if a newer release fixed your issue. If it is no longer relevant, please feel free to close this issue. The needs-attention label signals to maintainers that something has fallen through the cracks. No action is needed by you; your issue will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity. Thank you for your contributions!

webwurst commented 7 months ago

I ran today into this :) It seems the "Grafana Agent Flow UI" shows for prometheus.operator.servicemonitors under "Debug Info" all the discovered crds, but as targets only those that are scraped by the current instance which serves the UI.

When clustering is enabled a hint in the UI would be nice about only showing parts of the targets.