Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upJob relabeling stops working after v2.4.3 #5404
Comments
This comment has been minimized.
This comment has been minimized.
|
It still works as before, the status page changed however. The job label was briefly not shown here, but it's there again now. |
This comment has been minimized.
This comment has been minimized.
|
@brian-brazil Ah! Okay, so it was only the status page that was changed. Is the update. That's good to know. I've just confirmed that job was set on the metric (even through it was not displayed on the status page).
When you say briefly, was there a commit that corrected the issue in master and I just need to wait for the blessed release? |
This comment has been minimized.
This comment has been minimized.
|
That release was several months ago, either 2.5 or 2.6. |
This comment has been minimized.
This comment has been minimized.
|
Maybe it regressed for v2.8.0? All my screenshots where job is rendered as job_name are from v2.8.0 |
simonpasquier
referenced this issue
Mar 26, 2019
Merged
web/ui: display the job label in /targets #5406
This comment has been minimized.
This comment has been minimized.
|
Right there's been a regression introduced by the Boostrap upgrade, see #5406. |
This comment has been minimized.
This comment has been minimized.
|
Closed by #5406 |
codesome
closed this
Mar 26, 2019
This comment has been minimized.
This comment has been minimized.
|
fantastic! thank you! |
This comment has been minimized.
This comment has been minimized.
|
@codesome @simonpasquier @brian-brazil
|
This comment has been minimized.
This comment has been minimized.
|
That looks fine to me. |
This comment has been minimized.
This comment has been minimized.
|
In the example posted (by both config and pictures), the |
This comment has been minimized.
This comment has been minimized.
|
That's how it works now, everything is grouped by job_name. |
This comment has been minimized.
This comment has been minimized.
|
Okay, so the new behavior is to group by naively adding something like this (I mean I know job_name doesn't show up in the "Before relabing" section), does nothing to the grouping.
Is there an alternate way to change grouping on the targets page? Or was that feature removed completely? |
This comment has been minimized.
This comment has been minimized.
|
There's no way to change grouping, it's now always by job_name. |




mattalberts commentedMar 25, 2019
Bug Report
Relabeling a job stoped working after v2.4.3.
What did you do?
Set scrape config to relabel job based on
__meta_kubernetes_namespaceWhat did you expect to see?
I expected to see the
joblabel replaced by the value of__meta_kubernetes_namespace. the expected behavior occurs on v2.4.3 and prior.What did you see instead? Under which circumstances?
However, relabeling
jobusing the same mechanism in version v2.5.0, v2.6.1, v2.7.2, and v2.8.0 does not work. All jobs remain defaulted to the value ofjob_nameEnvironment