AutoOps events

An AutoOps event provides a detailed analysis of a specific issue, including why it was triggered and the steps needed to resolve it. The following sections provide you with comprehensive insights and context around issues, the reasons why the event was created, as well as the affected nodes and indices with high indexing activity.

AutoOps provides a set of recommendations. The sequence of their appearance indicates the suggested order of steps to address the issue.

The time the event was detected (opened at) and the time AutoOps identified that the issue no longer exists (closed at). The closing of an event does not necessarily indicate that the customer resolved the issue, but rather that AutoOps no longer detects it.

Provides background and context as to why an event is important, and the impact it can have on performance and stability.

This chart visually represents metrics related to an issue. It appears only for events with dynamic metrics. For example, load issues will have this section, while settings-related issues will not.

Events are categorized into three levels of severity - high, medium, and low - based on their potential impact on cluster performance and stability:

AutoOps events are set to open and close based on triggering mechanisms that have default settings for each event type. You can modify the default settings through the Customize option in the event settings. Be cautious while changing these settings, to avoid situations where alerts fail to trigger.

AutoOps can send notifications to a variety of operation management tools like PagerDuty, Opsgenie, Slack, Teams and custom webhooks. Refer to Notifications Settings for more details.

You can easily share event information with other users by sending them a direct link to the AutoOps event using the share event link located at the top right of the event window.

Only users with access to the AutoOps deployment from which the link was copied can view the event details.