Cloudera Docs

Known Issues

Current known issues and limitations in Cloudera Observability.

CML secret key expiration impacts workload data collection
The CML secret key expires every 24 hours. The key is renewed automatically through an internal scheduled process. If the key expires while the CML workspace is suspended, it does not refresh immediately upon resuming. This delay causes a temporary halt in workload data collection for Cloudera Observability. The automated CML process refreshes the key within 12 hours, and data collection resumes. You can view the error in the logs when the secret expires.
The automatic key refresh runs every 12 hours at 00.00 UTC and 12.00 UTC. To avoid issues, ensure your workspace is active during these times.
Exporting of Impala queries fail for Telemetry Publisher with Cloudera Manager 7.11.3
Telemetry Publisher for Impala queries does not work with Cloudera Manager7.11.3
Upgrade Cloudera Manager from 7.11.3 to 7.11.3 cumulative hotfix 6 (CHF6) version to successfully export Impala queries.
Telemetry publisher test altus connection fails for Cloudera Manager 7.11.3 hotfix (CHF6, 7, and 8) versions
Test connection fails with the following error: 
Exception in thread "main" java.lang.NoSuchMethodError: 'com.google.common.collect.ImmutableSet com.google.common.collect.ImmutableSet.copyOf(java.util.Collection)'
	at com.cloudera.cdp.http.HttpCodesRetryChecker.<init>(HttpCodesRetryChecker.java:57)
	at com.cloudera.cdp.client.CdpClientConfigurationBuilder.<init>(CdpClientConfigurationBuilder.java:53)
	at com.cloudera.cdp.client.CdpClientConfigurationBuilder.defaultBuilder(CdpClientConfigurationBuilder.java:400)
	at com.cloudera.cdx.client.TestDatabusConnection.main(TestDatabusConnection.java:55)

This issue only affects the test connection method.

Upgrade Cloudera Manager to 7.11.3 cumulative hotfix 9 (CHF9) version, and then start Telemetry Publisher.
Auto Action trigger for Impala Engine
Impala Auto Action triggers do not work for the Kerberos-enabled Private Cloud base cluster running onCloudera Manager 7.9.5 and 7.11.3.
Upgrade Cloudera Manager to 7.11.3 cumulative hotfix 9 (CHF9) version.
Interruption of Observability data flow due to HiveServer node failure
In multiple Hive server instances (Active-Active), if one of the Hive server nodes hosting the main OpenTelemetry (OTel) pipeline fails, data flow to Cloudera Observability stops.
Refresh the cluster in Cloudera Manager. If the refresh cluster does not work, restart the Hive server.

For information, see Starting, Stopping, Refreshing, and Restarting a Cluster and Restarting a Cloudera Runtime Service in Cloudera Manager documentation.