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] collapse by only one field for multi-field top values #146733

Closed
Tracked by #184459
drewdaemon opened this issue Nov 30, 2022 · 5 comments
Closed
Tracked by #184459

[Lens] collapse by only one field for multi-field top values #146733

drewdaemon opened this issue Nov 30, 2022 · 5 comments
Labels
enhancement New value added to drive a business result Feature:Lens 🧊 iceboxed 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

@drewdaemon
Copy link
Contributor

Describe the feature:
Collapse-by is currently only be applied at the dimension level. We could consider allowing it to be applied more granularly.

Screen Shot 2022-11-30 at 11 44 00 AM

@drewdaemon drewdaemon added the Team:Visualizations Visualization editors, elastic-charts and infrastructure label Nov 30, 2022
@elasticmachine
Copy link
Contributor

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

@joshdover
Copy link
Contributor

This is important for counter metrics where you need to be able to calculate the rate within the individual dimensions first, before summing to receive a total. Without the ability to collapse on a subset of the breakdown metrics, you can only provide a summed total across all dimensions, rather than maybe only on 1 of them.

My current example is ingest pipeline metrics. These are reported as counters on a per-ES-node, per-pipeline basis. So I need to calculate the counter_rate on those two breakdowns, however I'd like to be able collapse only on the node dimension, and retain the pipeline dimension. This is currently possible with Tables in Lens but not Line or Bar graphs.

Related to elastic/integrations#4597

@joshdover
Copy link
Contributor

The good news is that I don’t think the technical implementation here is going to be reinventing anything, as we already support this in Tables, just not in time-series charts like Line and Bar. I think the initial challenge to getting this done is likely to be the UX design of how to present this in the UI.

I think we should explore copying how Lens Tables presents breakdowns (which are labelled "Rows") by having each breakdown field be a separate pill in the top-level Lens menu, rather than being grouped into a single "top values":

image

@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 Dec 20, 2022
@stratoula
Copy link
Contributor

@stratoula stratoula 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 Aug 9, 2023
@markov00
Copy link
Member

markov00 commented Jun 3, 2024

In order to provide better transparency of priorities, issues that will not be prioritized within the next 24 months are being closed.

Tracking request in Lens general improvements ice box #184459

@markov00 markov00 closed this as not planned Won't fix, can't repro, duplicate, stale Jun 3, 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 🧊 iceboxed 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