-
Notifications
You must be signed in to change notification settings - Fork 572
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide web endpoints to view targets discovered using k8s service discovery #592
Comments
Rperry2174
moved this from TODO
to Discussion / Seeking Contributors
in Pyroscope Public Roadmap
Jan 3, 2022
Rperry2174
moved this from Discussion / Seeking Contributors
to In progress
in Pyroscope Public Roadmap
Feb 7, 2022
gawicks
added a commit
that referenced
this issue
Feb 21, 2022
petethepig
added a commit
that referenced
this issue
Mar 1, 2022
* Provide web endpoints to view targets discovered using k8s service discovery #592 * feat: Provide web endpoints to view targets discovered using k8s service discovery #592 * styling changes * code formatting * rename scrape manager * code formatting * modifies styling Co-authored-by: Dmitry Filimonov <dmitry@pyroscope.io>
korniltsev
pushed a commit
that referenced
this issue
Jul 18, 2023
* Allow specifying a tenant ID This will configure the related X-Scope-OrgID. Note: basic auth is already supported by using the http://user:password@host notation. * Implement round tripper separately
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As an operator, I'd like an easy way to know which pods are being discovered by pyroscope, so that I can troubleshoot why some pods are missing. A log line could work, but this would likely just log once and it'd be hard to track down. A web UI would probably be best.
Prometheus provides a view: http://demo.robustperception.io:9090/service-discovery
This allows the operator to see which pods were discovered, which labels they have and what the relabel config execution produces.
http://demo.robustperception.io:9090/targets is also pretty useful, to know which targets are actually scraped, how long ago they were scraped and how long it took.
The text was updated successfully, but these errors were encountered: