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

[Lens] Metric Vis 8.5 Follow-ups #137769

Closed
14 of 15 tasks
drewdaemon opened this issue Aug 1, 2022 · 10 comments
Closed
14 of 15 tasks

[Lens] Metric Vis 8.5 Follow-ups #137769

drewdaemon opened this issue Aug 1, 2022 · 10 comments
Labels
Feature:Lens Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects

Comments

@drewdaemon
Copy link
Contributor

drewdaemon commented Aug 1, 2022

@drewdaemon drewdaemon added Team:Visualizations Visualization editors, elastic-charts and infrastructure Feature:Lens labels Aug 1, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors)

@kibanamachine kibanamachine added this to Long-term goals in Lens Aug 1, 2022
@drewdaemon
Copy link
Contributor Author

Suggested/auto prefix for secondary metric

I know this one seems trivial, but we may only be able to support part of this ask. The good news is that it is easy to give the prefix a helpful initial value based on the dimension name.

However, keeping it in sync whenever the dimension name changes is not currently possible because of a boundary in the code between the visualization and the datasource classes. I.e. there's currently no way for the visualization (which handles the prefix) to know when a dimension name has changed (happens in the datasource).

We could consider strengthening the communication channel between datasource and visualization to support something like this, but there may be architectural drawbacks to associating them more closely.

Any thoughts @flash1293 ?

@drewdaemon drewdaemon changed the title [Lens] Small Metric Vis 8.5 Follow-ups [Lens] Metric Vis 8.5 Follow-ups Aug 3, 2022
@flash1293
Copy link
Contributor

flash1293 commented Aug 4, 2022

@andrewctate We have a similar kind of problem with the axis names in xy - the way it's solved is the following:

  • As long as there is no prefix configured for the secondary metric, the name of the table column is used as default (the renderer has access to this information)
  • If a custom name is set, it's passed to the expression argument from the visualization state (which can be empty string as well)

This way the visualizaiton doesn't have to store the default dimension name in its own state

@gvnmagni
Copy link

gvnmagni commented Aug 4, 2022

I had the chance to talk with @markov00 about empty tiles and title+subtitle for panels (when we have a break-down-by). I'm posting here a couple of images as an example but I wanted to mention that he will probably reach out to align details between Lens and Charts

Frame 116

Frame 125

@flash1293
Copy link
Contributor

@gvnmagni I'm not sure I fully get how empty tiles are handled - if there are multiple empty tiles will they all be rendered with the black line in the bottom right? Like for the case with a fully empty 3x2 grid

@gvnmagni
Copy link

gvnmagni commented Aug 4, 2022

Yes exactly, each empty tile would have that little line suggesting that there should be something but given the filters (or any other reason) we don't have it. We can see a difference with the last couple of tiles into the image that has no border, this case is when we have a 5x3 grid but we only show top 13 values and we obtain empty space that would never be filled, it's not a matter of filters

Frame 116

@flash1293
Copy link
Contributor

Makes sense, thanks!

@drewdaemon
Copy link
Contributor Author

drewdaemon commented Aug 5, 2022

add an option to display infinity instead of "Max value" and "Min value" in the color stops UI for metric visualization max / min

@ghudgins we wanted to consult you before committing to this course of action. The idea is that showing the infinity symbol in the context of a single-value metric visualization is more clear than "Max value" and "Min value." WDYT?

Same discussion back in January: #123756 (comment)

@ghudgins
Copy link

ghudgins commented Aug 5, 2022

sounds good - sorry for the delay

@flash1293
Copy link
Contributor

All done!

Lens automation moved this from 8.5 to Done Sep 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Lens Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
No open projects
Lens
  
Done
Development

No branches or pull requests

5 participants