-
Notifications
You must be signed in to change notification settings - Fork 312
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
Expose promExporter to service or Prometheus could not scrape #877
Comments
It's already enabled via the headless service, example: |
Ah, maybe we should go ahead and add it to the Headless Service port list if its enabled then. If you're not doing any network policy it should still work though. |
I have 1 more question about promExporter. The thing is when I install a new chart from But if I use embedded promExporter, Grafana always shows no data |
Did you you realice how to use the embedded promExporter on Grafana, show no data to me as well., even using the chart for helm https://github.com/nats-io/prometheus-nats-exporter/blob/main/walkthrough/grafana-jetstream-dash-helm.json |
Hii,
|
What motivated this proposal?
promExporter port 777 should expose to nats service so Prometheus can scrape
What is the proposed change?
should add
promExporter: enabled: true
hereWho benefits from this change?
Who doesn't want to install
prometheus-nats-exporter
fromhttps://prometheus-community.github.io/helm-charts
and can use embedded pod by set enable = true
What alternatives have you evaluated?
I must write a new service to expose prompExporter 777 and update Prometheuse scrape config
The text was updated successfully, but these errors were encountered: