Using the Multi Cloudera Manager Status Dashboard

Use the Multi Cloudera Manager Status Dashboard Status page to monitor the CDH clusters managed by the Cloudera Manager instancess you have added to the Multi Cloudera Manager Dashboard. The Status tab displays a table with rows that contain information about each cluster. Within each row, you can click links to display additional information and go to the relevant Cloudera Manager, cluster, or service.

You configure which columns display by creating Profiles. The name of the active profile displays in a button on the right of the screen above the table of Cloudera Managers. You can choose which profile is active by clicking next to the profile name and selecting a new profile.



In a profile, you can also select Metrics, which are queries that display metrics about the functionality of each cluster. A set of metrics are provided, and you can create custom metrics using the tsquery Language.

Using the Filters section, you can limit the rows displayed by selecting various values of the displayed columns. You can define which columns are used as filters in the profile.

Multi Cloudera Manager Status Dashboard Columns

The Multi Cloudera Manager Status Dashboard displays a table with a row for each cluster managed by a Cloudera Manager. Click the arrows next to a column name to sort the table by the values in the column. Some columns contain links that you can click to display additional details or to go to other displays. You can select which columns to display by editing a Profile. The following table describes the columns.
Multi Cloudera Manager Status Dashboard Columns
Column Description
Status Displays an icon representing the health of the cluster. See Health Status Icons.
Cluster Name Displays the cluster name and the Cloudera Manager that manages it; for example:

Cluster 1 / Sales

The cluster name is a link that you can click to display a pop-up box containing additional information about the cluster. The pop-up includes the following links:
  • Visit Cluster - Opens the Status page in the Cloudera Manager Admin Console for the cluster.
  • Visit Cloudera Manager - Opens the Home page of the Cloudera Manager Admin console for the Cloudera Manager instance.
  • Cloudera Management Service - Opens the Cloudera Management Service > Status page for the Cloudera Manager instance.

The Cluster Name column also displays the latest time that data was fetched from the Cloudera Manager and displays text indicating the health status of the Cloudera Management Service for the cluster.

Services Displays icons indicating the health status of each service defined in the cluster. See Health Status Icons.

Click the service name to open a pop-up box that displays details about the service's status. Click Visit Service to go to the service page in the Cloudera Manager instance that manages that service.

Healthy services are hidden by default. Click the Show healthy services(#) link to show the list of services. Click Hide healthy services to hide them.

Hosts Displays colored badges displaying the number of hosts in the cluster by their health status. For example:



Click the badge to go to the Hosts page of the Cloudera Manager instance that manages the cluster.

CM Version Displays the version of the Cloudera Manager instance.
Cloudera Management Service Status Displays icons indicating the health status of the Cloudera Management Service. See Health Status Icons.
Host Count Number of hosts in the cluster.

Filtering the Status Display

Click the icon next to an item in the Filters section to see the values you can select for filtering. By selecting one or more items, you can limit the rows displayed to those that match the values you select. You can select multiple values for multiple items.

Click the Clear link to remove the filter.

For example, Selecting Filter Values shows the Services filter expanded to include only Flume and HDFS:
Selecting Filter Values

Multi Cloudera Manager Status Dashboard Metrics

The Multi Cloudera Manager Dashboard has a number of default queries you can use to display metrics. You select which metrics display by defining a Profile. See Installing and Managing the Multi Cloudera Manager Dashboard. You can also create custom queries by using the tsquery Language to write queries on data from the Cloudera Manager time-series datastore. See Adding a Custom Metric.

Health Status Icons

The following icons indicate the health of hosts and services:
Status
Indicator Status Description
Started with outdated configuration For a service, this indicates the service is running, but at least one of its roles is running with a configuration that does not match the current configuration settings in Cloudera Manager. For a role, this indicates a configuration change has been made that requires a restart, and that restart has not yet occurred. Click the indicator to display the Stale Configurations page.
Starting The entity is starting up but is not yet running.
Stopping The entity is stopping but has not stopped yet.
Stopped The entity is stopped, as expected.
Down The entity is not running, but it is expected to be running.
History not available Cloudera Manager is in historical mode, and the entity does not have historical monitoring support. This is the case for services other than HDFS, MapReduce and HBase such as ZooKeeper, Oozie, and Hue.
None The entity does not have a status. For example, it is not something that can be running and it cannot have health. Examples are the HDFS Balancer (which runs from the HDFS Rebalance action) or Gateway roles. The Start and Stop commands are not applicable to these instances.
Good health The entity is running with good health. For a specific health test, the returned result is normal or within the acceptable range. For a role or service, this means all health tests for that role or service are Good.
   Concerning health The entity is running with concerning health. For a specific health test, the returned result indicates a potential problem. Typically this means the test result has gone above (or below) a configured Warning threshold. For a role or service, this means that at least one health test is Concerning.
Bad health The entity is running with bad health. For a specific health test, the test failed, or the returned result indicates a serious problem. Typically this means the test result has gone above (or below) a configured Critical threshold. For a role or service, this means that at least one health test is Bad.
Disabled health The entity is running, but all of its health tests are disabled.
Unknown health The status of a service or role instance is unknown. This can occur for a number of reasons, such as the Service Monitor is not running, or connectivity to the Agent doing the health monitoring has been lost.