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

A single NaN breaks a graph plot line #594

Closed
leonerd opened this Issue Mar 13, 2015 · 4 comments

Comments

Projects
None yet
2 participants
@leonerd
Copy link

leonerd commented Mar 13, 2015

I'm plotting a graph of cache hit ratio. Normally the number is 1, or rather close to it; but for caches that are rarely used there may be entire time slices with no attempts at all, so the "hit ratio" becomes NaN. A single NaN will entirely break the graph plot, causing the line not to be drawn for later times even though the data series itself has defined numbers there. Furthermore, hovering the mouse in the right area of the graph still shows the on-hover popup to tell me the exact number, series labels, etc...; just the line is invisble.

Almost certainly just a float variable that retains a "NaN" value somewhere in the client-side JS that needs resetting.

@juliusv

This comment has been minimized.

Copy link
Member

juliusv commented Mar 13, 2015

@leonerd Could you take a look if #595 fixes your problem?

@juliusv

This comment has been minimized.

Copy link
Member

juliusv commented Mar 17, 2015

@leonerd any luck with #600 now?

@juliusv

This comment has been minimized.

Copy link
Member

juliusv commented Apr 2, 2015

Heard out of band that this is fixed.

@juliusv juliusv closed this Apr 2, 2015

simonpasquier pushed a commit to simonpasquier/prometheus that referenced this issue Oct 12, 2017

Merge pull request prometheus#594 from InQuicker/k8s-tls-config
Clarify that the in_cluster option only affects discovery.
@lock

This comment has been minimized.

Copy link

lock bot commented Mar 24, 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 24, 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.