-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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
Unable to add namespace in nomad_sd_configs #13988
Comments
It looks like the issue isn't with the namespace setting itself, but rather a connection problem. The error message showing "connection refused" suggests that Prometheus can't connect to your Nomad server at localhost:4646... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What did you do?
I'm trying to get the nomad_sd_configs working with a custom namespace.
If I don't specify it works with the default. But if I try to use a custom (or if I put the default like the exame) it gives and error
Discover Nomad services to scrape.
job_name: "nomad_sd"
nomad_sd_configs:
relabel_configs:
target_label: job
What did you expect to see?
No response
What did you see instead? Under which circumstances?
Here is the log
2024-04-24T14:26:40.184Z [prometheus] ts=2024-04-24T14:26:40.184Z caller=refresh.go:90 level=error component="discovery manager scrape" discovery=nomad config=nomad_sd msg="Unable to refresh target groups" err="Get "http:https://localhost:4646/v1/services?namespace=default®ion=global&stale=\": dial tcp [::1]:4646: connect: connection refused"
My guest is the namespace=default®ion=global, was to be namespace=default®ion=global
System information
No response
Prometheus version
No response
Prometheus configuration file
No response
Alertmanager version
No response
Alertmanager configuration file
No response
Logs
No response
The text was updated successfully, but these errors were encountered: