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

[Reporting] Use Search Sessions to speed up capture time #90211

Closed
tsullivan opened this issue Feb 3, 2021 · 3 comments
Closed

[Reporting] Use Search Sessions to speed up capture time #90211

tsullivan opened this issue Feb 3, 2021 · 3 comments
Labels
(Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead enhancement New value added to drive a business result impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:medium Medium Level of Effort performance

Comments

@tsullivan
Copy link
Member

With the Search Sessions feature in Kibana, search results can be preloaded in Elasticsearch and viewed later in a Kibana dashboard or other application.

Reporting should utilize Search Sessions so that when a request to generate a report is triggered, the it creates a search session in the background. Once the session has complete status, then Reporting loads the URL and views the application which loads the search session.

This would improve Reporting performance because it removes the latency from the headless browser's requests. The headless browser wouldn't need to stay open as long, which lowers the CPU and RAM utilization.

Thanks to @streamich for the idea.

@elasticmachine
Copy link
Contributor

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

@tsullivan tsullivan added the enhancement New value added to drive a business result label Feb 3, 2021
@streamich streamich added (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:x-large Extra Large Level of Effort performance labels May 4, 2021
@exalate-issue-sync exalate-issue-sync bot added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:weeks and removed impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:x-large Extra Large Level of Effort labels May 13, 2021
@exalate-issue-sync exalate-issue-sync bot added impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. and removed impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. labels Aug 20, 2021
@exalate-issue-sync exalate-issue-sync bot added loe:x-large Extra Large Level of Effort and removed loe:weeks labels Dec 1, 2021
@exalate-issue-sync exalate-issue-sync bot added loe:large Large Level of Effort impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. loe:medium Medium Level of Effort and removed loe:x-large Extra Large Level of Effort impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:large Large Level of Effort labels Apr 1, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

@ppisljar
Copy link
Member

Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still be considered, please reopen with a comment.

@ppisljar ppisljar closed this as not planned Won't fix, can't repro, duplicate, stale Aug 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
(Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead enhancement New value added to drive a business result impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:medium Medium Level of Effort performance
Projects
None yet
Development

No branches or pull requests

5 participants