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

[Discover][Field statistics] Number of searches in SearchSession Management #123027

Closed
kertal opened this issue Jan 14, 2022 · 4 comments
Closed
Labels
bug Fixes for quality problems that affect the customer experience duplicate Feature:Search Sessions impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. TestWeek-8.0

Comments

@kertal
Copy link
Member

kertal commented Jan 14, 2022

Kibana version:
8.0-rc1

Original install method (e.g. download page, yum, from source, etc.):
Cloud

Describe the bug:

When using search sessions in Discover's Field statistics tab with a large dataset, I've encountered a mismatch between the number of searches in the management session. So when saving the session and switching to management, I've got 2 searches. Then, after opening the search session, and returning to management, it were 81 searches (That's correct).
It wasn't always the case, but I also encountered a state where the session was marked as Complete, but when I returned to Discover I got a popup that it was still running.

discover-field-stats-search-session.mp4
@kertal kertal added bug Fixes for quality problems that affect the customer experience Feature:Search Sessions Team:AppServicesUx labels Jan 14, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-services (Team:AppServicesUx)

@Dosant
Copy link
Contributor

Dosant commented Jan 14, 2022

but when I returned to Discover I got a popup that it was still running.

Sometimes this could happen because when you restore a session, client side cache kicks in: #106074 (comment)

To make sure this is not happening when reproducing the bug - suggest to reload the page before navigating from search session management (to purge client side cache)

I've got 2 searches. Then, after opening the search session, and returning to management, it were 81 searches (That's correct).
It wasn't always the case, but I also encountered a state where the session was marked as Complete, but when I returned to Discover I got a popup that it was still running.

We have this problem that only searches that were started during your original session are added into search session object.
Meaning that if you saved and left before all your field statists requests kicked in - you won't get them as part of the session.
When you restore - you will restore a "part" of the session (first 2 requests) and all next requests will be started from scratch and you'll see a popup.
here is issue: #97825
and here is specifically about "complete" label: #105061

@kertal
Copy link
Member Author

kertal commented Jan 14, 2022

ok , I see, so I think this is nothing new, so it can be closed, right?

@Dosant
Copy link
Contributor

Dosant commented Jan 14, 2022

Yes, looks like all is known.
Good to know about this newish use-case though 👍

@Dosant Dosant closed this as completed Jan 14, 2022
@exalate-issue-sync exalate-issue-sync bot added impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:small Small Level of Effort labels Feb 1, 2022
@exalate-issue-sync exalate-issue-sync bot removed the loe:small Small Level of Effort label Sep 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience duplicate Feature:Search Sessions impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. TestWeek-8.0
Projects
None yet
Development

No branches or pull requests

3 participants