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 upOrdering of targets in a group is not consistent #5155
Comments
This comment has been minimized.
This comment has been minimized.
|
I forgot to provide the labels for this problem:
|
codesome
added
the
kind/bug
label
Jan 30, 2019
This comment has been minimized.
This comment has been minimized.
yeya24
commented
Jan 30, 2019
|
Yeah the logic is a little bit wrong. But I can't reproduce this error. How to reproduce it? Here in my webui the targets are always ordered |
This comment has been minimized.
This comment has been minimized.
|
If the labels come sorted with |
simonpasquier
added
component/ui
priority/P3
labels
Jan 31, 2019
This comment has been minimized.
This comment has been minimized.
|
Opening a PR with the fix in a bit. |
This comment has been minimized.
This comment has been minimized.
|
@codesome looks like this can be closed? |
This comment has been minimized.
This comment has been minimized.
|
Looks that way |
martinhanzik
closed this
Jan 31, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
martinhanzik commentedJan 30, 2019
Bug Report
What did you do?
I added a file scraper using swarm-discovery that automatically generates the file from the docker API.
I opened the 'Targets' page.
What did you expect to see?
Targets in a consistent order, ordered by job first, then label, as specified by #4898
What did you see instead? Under which circumstances?
When refreshing the page, the target order in the group changes. Targets for one job seem to always be ordered by instance, but they mix with the other jobs.
I don't know why https://github.com/prometheus/prometheus/blob/v2.7.0/web/web.go#L698 is using the OR operation for the 2 conditions, normally one would do something like this:
Environment
Prometheus version:
2.7.0
Prometheus configuration file: