--- title: AutoOps events description: AutoOps continuously monitors your Elasticsearch deployments by sampling performance and health metrics at 10-second intervals. This high-frequency data... url: https://www.elastic.co/elastic/docs-builder/docs/3717/deploy-manage/monitor/autoops/ec-autoops-events products: - Elastic Cloud Enterprise - Elastic Cloud Hosted - Elastic Cloud on Kubernetes applies_to: - Elastic Stack: Generally available --- # AutoOps events AutoOps continuously monitors your Elasticsearch deployments by sampling performance and health metrics at 10-second intervals. This high-frequency data collection allows AutoOps to rapidly detect and diagnose issues so you can get timely notifications and resolve issues faster. When AutoOps detects an issue, it creates an event. Events provide detailed analyses of detected issues, including why they were triggered and the steps needed to resolve them. You can view events on the **Deployment** page (for Elastic Cloud Hosted deployments) or the **Cluster** page (for ECE, ECK, and self-managed clusters) in the **Open events** and **Event history** tabs. When you select an event, a flyout appears with insights about the detected issue and actions you can take. ![Screenshot showing an AutoOps event flyout](https://www.elastic.co/elastic/docs-builder/docs/3717/deploy-manage/images/cloud-autoops-events.png) ## Event insights The following table describes the information presented in this flyout: | Section | Description | |-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Event severity | Categorizes the event into one of four severity levels based on its potential impact on the cluster: **Critical**: Immediate threat to cluster functionality. Urgent intervention is required to restore or maintain core operations. **High**: Immediate, significant degradation to usability, performance, or stability. **Medium**: Potential risk to the cluster. Won't cause immediate disruption but can escalate into severe problems if left unaddressed. **Low**: Minor anomalies with minimal operational impact and no threat to cluster stability. | | Notification status | Indicates whether a notification was sent for the event. Click on the badge to view active connectors or edit notification settings. | | Event timestamps | Show when the event was opened (when AutoOps detected the issue), and if applicable, when the event was closed (when AutoOps identified that the issue no longer exists). A closed event doesn't necessarily mean that the issue is resolved, rather that AutoOps no longer detects it. | | What was detected | Describes why the event was created and provides links to drill down into the detected issue. | | Event timeline | Visually presents metrics related to the issue in the last 15 minutes. This chart appears only for events with dynamic metrics. For example, load issues will have this section, but settings-related issues will not. | | Recommendations | Lists recommendations to address the issue and improve your cluster's overall performance. The recommendations are organized according to the suggested order of execution. | | Background and impact | Provides background and context about why the event is important and its potential impact on cluster performance and stability. | ## Event actions In the event flyout, you can perform the following actions: ### Settings AutoOps events are opened and closed based on triggering mechanisms that have default settings for each event type. Select **Settings** from the actions menu to view these event settings and see options to edit them. Avoid making changes that will cause alert triggers to fail. Refer to [Event settings](https://www.elastic.co/elastic/docs-builder/docs/3717/deploy-manage/monitor/autoops/ec-autoops-event-settings) for more details. ### Set up notifications AutoOps can send event notifications to operation management tools like PagerDuty, Opsgenie, Slack, Teams, custom webhooks, and more. Select **Set up notifications** from the actions menu to configure these settings. Refer to [Notification settings](https://www.elastic.co/elastic/docs-builder/docs/3717/deploy-manage/monitor/autoops/ec-autoops-notifications-settings) for more details. ### Dismiss Some events may not require your attention immediately, or at all. If you are an Organization owner, you can dismiss an event to remove all events of its kind from your dashboard and prevent AutoOps from opening other similar events. Select **Dismiss** from the actions menu to dismiss an event. This action can be reversed using the **Dismiss events** report. ### Share event You can share event information with other users by sending them a link to the event in AutoOps. Select the share icon in the flyout to copy the event link. Users can only view the event from the shared link if they have access to the AutoOps deployment or cluster from which the link was copied.