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

Indicate thresholds on utilization donut charts #901

Closed
ncameronbritt opened this issue Nov 6, 2018 · 18 comments
Closed

Indicate thresholds on utilization donut charts #901

ncameronbritt opened this issue Nov 6, 2018 · 18 comments

Comments

@ncameronbritt
Copy link

ncameronbritt commented Nov 6, 2018

The utilization donut chart pattern indicates that fill colors can be used to indicate different thresholds. It could be helpful for a user to see where those thresholds change and where the current value sits within the ranges. I.e. Am I close to the line, or safely within a range?

@jeperry
Copy link
Member

jeperry commented Nov 6, 2018

+1 this would add much needed context to donuts when there is a threshold.

@LHinson
Copy link
Member

LHinson commented Nov 14, 2018

@ncameronbritt curious, do you have any ideas, examples or designs for how you expected this to look/behave? Not required but wanted to make sure we had all the history.

@jeperry do you want a priority number associated with this issue?

@ncameronbritt
Copy link
Author

I didn't have anything specific in mind, it was something @jeperry mentioned. I could imagine that instead of a grey background on the unfilled part of donut, that the threshold colors are hinted at in some way:
screen shot 2018-11-14 at 4 13 12 pm

@mcoker mcoker added the p4 label Feb 19, 2019
@mcoker
Copy link
Contributor

mcoker commented Feb 19, 2019

@dlabrecq do you know if this is something the charting library supports?

cc @mceledonia

@mceledonia
Copy link

I like the idea, we could visually represent this as faded colors like Cameron shows above, or perhaps 1px colored line at the edge of each threshold would work. Either way I think we can come up with a nice solution from a visual standpoint, and I agree we should support it.

@dlabrecq
Copy link
Member

dlabrecq commented Feb 19, 2019

Victory doesn't support a donut chart out of the box. We can change styles for the stroke color, width, etc., but they're applied to the entire chart. Although, it may be possible to overlay one chart on top of another?

@rachael-phillips rachael-phillips added P1 and removed p4 labels Apr 5, 2019
@rachael-phillips
Copy link
Contributor

rachael-phillips commented Apr 5, 2019

@kybaker and @mceledonia we are bumping this issue up in priority. What are the design next steps on this and what is your availability to work on it?

@rachael-phillips rachael-phillips added this to the 1.0.0-rc.1 milestone Apr 10, 2019
@mceledonia
Copy link

mceledonia commented Apr 10, 2019

@gdoyle1 Actually has some work on this in her donut chart documentation. Take a look at that and I would be happy to pick this up from where she left off! It looks like it might be enough to run with though. I think really I would just take what's there and spell it out more precisely.

@LHinson
Copy link
Member

LHinson commented Apr 10, 2019

nice @mceledonia, where can we find that work?

looping in @ncameronbritt and @beanh66 on this since they have vested interest.

@ncameronbritt
Copy link
Author

May as well get @cshinn in here too, since he's working on the charting stuff in OpenShift.

@mceledonia
Copy link

@LHinson @rachael-phillips @cshinn @ncameronbritt
Check out the donut chart section here
https://docs.google.com/document/d/1-R9JGlkTeU8-xa0lkfox4kn5HxFN6vJjQ1i9NN1-z6M/edit?usp=sharing
@dlabrecq Based on the information there and our conversation earlier in the week, how's that level of detail look? I am happy to expand on what's there if needed, but figured we could check first.

@gdoyle1
Copy link

gdoyle1 commented Apr 10, 2019

This is what I proposed in the documentation:
Donut chart threshold

(Disregard the pointers in the image)
Donut chart fill: When dealing with thresholds, the fill should either be blue, orange or red. The fill starts at 12 ‘oclock and move clockwise.
The fill color depends on the thresholds:

  1. When no thresholds exist, apply the charting color system.
  2. When a threshold exists and the percentage has not surpassed any thresholds, the indicator is blue (#39A5DC). The remaining area of the chart will be #D8D8D8.
  3. When the utilization percentage has surpassed the warning threshold, but not the error threshold, the indicator is orange (#F0AB00). The remaining area of the chart will be #D8D8D8.
  4. When the utilization percentage has surpassed the error threshold, the indicator is red (#CC0000). The remaining area of the chart will be #D8D8D8.

@ncameronbritt
Copy link
Author

The idea behind the original issue was to be able to see how close you are to the threshold--to see where the breakpoints are--not just to be able to change color based on some thresholds. For example in the above mockup, am I just barely in the yellow, in the middle of the yellow, or am I almost in the red?

You get that with the gauges we have in OpenShift:
Screen Shot 2019-04-10 at 3 06 03 PM

@gdoyle1 gdoyle1 self-assigned this Apr 11, 2019
@gdoyle1
Copy link

gdoyle1 commented Apr 16, 2019

@ncameronbritt @beanh66 @cshinn @rachael-phillips @jeperry We still have some technical discovery to do in order to figure out if this option is possible using Victory, but here is what I came up with for donut charts with thresholds https://redhat.invisionapp.com/share/C2RIRGUYTQA. Does this satisfy your requirements?

@ncameronbritt
Copy link
Author

That's similar to what my first thought was. But now seeing the mockups with the different levels, I notice that once it turns yellow you can't see how close you are to blue, and once it turns red you can't see how close you are to yellow or blue. The scale only works in one direction--you can only see how close you are to the next worst level.

I think ideally you should always be able to see thresholds, regardless of the current level.

@mcarrano
Copy link
Member

mcarrano commented May 8, 2019

@gdoyle1 What's the latest on this? Did we ever finalize these designs?

@gdoyle1
Copy link

gdoyle1 commented May 10, 2019

@mcarrano Latest is that I met with the people tagged above to discuss the design and got it passed by Kyle - I then met with @TheRealJon to discuss the feasibility of the design and it seems like it'll work but he'll have to prototype to make sure. I handed this InVision project here that contains the most updated designs and documentation to Jon last week

@gdoyle1 gdoyle1 removed their assignment May 14, 2019
@mcarrano mcarrano moved this from Design to Checkpoint 2 (Final Design Review) in PatternFly 4 Feature Board May 14, 2019
@dlabrecq
Copy link
Member

Created the following PR for the donut percentage and threshold charts.
patternfly/patternfly-react#2064

dlabrecq added a commit to dlabrecq/patternfly-react that referenced this issue May 23, 2019
dlabrecq added a commit to dlabrecq/patternfly-react that referenced this issue May 23, 2019
dlabrecq added a commit to dlabrecq/patternfly-react that referenced this issue May 23, 2019
dlabrecq added a commit to dlabrecq/patternfly-react that referenced this issue May 23, 2019
dlabrecq added a commit to dlabrecq/patternfly-react that referenced this issue May 23, 2019
dlabrecq added a commit to dlabrecq/patternfly-react that referenced this issue May 24, 2019
dlabrecq added a commit to dlabrecq/patternfly-react that referenced this issue May 24, 2019
dlabrecq added a commit to dlabrecq/patternfly-react that referenced this issue May 24, 2019
@mcarrano mcarrano moved this from Checkpoint 2 (Final Design Review) to React Component Development in PatternFly 4 Feature Board May 24, 2019
dlabrecq added a commit to dlabrecq/patternfly-react that referenced this issue May 25, 2019
dlabrecq added a commit to dlabrecq/patternfly-react that referenced this issue May 28, 2019
dlabrecq added a commit to dlabrecq/patternfly-react that referenced this issue May 29, 2019
dlabaj pushed a commit to patternfly/patternfly-react that referenced this issue May 29, 2019
* feat(charts): Add donut threshold & utilization charts

Fixes patternfly/patternfly#901

* chore(charts): modified donut threshold & utilization charts per code review comments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
PatternFly 4 Feature Board
  
React Component Development
Development

No branches or pull requests

9 participants