Cloudera Docs

Creating an Auto Action event

You can create an Auto Action definition in Cloudera Observability that triggers an action when an application, job, or query exceeds its defined thresholds. This allows you to automatically manage workload issues, such as stopping a job that's running too long and potentially delaying others. For example, if a job is exceeding its defined runtime, you can configure an Auto Action to: Notify you through a communication channel (such as email or Slack) or optionally, stop the application, job, or query automatically. The optionality of the Stop action allows you to decide whether you want to manually manage the issue or let the Auto Action resolve it for you automatically.

Describes how to create a Cloudera Observability Auto Action definition.
  1. Log in to the Cloudera Observability web UI
  2. Click on the environment to create an Auto Action. You can filter by environment type from the All Environments option.
  3. Click Analytics > Auto Actions > Create Auto Action
  4. In the Auto Action Name field, enter a unique name that is easily identifiable.
  5. Select an option from the Scope drop-down.
    For example, if you want your action to only evaluate Spark related applications, select Spark Application.

    The following options are currently available for Classic Clusters, Private Cloud Base, Data Lake, and Data Hub: Tez Session, Impala Query, MapReduce Job, Spark Application, and YARN Application.

    The following options are currently available for Cloudera AI: Application, Job, Model, and Session.

  6. Define the conditions for the Auto Action:
    1. Specify a Specify Criteria Logic
      1. AND (default): All criteria conditions must be met.
      2. OR: Any one of the criteria conditions must be met.
    2. Specify a Criteria:
      1. From the Criteria list, select a criteria item. For more information, see the Criteria selection information documentation.
      2. From the Operator list, select the required operator.
      3. In the Value field, enter the value for this filter.
    3. Specify a Trigger Logic
      1. OR (default): Any one of the trigger conditions must be met.
      2. AND: All trigger conditions must be met.
    4. Specify a Trigger:
      1. From the Metric list, select a metric item. For more information, see Trigger selection information documentation.
      2. From the Operator list, select the required operator.
      3. In the Value field, enter the value for this trigger condition.
  7. From the Select Action options, choose the action to perform when the condition is met. The available actions are Notification only and Kill. Choosing Kill automatically includes the Notification only action.
  8. From the Notification section, do the following:
    1. In the Emails field, enter one or more email addresses that you use to log into Cloudera Observability.
    2. In the Slack Channel IDs field, enter the Slack channel ID.
    3. In the Subject field, enter a subject for the email that distinguishes the email from another email for a different Auto Action.
  9. Click Create, which creates the Auto Action, adds an event denoting its creation to the Action Events tab and displays the Auto Action with an enabled status on the Management tab.
The Auto Action executes the defined action when an application, job, or query meets the action's criteria and trigger conditions.