Cloudera Docs

Creating an auto action event

The steps to create a Cloudera Observability on premises 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 on premises Auto Action definition.
  1. Verify that you are logged in to the Cloudera Observability on premises web UI.
    1. In the URL field of a supported web browser, enter the Cloudera Observability on premises URL that you were given by your system administrator and press Enter.
    2. When the Cloudera Observability on premises Log in page opens, enter your Cloudera Observability on premises user name and password access credentials.
    3. Click Log in.
      The Cloudera Observability on premises web user interface landing page opens, which by default displays the Analytics Environments page that lists your Workload cluster environments.
    4. From the Environment Name column in the Environment's table, select the environment required for analysis.

      The Environments navigation panel opens, which hierarchically lists the environment's cluster, engines, and if applicable the Hive Metastore category.

  2. Depending on the environment selected, verify that the Cluster Summary page is displayed for the environment's cluster required for analysis.
  3. Select the Auto Actions tab.
  4. 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.

  5. In the Auto Action Name field, enter a unique name that is easily identifiable.
  6. 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.
  7. 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.
      3. In the Value field, enter the value for this filter.
    • Specify the trigger for the auto action by doing the following:
      1. 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.
      2. From the Operator list, select the required operator.
      3. In the Value field, enter the value for this trigger condition.
  8. From the Select Action options, select the action that is to be performed when the condition is met.
  9. From the Notification section do the following:
    1. In the Emails field, enter the email address that you use to log into Cloudera Observability on premises.
    2. In the Slack Channel IDs field, enter the Slack channel ID.
    3. In the Subject field, enter the subject for the email that distinguishes the subject matter from other auto action emails.
  10. 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.