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

Always keep thresholds visible in graphs ('minimum' maximum) #5984

Closed
1 of 3 tasks
dannygoulder opened this issue Sep 7, 2016 · 6 comments · Fixed by #30326
Closed
1 of 3 tasks

Always keep thresholds visible in graphs ('minimum' maximum) #5984

dannygoulder opened this issue Sep 7, 2016 · 6 comments · Fixed by #30326
Labels
area/panel/graph prio/low It's a good idea, but not scheduled for any release type/feature-request

Comments

@dannygoulder
Copy link

  • I'm submitting a ...
  • Bug report
  • Feature request
  • Question / Support request: Please do not open a github issue. Support Options

Please include this information:

  • What Grafana version are you using?
    3.1.1
  • What datasource are you using?
    Elasticsearch 2.x
  • What OS are you running grafana on?
    RHEL 6.x
  • What did you do?
    Added thresholds to a graph which could go far above the upper threshold
  • What was the expected result?
    Threshold lines always visible
  • What happened instead?
    Threshold lines not visible until datapoints exceed them.

I would like to have the option to keep thresholds visible on the graph at all times without needing to set a fixed maximum in the panel settings.

The graph plots the age of replicated data on the y-axis, and our thresholds are 20 minutes and 30 minutes. We would like the upper threshold to be visible all the time to highlight how close (or ideally how far) the age of data is from the threshold, but also to allow the graph to scale beyond the threshold when required.

Effectively this would mean setting a 'minimum' on the maximum, or padding the upper value in the graph to ensure that the threshold is always visible.

Currently I am doing this by using graphite to plot a single value, but this makes the tooltip show the date on the far left of the x axis regardless of where you hover on the graph.

@bergquist bergquist added area/panel/graph prio/low It's a good idea, but not scheduled for any release labels Sep 8, 2016
@torkelo torkelo added this to the 4.0.0-Beta1 milestone Oct 6, 2016
@torkelo torkelo modified the milestones: 4.0.0, 4.0.0-Beta1 Oct 19, 2016
@torkelo torkelo modified the milestones: 4.1.0, 4.0.0 Nov 17, 2016
@torkelo torkelo modified the milestones: 4.2.0, 4.1.0 Dec 14, 2016
@bergquist
Copy link
Contributor

I think this could be solved easier once flexible y-min/y-max have been added. ref #5720

@bergquist bergquist modified the milestones: 5.0, 4.2.0 Feb 14, 2017
@torkelo torkelo removed this from the 5.0 milestone Jul 31, 2017
@gsuberland
Copy link

+1 on this. It would be very useful to set a sort of "y-scale-min" value, so that a long run of small values doesn't appear artificially inflated at first glance due to autoscaling the y-axis.

@tyvich
Copy link

tyvich commented Mar 24, 2019

To expand visually on the value of this feature. Here is a graph of one of our instance’s CPU % value with the y-axis autoscaling based on the data points:

cpu_2_percent

Graph panels allow us to easily compare metrics in relation to values before and after (typically across time), making visual anomaly detection quite easy for us. At first glance, the spike around 11:00 could warrant further investigation (and attracts the users attention) as it is 2 X the values around it.
However, when setting the y-max to 20%, that blip becomes nearly invisible:

cpu_20_percent
cpu_20_percent_cloudwatch

This feature would allow us to add an additional dimension outside of the datapoints (20% in this case) without limiting y axis max (I still want to display up to 100% obviously)

It would expand Grafana’s discovery capability, and allows dashboard users to cut down on lots of “metric clutter” to discover and hone in on just what’s relevant.

I’ve also included a picture of this feature as it works currently in CloudWatch dashboards. Implementation wise, I think a toggle on thresholds to allow them to set the visual initial max would work well.

@tyvich
Copy link

tyvich commented Apr 2, 2019

Would be similar in functionality to #979

@stale
Copy link

stale bot commented Dec 2, 2019

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale Issue with no recent activity label Dec 2, 2019
@torkelo
Copy link
Member

torkelo commented Dec 2, 2019

Sorry, stale bot was wrongly configured (should only have acted on PRs)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/panel/graph prio/low It's a good idea, but not scheduled for any release type/feature-request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants