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

[Fleet] Data streams page is slow when there are many data streams #97044

Closed
jen-huang opened this issue Apr 13, 2021 · 2 comments · Fixed by #97058
Closed

[Fleet] Data streams page is slow when there are many data streams #97044

jen-huang opened this issue Apr 13, 2021 · 2 comments · Fixed by #97058
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Fleet Fleet team's agent central management project Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@jen-huang
Copy link
Contributor

jen-huang commented Apr 13, 2021

When there are many data streams, Fleet > Data streams page is slow due to fetching Dashboard information for each data stream package. We can improve the performance by fetching all dashboards once and then doing a lookup based on package name.

In extreme cases, this can cause the /api/fleet/data_streams endpoint to time out, the following screenshot was taken with >120 data streams.

image

@jen-huang jen-huang added bug Fixes for quality problems that affect the customer experience Feature:Fleet Fleet team's agent central management project Team:Fleet Team label for Observability Data Collection Fleet team labels Apr 13, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Feature:Fleet)

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 Feature:Fleet Fleet team's agent central management project Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants