Cloudera Docs

Configuring Activity Monitoring

The Activity Monitor monitors the MapReduce MRv1 jobs running on your cluster. This also includes the higher-level activities, such as Pig, Hive, and Oozie workflows that run as MapReduce tasks. You can monitor for slow-running jobs or jobs that fail, and alert on these events.

To detect jobs that are running too slowly, you must configure a set of activity duration rules that specify what jobs to monitor, and what the limits on duration are for those jobs. A "slow activity" event occurs when a job exceeds the duration limit configured for it in an activity duration rule. Activity duration rules are not defined by default; you must configure these rules if you want to see events for jobs that exceed the duration defined by these rules.

Minimum Required Role: Configurator (also provided by Cluster Administrator, Limited Cluster Administrator , and Full Administrator)

  1. Go to the MapReduce service.
  2. Click the Configuration tab.
  3. Select Scope > MapReduce service_name (Service-Wide).
  4. Click the Monitoring category.
  5. Specify one or more activity duration rules.
  6. Enter a Reason for change, and then click Save Changes to commit the changes.
  7. Click the Cloudera Manager logo to return to the Home page.
  8. Click the icon that is next to any stale services to invoke the cluster restart wizard.