Creating an auto action event

The steps to create a Cloudera Observability auto action definition, which is triggered when a workload application, job, or query matches the auto action’s definition threshold. For example, when a job is taking too long to run it may delay other jobs waiting in the queue. With Auto Actions, you can create an auto action alert that informs you through an email when a job is exceeding its usual runtime so that you can decide whether to manually take steps to alleviate the problem or have an auto action that will terminate the job or query process for you.

Describes how to create a Cloudera Observability Auto Action definition.

Verify that you are logged in to the Cloudera Observability web UI and that you selected an environment from the Analytics Environments page.
1. Log in to Cloudera in a supported browser.
  The Cloudera web interface landing page opens.
2. From the Your Enterprise Data Cloud landing page, select the Observability tile.
  The Cloudera Observability landing page opens to the main navigation panel.
3. From the Cloudera Observability Environments page, select the environment required for analysis.
  
  tip
  You can reduce the number of environments by selecting your environment's type from the Environments list.
  
  The Environment navigation panel opens.
Depending on the environment selected, verify that the Cluster Summary page is displayed for the environment's cluster required for analysis.

tip
The page's title is displayed in the browser tab.
Select the Auto Actions tab.
Do one of the following:
- If no other auto actions exist, select the Management tab and then click Auto Actions Setup.
- If other auto actions exist, click Create Auto Action.
The Auto Actions Create page opens.
In the Auto Action Name field, enter a unique name that is easily identifiable.
From the Scope list, select the workload component service that is to be monitored by the action.
For example, if you want your action to only evaluate Spark related applications, select Spark Application.

Define the conditions for the auto action by doing at least one of the following:

Specify the Criteria:
1. From the Criteria list, select a criteria item.
2. From the Operator list, select the required operator.
  important
  Cloudera Observability does not validate regular expressions when using the matches regex operator for string criteria types, such as User, Pool, or Query Name. Neither does it display help for poor syntax. Cloudera recommends validating your code and syntax before entering your regular expression in the Value field.
3. In the Value field, enter the value for this filter.
  tip
  You can define multiple AND filters for the Criteria by clicking the plus sign.
  note
  An Auto Action does not require the Criteria filter as long as a Trigger condition is defined:
  - When included, only those workloads that are run on the selected workload component service and meet the criteria conditions are tested by the Trigger.
  - When not included, all workloads that are run on the selected workload component service are tested by the Trigger.

Specify the trigger for the auto action by doing the following:

From the Metric list, select a metric item.

Triggers (Scope: Spark applications only)	Description	Additional information
Requested Containers	The total number of containers the application requests.	For Spark, this includes containers allocated for both the Driver and Executors.
Requested Memory	The total amount of memory the application requests across all containers	For Spark, this includes memory allocated for the Driver, Executors, and any additional overhead.
Requested VCores	The total number of virtual cores (vCores) the application requests across all containers.	For Spark, this includes vCores allocated to the Driver and Executors.

From the Operator list, select the required operator.
note
The in between operator is inclusive.
In the Value field, enter the value for this trigger condition.
tip
You can define multiple OR conditions for the trigger by clicking the plus sign.
note
An Auto Action does not require the Trigger filter as long as a Criteria condition is defined:
- When included, workloads that are run on the selected workload component service and meet the criteria conditions are tested by the Trigger.
- When not included, only those workloads that are run on the selected workload component service and meet the criteria conditions are evaluated.

From the Select Action options, select the action that is to be performed when the condition is met.

warning
Terminating a workload application, job, or query could impact other workloads. Especially when another workload is dependent on the results of the terminated workload application, job, or query. Before triggering a Kill type action, Cloudera recommends using the Notification only action until you have verified that no issues will arise if the workload application, job, or query is terminated.
From the Notification section do the following:
1. In the Emails field, enter the email address that you use to log into Cloudera Observability.
  important
  Your email address domain must be in the Allowed Domains list. Only Administrators with Account access permissions can update the allowed domain list, which is located from the Notifications link in the main navigation panel of the Cloudera Management Console.
2. In the Subject field, enter the subject for the email that distinguishes the subject matter from other auto action emails.
Click Create, which creates the action and its audit log, adds it on the Auto Actions Events and Management pages, and displays its status as Enabled and its most recent event type as Create.

When a workload application, job, or query meets the auto action's criteria and trigger conditions, the action event is triggered.