Incident management
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
Explore the topics in this section to learn how to respond to incidents detected in your Observability data.
| Alerting | Trigger alerts when incidents occur, and use built-in connectors to send the alerts to email, slack, or other third-party systems, such as your external incident management application. |
| Cases | Collect and share information about Observability issues by opening cases and optionally sending them to your external incident management application. |
| Service-level objectives (SLOs) | Set clear, measurable targets for your service performance, based on factors like availability, response times, error rates, and other key metrics. |
Use Elastic Workflows to encode your incident-response runbooks as declarative YAML automations triggered by alerts. The Automate root cause analysis for an Observability alert workflow shows how to invoke an Agent Builder agent on each alert, attach the analysis to a case, and notify the on-call channel.