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] Not having feature to set last bucket value #153326

Closed
harnish-elastic opened this issue Mar 20, 2023 · 10 comments
Closed

[Lens] Not having feature to set last bucket value #153326

harnish-elastic opened this issue Mar 20, 2023 · 10 comments
Labels
impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. Team:Visualizations Visualization editors, elastic-charts and infrastructure triage_needed

Comments

@harnish-elastic
Copy link

Kibana version: 8.6.0

Elasticsearch version: 8.6.0

Describe the bug:

While migrating visualizations to lens, found that Lens doesn't have a support for last bucket value. Due to this thing, not able to migrate visualization to lens because the count getting mismatched due to the last bucket value is showing the value of last bucket while the lens is working on entire time range. Hence not able to migrate these kind of visualizations to lens. Please refer the below screenshot.

screenshot

@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Mar 21, 2023
@stratoula stratoula added triage_needed and removed bug Fixes for quality problems that affect the customer experience labels Mar 22, 2023
@stratoula
Copy link
Contributor

@harnish-elastic have you tried to use the reduced time range to simulate the last bucket behavior?

image

@harnish-elastic
Copy link
Author

@harnish-elastic have you tried to use the reduced time range to simulate the last bucket behavior?

image

@stratoula Yes, we have tried using the reduced time range to simulate the last bucket behavior. However we are not able to match the value of the particular metrics in same time range. Please refer the screenshots for further process. Let me know if I have missed something or you need anything else. Thanks!

Lens:
image

TSVB:
image

@stratoula
Copy link
Contributor

@harnish-elastic if you go to your TSVB chart and switch to timeseries which bucket size is used? You can find it from the x-axis label.

image

@harnish-elastic
Copy link
Author

@harnish-elastic if you go to your TSVB chart and switch to timeseries which bucket size is used? You can find it from the x-axis label.

image

Thank you for providing screenshot. I have checked the bucket size. It is showing 5 minutes. However I am still not able to match the counts in lens. Please refer the below screenshot. Let me know is there anything else I need to correct.

TSVB:
image

Lens:
image

@stratoula
Copy link
Contributor

@harnish-elastic thanx! Can you ping me in Slack to investigate together?

@stratoula
Copy link
Contributor

So the problem here is that in TSVB the last bucket is dropped while in Lens is kept
@harnish-elastic will check why they are dropping the last bucket. If it is needed we need to support it in Lens, otherwise you can transform this to Lens without dropping the last bucket (which can be confusing and in general we dont recommend it)

@harnish-elastic
Copy link
Author

harnish-elastic commented Mar 24, 2023

@stratoula We haven't requirement for dropped last bucket option. But we strongly have requirements of reduced timerange value option to set to auto in lens charts . The reason behind this requirement is every time user won't go to update the reduced timerange value while filtering out the time. Kibana currently supporting only this values for reduced timerange option.

image

@stratoula
Copy link
Contributor

Great, yes I have it on my list to discuss it with the team but I agree that is a nice addition to Lens!

@drewdaemon drewdaemon added the impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. label Apr 6, 2023
@harnish-elastic
Copy link
Author

As discussed with the team, the TSVB visualizations which contains the last bucket can be converted to lens line charts which is the best solution. Hence closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. Team:Visualizations Visualization editors, elastic-charts and infrastructure triage_needed
Projects
None yet
Development

No branches or pull requests

5 participants