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

Graph legends have irrational behavior when monitoring thousands of hosts #2839

Closed
e271828- opened this Issue Jun 12, 2017 · 4 comments

Comments

Projects
None yet
2 participants
@e271828-
Copy link

e271828- commented Jun 12, 2017

Prometheus graphs are largely unusable when looking at properties across many thousands of hosts.

The graph itself has reasonable behavior, but the legend extends infinitely instead of enforcing a maximum visible length and hiding the rest behind a folded div.

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Jun 12, 2017

The expression browser is only intended for ad-hoc debugging and exploration, for general dashboarding use we recommend Grafana.

Also, it's generally unwise to have thousands of plots on a single graph. It's extremely difficult for a human to pick anything useful out of that much noise.

@e271828-

This comment has been minimized.

Copy link
Author

e271828- commented Jun 12, 2017

Ad-hoc debugging and exploration is less than convenient when you can't stack two graphs on top of each other due to the size of the legends :)

From practical experience I must say I disagree strongly with your second point.

screen shot 2017-06-12 at 2 17 38 pm

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Jul 14, 2017

I'm afraid I don't think it's practical to fix this on our end.

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 23, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 23, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.