Closed harnish-elastic closed 7 months ago
Pinging @elastic/kibana-visualizations @elastic/kibana-visualizations-external (Team:Visualizations)
@harnish-elastic although I see the different behavior, the Lens one makes more sense to me. The maximum value indicates the maximum band. Why do you need a static value here? Why don't you add a dynamic function? So in your example the maximum of cores used. But of course I am not an expert on gauges, this is my personal opinion.
@markov00 wdyt?
With the new Gauge design we are working on you will also be able to see the current numeric value even if it overshoot the target/range
Observability team has migrated the existing gauge chart visualization based on this perspective. The current lens editor only supports horizontal and vertical gauge chart. It will be good to have arc gauge chart a well. Hence we have created this issue.
Tracking this here https://github.com/elastic/kibana/issues/171903
Kibana version: 8.1.0
Elasticsearch version: 8.1.0
Describe the issue:
While performing lens migration, we found that in aggregation based gauge chart as you can see in the image, I have set the maximum range to 5 but still, it is populating the value 8.
While migrating it into gauge chart in lens as you can see in the below image, I have set the same maximum range to 5 and it is populating the value to 5 only but the actual value is 8.
Steps to reproduce:
Expected behavior:
Actual behavior: