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

Display multiple metric on tree map #149680

Open
angorayc opened this issue Jan 27, 2023 · 4 comments
Open

Display multiple metric on tree map #149680

angorayc opened this issue Jan 27, 2023 · 4 comments
Labels
enhancement New value added to drive a business result Feature:Lens impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:large Large Level of Effort Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@angorayc
Copy link
Contributor

angorayc commented Jan 27, 2023

Current multiple metric on tree map is not rendering as expected:
multiple_metric

Expected
request

multiple metric

After putting everything together, ideally it'll look like this (and legend sticks to Group By fields)

alerts_treemap

@botelastic botelastic bot added the needs-team Issues missing a team label label Jan 27, 2023
@angorayc angorayc added Team:Visualizations Visualization editors, elastic-charts and infrastructure Feature:Lens and removed needs-team Issues missing a team label labels Jan 27, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-visualizations @elastic/kibana-visualizations-external (Team:Visualizations)

@stratoula stratoula added enhancement New value added to drive a business result impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. labels Jan 27, 2023
@markov00
Copy link
Member

As stated in a call, I don't believe this is a good practice.
If I'm showing multiple values on a treemap I can face the following problem:

  • is not clear what number refers to the size of the treemap
  • it is useful for simple tree map, but if the treemap is complex, with a lot of nodes and with longer text, the text size becomes an issue and will vanish the effect of having a second metric

We can probably suggest to use 2 separate treemap, like a small multiple, one with one metric and the other with the rest. Reusing the same colors and connecting the interaction on both charts could increase the understanding of the value and improves the visibility of data.
cc @gvnmagni if you have other ideas here

@gvnmagni
Copy link

gvnmagni commented Feb 6, 2023

I find the issue very interesting but I have to say that I largely agree with Marco. It would be very complex for a user to identify what the numbers stand for.

It would be interesting to evaluate if there is a way to clearly inform the user about the role and meaning of those numbers, something so clear visually that it can't be misunderstood, but this is easier said that done and it should come with a solid re-design of typographic hierarchy within blocks. (attaching a very rough example)

Frame 143ss

@timductive timductive added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. and removed impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. labels Feb 8, 2023
@ninoslavmiskovic
Copy link
Contributor

We have a similar ask from O11y to add metrics in the tooltip, so perhaps we can use that for inspiration or handle the JTBD. #106024

@markov00 markov00 added the loe:large Large Level of Effort label Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:Lens impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:large Large Level of Effort Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

No branches or pull requests

7 participants