Cloudera Docs

cdp-doctor fluentd doctor

Scope

The cdp-doctor fluentd doctor command runs a health and configuration check for the CDP logging agent (Fluentd / cdp-logging-agent) on a node.

It validates installation, Salt configuration, service status, and network access to downstream endpoints (S3 / Databus) required for log/telemetry shipping.

  • Installation status and detection of the expected binary.
  • Whether Salt applied the correct configuration.
  • The service status (running / enabled).
  • Accessibility of S3 endpoints and Databus API used for shipping logs and telemetry.

Use Case

  • After installing or updating the logging agent.
  • When troubleshooting missing logs/telemetry in the Control Plane.
  • During pre-upgrade checks or if Salt states were re-applied.

Sample Output

Running the cdp-doctor fluentd doctor command displays the following output:

Running logging agent checks ...
deprecated skip_scan_neighbours flag is used but it's going to be ignored since it's deprecated
Logging agent installed ... OK
Logging agent found: cdp-logging-agent
Logging agent configured by Salt ... OK
Logging agent service status ... OK
S3 endpoint accessibility ... OK
Databus API endpoint accessibility ... OK
  • OK results indicate that Fluentd is installed, configured by Salt, running, and can reach S3/Databus endpoints.
  • Deprecation warnings are not critical, but indicate that the configuration should be updated to remove deprecated flags.
  • Any FAIL or WARN entries point to installation, configuration, service, or network problems.