cdp-telemetry doctor metering salt-healthcheck -d <directory>
Scope
The cdp-telemetry doctor metering salt-healthcheck command performs a Salt-based distributed metering health check across all nodes in a Cloudera environment. This command helps validate whether telemetry and metering components are functioning properly across the cluster, ensuring that usage, billing, and monitoring data are collected and reported correctly to the Cloudera Control Plane.
| Components | Description |
|---|---|
| Salt Connectivity | Verifies that the Salt master can reach and execute commands on all minion nodes. |
| Metering Service Status | Runs cdp-doctor metering status on each node to check local metering agent health. |
| Telemetry Pipeline Health | Confirms that telemetry data (usage metrics, billing info, etc.) is being generated and collected. |
| Output Collection | Consolidates individual node reports into a JSON file for centralized diagnostics. |
Use Case
- Performing cluster-wide metering or telemetry validation.
- Verifying Salt orchestration and communication across all nodes.
- Preparing health data for Cloudera Support.
- Diagnosing usage reporting or billing discrepancies.
Sample Output
Running the cdp-telemetry doctor metering salt-healthcheck command displays the following output:
cdp-telemetry doctor metering salt-healthcheck -d .
Running salt command: cmd.run 'cdp-doctor metering status --format json' --out=json --out-file=./salt_metering_healthcheck_result.json
[OK]- An
[OK]status indicates that the health check completed successfully on all targeted nodes. - The salt_metering_healthcheck_result.json (created in the specified directory) file contains the full, per-node health results in JSON format.
- Each node's result includes metering agent status, last sync timestamps, and component health indicators.
- If errors occur, they typically indicate:
- Salt communication issues (minion not responding).
- Telemetry service failures (Fluentd or metering agent down).
- File permission or output path problems.
