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
When trying to use Grafana Alloy as a discovery agent for Nomad containers, we are finding that any meta block information is not visible from the nomad.discovery targets. Since Alloy is using the Nomad HTTP API, it would be great if there was an option to pass meta = true to the nomad.discovery module so that we can do something with that data.
What's wrong?
When trying to use Grafana Alloy as a discovery agent for Nomad containers, we are finding that any meta block information is not visible from the nomad.discovery targets. Since Alloy is using the Nomad HTTP API, it would be great if there was an option to pass
meta = true
to the nomad.discovery module so that we can do something with that data.Steps to reproduce
/* Nomad discovery */
discovery.nomad "nomad_discovery" {
server = "${SERVER}"
bearer_token = "${TOKEN}"
refresh_interval = "10s"
}
/* Prometheus Nomad node metrics scraper */
prometheus.scrape "nomad_scraper" {
targets = discovery.nomad.nomad_discovery.targets
extra_metrics = true
forward_to = [prometheus.remote_write.mimir.receiver]
job_name = "nomad_metrics"
scrape_interval = "10s"
tls_config {
insecure_skip_verify = true
}
}
Look at the output and you find that there is no Nomad based meta block info
System information
RHEL 9.5
Software version
Grafana Alloy Latest Container
Configuration
Logs
The text was updated successfully, but these errors were encountered: