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] Filter last value fields by default #113140

Closed
Tracked by #57708
ghudgins opened this issue Sep 27, 2021 · 7 comments · Fixed by #127251
Closed
Tracked by #57708

[Lens] Filter last value fields by default #113140

ghudgins opened this issue Sep 27, 2021 · 7 comments · Fixed by #127251
Assignees
Labels
Feature:Lens Team:Visualizations Visualization editors, elastic-charts and infrastructure usability
Projects

Comments

@ghudgins
Copy link

Describe the feature:
When selecting the last value function in Lens (top_hits) we should auto apply a fieldname : * filter to the metric / field so that it returns a value if one is present.

Describe a specific use case for the feature:
Given A user is using a data view that has multiple indexes in it (or multiple event.datasets like non data stream beats)
When a user picks "Last Value" + a field
I need the default metric to come out with an "exists" filter on it
So I can avoid the confusion of last value returning a - even though there was a true last value in the interval

@ghudgins ghudgins added usability Team:Visualizations Visualization editors, elastic-charts and infrastructure Feature:Lens labels Sep 27, 2021
@elasticmachine
Copy link
Contributor

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

@kibanamachine kibanamachine added this to Long-term goals in Lens Sep 27, 2021
@flash1293
Copy link
Contributor

I can definitely see the case for this, it's annoying to fall into this trap ("why are some last values empty?"). Some questions:

  • Should it be visible and changeable to the user or should we change the semantics of "last value" to "last existing value" as a whole? Not sure about it, it might be taking away too much control
  • How would transitions work? I guess if the field is changed, then the filter is changed to the new field as long as it was <old field name>: * before, otherwise it just keeps the filter the user defined

@ghudgins
Copy link
Author

I was thinking it could just be applied (and removed by the user if they want) as a default post setting a new field.

yeah on the transition on clear if it's the exists filter for a previous field (if possible)

@ghudgins
Copy link
Author

+1 from observability metrics explorer

@ghudgins
Copy link
Author

+1

I have gone into dashboard visualise and created a table with host name and latest value option for the above indexes, but they appear as dashes

from https://discuss.elastic.co/t/visualising/289212

@flash1293 flash1293 moved this from Long-term goals to 8.2 in Lens Feb 9, 2022
@ghudgins
Copy link
Author

ghudgins commented Feb 25, 2022

I need show on dashboard uptime for server. I tried do this by Lens -> Metric. When i set for metric: Last value od system.uptime.duration.ms and sort by @timestamp then i dont see anything. In index i have this data, i can see this in Discovery modul. When i switch in metric from 'Last value' to Mediana then data was showed. Why i cant see this when i have choosen Last value ?

+1 from https://discuss.elastic.co/t/last-value-of-syste-uptime-duration-ms/298119

@ghudgins
Copy link
Author

+1 https://discuss.elastic.co/t/last-value-no-result-found/297981

hi my field having new value every min, i want to show the latest value of field in Metric regardless of dashboard Time interval but when i choose Last value i got No result found

@flash1293 flash1293 self-assigned this Mar 8, 2022
Lens automation moved this from 8.2 to Done Mar 10, 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 usability
Projects
No open projects
Lens
  
Done
Development

Successfully merging a pull request may close this issue.

3 participants