Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Allow autoMinMax for percent percentunit types #24177

Closed
knoguchi opened this issue May 2, 2020 · 2 comments
Closed

Allow autoMinMax for percent percentunit types #24177

knoguchi opened this issue May 2, 2020 · 2 comments
Labels
area/datasource/frontend area/units gh-discussions A label used for bulk-migration of FRs/ERs to discussions

Comments

@knoguchi
Copy link

knoguchi commented May 2, 2020

What would you like to be added:
Remove the full scale min and max for the percent and percentunit units.

Why is this needed:
BarGauge panel is more readable when the range is not fixed for min=0 and max=100%. For example when the values are around 1.0% the bar gauge is unreadable.

Same problem for the spark line of the Stat panel. I have a stat panel for a metric where the value is usually 1%, and small deviation is significant. The spark line is kind of flat because the value is low. I can't simply set min and max because it can shoot up to 90% occasionally.

https://github.com/grafana/grafana/blob/master/packages/grafana-data/src/field/fieldOverrides.ts#L160-L175

The above section forces the min=0 and max=100 for precent or max=1 for percentunit when min and/or max is not set. I think it's not necessary. Users can enter 0 and 100 if they want this behavior.

@papagian papagian added this to Needs triage in Platform Backlog via automation May 2, 2020
@peterholmberg peterholmberg added this to Inbox in Backend Platform Backlog via automation Aug 17, 2020
@peterholmberg peterholmberg removed this from Needs triage in Platform Backlog Aug 17, 2020
@peterholmberg peterholmberg moved this from Inbox to Features in Backend Platform Backlog Aug 17, 2020
@marefr
Copy link
Member

marefr commented Sep 29, 2020

@peterholmberg why have this been added to the backend platform backlog?

@marefr marefr added this to Needs triage in Platform Backlog via automation Sep 29, 2020
@marefr marefr removed this from Features in Backend Platform Backlog Sep 29, 2020
@mckn mckn moved this from Needs triage to Feature requests in Platform Backlog Oct 6, 2020
@pkolyvas pkolyvas added gh-discussions A label used for bulk-migration of FRs/ERs to discussions and removed type/feature-request labels Aug 20, 2021
@pkolyvas
Copy link
Contributor

We're in the process of moving Grafana feature requests to GitHub Discussions. This issue is being moved to Discussions or has been moved from our issues list, depending on where you're seeing this message.

We hope to use the discussion thread to continue building use cases, and additional evidence based on engagement/voting, in order to help us prioritize this feature request later on down the road.

As with all things Grafana, we value your input and participation in this project and appreciate your patience during this transitional period. Looking forward to the discussion!

@grafana grafana locked and limited conversation to collaborators Aug 20, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
area/datasource/frontend area/units gh-discussions A label used for bulk-migration of FRs/ERs to discussions
Projects
None yet
Development

No branches or pull requests

4 participants