cdp-doctor metering status
Scope
The cdp-doctor metering status command checks the health, configuration, and operational status of the metering and telemetry components on a Cloudera node. It validates the correct setup and functioning of the heartbeat service, logging agent, and metering configuration files, ensuring telemetry data is correctly generated and transmitted to the Cloudera Control Plane.
This command is commonly used to troubleshoot usage reporting, billing, and monitoring issues in Cloudera environments.
| Check | Description |
|---|---|
| Configuration Files | Verifies the presence of metering and logging configuration files that define how heartbeats and metrics are collected. |
| Heartbeat Service | Confirms that the metering-heartbeat service responsible for sending usage pings to Cloudera is running. |
| Logging Agent | Validates the cdp-logging-agent (Fluentd), which handles local telemetry collection and forwarding. |
| Heartbeat File (heartbeats.json) | Checks for valid heartbeat JSON data under /var/log/metering/, confirming that heartbeats are being generated and shipped. |
Use Case
- Diagnosing billing or telemetry data gaps in the Cloudera Control Plane.
- Verifying metering service health after deployment or configuration changes.
- Checking whether heartbeats are generated and shipped correctly.
- Preparing to run cdp-telemetry doctor metering salt-healthcheck for cluster-wide validation.
Sample Output
Running the cdp-doctor metering status command displays the following output:
Not found any logging agent configuration file! Heartbeat shipping will not work.
Not found any heartbeat metering configuration file! Without this heartbeats will not be generated.
Required services:
+--------------------+---------------+
| Service name | Service state |
+--------------------+---------------+
| metering-heartbeat | [OK] |
| cdp-logging-agent | [OK] |
+--------------------+---------------+
Cannot parse /var/log/metering/heartbeats.json - could mean problems with the metering service. Please check syslog of the service.- Missing configuration files indicate that either metering or logging configuration files are not present in the expected directories. As a result, heartbeats (usage metrics) cannot be generated or shipped.
- If metering-heartbeat is
[OK], the heartbeat daemon is running correctly and responding. - If cdp-logging-agent is
[OK], the Fluentd logging and telemetry collector is active.
