Skip to content

Kibana alerting scalability guidance #89120

@arisonl

Description

@arisonl

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Team:ResponseOpsPlatform ResponseOps team (formerly the Cases and Alerting teams) t//

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions