I will keep it simple: Why does it ignore the “Nodes” label, but it applies the “Routers” label for “job_name”? At least that is how I see it on Grafana. 1 │ // For a full configuration reference, see Grafana Alloy | Grafana Alloy documentation 2 │ logging { 3 │ level = “warn” 4 │ } 5 │ 6 │…

Because job_name is an argument for the prometheus.scrape component that tells it what to set the job_name label to on all resulting metrics. prometheus.exporter.* has no such corresponding argument. To do this, you’ll need to adjust your pipeline by creating a prometheus.relabel component with a …

Disregard the previous explanation, I misread your configuration. The reason is because, as per the prometheus.scrape documentation, the job_name argument only applies if the job label is not already set. In this case, the target list returned by prometheus.exporter.unix.lapi.targets already conta…

Ignores the "job_name" relabling setting

Grafana Alloy

endaro January 6, 2026, 8:17pm 3

To me, the question remains unanswered. Why does it ignore the “Nodes” label, but it applies the “Routers” label for “job_name”?

Topic		Replies	Views
How to change label to job name Grafana label	1	830	September 12, 2024
Recover Kubernetes Nodes names and use them in prometheus.scrape component (metrics_path) Grafana Alloy	0	83	February 12, 2025
`relabel_configs` in river format Grafana Alloy	0	260	March 30, 2024
Prometheus ignore metric by name from target scraping? Prometheus configuration , promethues	1	1063	May 15, 2024
Display hostnames instead of IPs of Nodes in Grafana dashboard	10	38350	January 13, 2021

Ignores the "job_name" relabling setting

Related topics