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

Nomad meta data is not available in nomad discovery records #2538

Open
Teknoenie opened this issue Jan 25, 2025 · 0 comments
Open

Nomad meta data is not available in nomad discovery records #2538

Teknoenie opened this issue Jan 25, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@Teknoenie
Copy link

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


@Teknoenie Teknoenie added the bug Something isn't working label Jan 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant