Skip to content
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

Prometheus discovery by CRD and custom labels #183

Open
caruccio opened this issue Dec 21, 2023 · 3 comments
Open

Prometheus discovery by CRD and custom labels #183

caruccio opened this issue Dec 21, 2023 · 3 comments

Comments

@caruccio
Copy link

Hi.

I ´d like to suggest the following:

  1. Allow user to specify prometheus service labels to discover.
  2. Use crd/prometheuses.monitoring.coreos.com objects to discover prometheus instances.
@aantn
Copy link
Contributor

aantn commented Dec 28, 2023

Hey, we already let you specify the Prometheus url using -p. Or we autodiscover.

Can you elaborate on your use case and how you would use this addition?

@caruccio
Copy link
Author

Hey. Sure I can.

  1. Services may be recreated with differente names, whereas labels are more "uniform" across projects (this is my intuition speaking, not real world data). More than once I had to rename a whole namespace where prometheus was installed, which required me to change the -p url provided to krr (of course I forgot that and krr failed on the first run after changes)
  2. Prometheus CRs are the "official" way to create prometheus instances. It may sometimes do not have any of the labels KRR uses to autodiscovery, thus looking into the object itself will always give a valid instance to use.

In fact, this is just a request to be more comprehensive in the discovery process.

@aantn
Copy link
Contributor

aantn commented Dec 31, 2023

Got it, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants