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.

Sign up for GitHub

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

Jump to bottom

[ResponseOps][UX] no logs shown when too many logs warning displayed #193618

Open
pmuellr opened this issue Sep 20, 2024 · 1 comment
Open

[ResponseOps][UX] no logs shown when too many logs warning displayed #193618

pmuellr opened this issue Sep 20, 2024 · 1 comment
Labels
enhancement New value added to drive a business result Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@pmuellr
Copy link
Member

pmuellr commented Sep 20, 2024

Doing some stress testing with LOTS of rules (1000's), noticed that the Logs page complains about too many documents to view, but doesn't show any at all. Feels like it should show some up to some limit. Especially since it takes a few seconds to even display that warning.

To work around this, the suggested action does work - adding some filters to get the list below 10K.

Image
@pmuellr pmuellr added Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Sep 20, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@cnasikas cnasikas added the enhancement New value added to drive a business result label Sep 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New value added to drive a business result Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pmuellr @cnasikas @elasticmachine