Monitoring clusters
You can monitor the status of your Cloudera Data Hub cluster from the Cloudera web UI or the CDP CLI.
Required role: The DataHubAdmin or Owner roles at the scope of Cloudera Data Hub allow you to manage the Cloudera Data Hub cluster. Note that EnvironmentAdmin and Owner of the environment can also manage Cloudera Data Hub clusters.
Monitoring Cloudera Data Hub clusters trough the UI
To access information related to your Cloudera Data Hub cluster from the Cloudera web UI, navigate to . Each Cloudera Data Hub cluster is represented by an entry
on the Cloudera Data Hub clusters page. To get more information about a
specific Cloudera Data Hub cluster, click the tile representing your
cluster. When a Cloudera Data Hub cluster is healthy, its status should be
Running
.
To check health of specific hosts and services, navigate to Cloudera Manager.
Monitoring Cloudera Data Hub clusters through the CLI
You can view and monitor your available Data Lake clusters via the CDP CLI using the following commands:
- List all available clusters:
cdp datahub list-clusters
- Describe a specific cluster:
cdp datahub describe-cluster --cluster-name <value>
- Get status of cluster hosts:
cdp datahub get-cluster-host-status --cluster-name <value>
- Get status of cluster services:
cdp datahub get-cluster-service-status --cluster-name <value>
- Get status of specified operation:
cdp datahub get-operation --crn <value> [--operation-id <value>]
To use the
get-operation
command to get the status of a specified event, you need to specify the operation id of the operation. Every operation that starts a process running in the background, like creating, starting, stopping, or repairing a cluster, returns anoperationId
field in the response.Example:cdp datahub create-aws-cluster [args] { "operationId": "23e5bdb6-b3a1-4d25-95aa-262365ecc6b9", "cluster": { ... } }
The value of this
operationId
can be used as the value for the--operation-id
option for theget-operation
command.Example:cdp datahub get-operation --crn crn:cdp:datahub:us-west-1:9d74eee4-1cad-45d7-b645-7ccf9edbb73d:cluster:6eeb2804-c938-4564-9da1-a005250d450b --operation-id 23e5bdb6-b3a1-4d25-95aa-262365ecc6b9
Output format:{ "operationId": "identifier of the operation", "operationName": "Short name of the operation", "operationStatus": "UNKNOWN | RUNNING | FAILED | FINISHED | CANCELLED", "started": "Start time of the operation" "ended": "End time of the operation if it is completed" }
Output example:{ "operationId": "23e5bdb6-b3a1-4d25-95aa-262365ecc6b9", "operationName": "Provision", "operationStatus": "RUNNING", "started": "2025-01-15T10:31:37+00:00" }
Unsuccessful operation statuses are stored for 2 weeks, while successful status operations are stored for 1 day.
The operation id is optional, and if it is omitted, the status of the last operation is returned.
- Get status of latest operation:
cdp datahub get-operation --crn <value>
Example:cdp datahub get-operation --crn crn:cdp:datahub:us-west-1:9d74eee4-1cad-45d7-b645-7ccf9edbb73d:cluster:6eeb2804-c938-4564-9da1-a005250d450b { "operationId": "23e5bdb6-b3a1-4d25-95aa-262365ecc6b9", "operationName": "Provision", "operationStatus": "RUNNING", "started": "2025-01-15T10:31:37+00:00" }