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] Add option for overall_* functions to indicate which grouping level should apply #174510

Closed
Tracked by #182774
dej611 opened this issue Jan 9, 2024 · 2 comments
Closed
Tracked by #182774
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. Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@dej611
Copy link
Contributor

dej611 commented Jan 9, 2024

Describe the feature:

Currently any overall_* function work at metric aggregation parent level grouping, this means that while in this table configuration the "overall" meaning applies for the entire dataset:

Screenshot 2024-01-09 at 12 35 05

Adding a nested grouping the "overall" function will operate at the most-nested level (in the example at @timestamp level):

Screenshot 2024-01-09 at 12 36 04

Which can be limiting for some use cases like global count (as already discussed in this issue: #160562 ).

Describe a specific use case for the feature:

It would be nice to have a feature to tell the overall_* function at what grouping level it should operate.

@dej611 dej611 added enhancement New value added to drive a business result Team:Visualizations Visualization editors, elastic-charts and infrastructure Feature:Lens labels Jan 9, 2024
@elasticmachine
Copy link
Contributor

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

@stratoula stratoula added the impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. label Jan 9, 2024
@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 Jan 10, 2024
@markov00
Copy link
Member

markov00 commented May 7, 2024

Closing this because it's not planned to be resolved in the foreseeable future. It will be tracked in our Icebox and will be re-opened if our priorities change. Feel free to re-open if you think it should be melted sooner.

@markov00 markov00 closed this as not planned Won't fix, can't repro, duplicate, stale May 7, 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. Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

No branches or pull requests

5 participants