-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Comments
Pinging @elastic/kibana-vis-editors (Team:VisEditors) |
I can definitely see the case for this, it's annoying to fall into this trap ("why are some last values empty?"). Some questions:
|
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) |
+1 from observability metrics explorer |
+1
|
+1 from https://discuss.elastic.co/t/last-value-of-syste-uptime-duration-ms/298119 |
+1 https://discuss.elastic.co/t/last-value-no-result-found/297981
|
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 intervalThe text was updated successfully, but these errors were encountered: