You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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...
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://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: