reverts metric visualization#14052
Conversation
|
Why are you reverting metric? |
|
There have been a lot of problems with new metric visualization. |
|
The new metrics allows splits on aggregations while the old one doesn't. Can you keep that functionality? Some of my metrics use the filters aggregations to show different numbers. I was able to do that with the old one by using the bucket metrics but it was easy to understand with the new metric. |
|
We hope to keep all the functionality, except switching between metric and gauge |
|
jenkins, test this |
cadecdc to
0f29527
Compare
|
@ppisljar I just pulled down the latest. Feedback below. It looks like we're defaulting to percent mode with count when creating a new metric. This seems a bit odd to me, what do you think? I believe defaulting to count without percentage mode is the current experience. Have we done any testing to make sure that metric visualizations created in the last few releases have no issues with the reverted metric? Quick comparison between configuration options:
I don't see any legend on a metric (which makes sense). Maybe we need to re-introduce the color input box if label and/or background color is chosen and remove this label? I don't think we need to hide/show legend as it doesn't really make sense to have a legend in the metric viz, however it'd be nice to be able to show/hide labels. In most cases, it's duplicate information that is presented in the title of the visualization. Can we get this configuration back? To me, it's unnecessary to show This is probably more of an enhancement request. I don't see it in the previous version of metric. It'd be great to add the Hope this helps! |
0f29527 to
ce428fa
Compare
|
thanks @alexfrancoeur I added the show labels option back and also made percentage mode disabled by default. This needs more testing (to make sure old visualizations work ok), also more unit tests should be added. |
99dfb99 to
6a14176
Compare
thomasneirynck
left a comment
There was a problem hiding this comment.
thx @ppisljar!
I am in favor of doing this revert for 6.0. I tested this with multiple layouts and setting-combinations.
The flex-based layout works well, and is exactly the behavior we need, especially on dashboards.
This will fix the fitting and margin issues. We also are preserving the coloring options we introduced in v5.
I do understand this needs to be tested, and we have two weeks of QA on this. It should also be easier to address issues in this code-base, which is the same as pre 5.5, and easier to work with than the gauges.
|
sorry @ppisljar @alexfrancoeur, it took me a while to look into this in-depth. I think we should get this in v6. A major is an appropriate venue for introducing a new approach like this. In fact, it is not really a "new" approach, we are just redressing the issues introduced in v5 by reusing the old code-base, slightly expanded to include the coloring options. @alexfrancoeur @timroes Could either of you take a second look? It would be nice if we could pull the trigger on this by the end of this week (yes/no). |
6a14176 to
c52bc62
Compare
|
@thomasneirynck @ppisljar The legend still seems to be missing. There's currently no way to customize a color for a single metric and for ranges. |
|
@alexfrancoeur i would vote to either:
|
|
@ppisljar I'm fine with punting on custom colors for a metric (without a range) now but can we open an issue to track it so we don't forget to come back and address? Also, if that's the case - shouldn't we remove the color option from style when one range is selected? Seems a bit odd that I can choose to color something but not the actual color. |
|
jenkins, test this |
d1d0b58 to
e751774
Compare
|
@thomasneirynck i added another commit, so the old saved metrics will work with this, do you want to take another look into this ? |
|
tilemap tests failling (probably no relation to this PR) |
|
jenkins, test this |
|
jenkins, test this |
Uses the previous html/css rendering code instead of the svg-based rendering for simple metrics.
Uses the previous html/css rendering code instead of the svg-based rendering for simple metrics. This backport required manual edits and js-linting.
Uses the previous html/css rendering code instead of the svg-based rendering for simple metrics. This backport required manual edits and js-linting.









Release Note: The metric visualization now no longer reuses the rendering code of the gauge and goal visualizations. This improves consistency of positioning of the metric on Dashboards.
based on top of tabify response handler for table