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

Kibana alerting scalability guidance #89120

Closed
arisonl opened this issue Jan 25, 2021 · 1 comment · Fixed by #91171
Closed

Kibana alerting scalability guidance #89120

arisonl opened this issue Jan 25, 2021 · 1 comment · Fixed by #91171
Labels
documentation Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@arisonl
Copy link
Contributor

arisonl commented Jan 25, 2021

A very frequent ask in customer meetings as well as in discussions with consulting is to provide guidance on how to scale Kibana alerting. The most common question is some flavour of:

  • "How many Kibana instances are needed to run X alerts per minute?"

Clearly there are many factors involved in order to be able to answer this question precisely, factors that we cannot be aware of per each particular case, but nevertheless we should be able to provide guidance, good practices or rule of thumbs in order to provide a sense of what to be expected.

We have done extensive performance testing, which highlights that the answer is a function of many parameters, but it should result in some sort of guidance in order to be of practical use to customers. This item has been discussed in the past as a GA deliverable.

@arisonl arisonl added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) documentation labels Jan 25, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
3 participants