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

Support portNumber and bearer_token_file for etcd integration #1017

Open
fplantinga-guida opened this issue Dec 19, 2024 · 0 comments
Open

Comments

@fplantinga-guida
Copy link
Contributor

In our Kubernetes setup (deployed with Rancher) we use a service and servicemonitor from the kube-prometheus-stack to monitor etcd. We tried to convert this to the alloy integration but we have hit the following issues:

  • Rancher etcd pod manifest doesn't specify a portName because it is running with hostNetwork. Unfortunately It is not possible to specify a portNumber in the etcd module.
  • If the above is possible we still need the prometheus.scrape to have the bearer_token_file argument as the metrics can't be scraped without authentication.

Is this something you are going te support?

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

1 participant