Telemetry export to third party for Cloudera Data Services on premises
You can configure the OpenTelemetry pipeline to duplicate and route your collected
metrics and logs to external, third-party destinations. To manage these export destinations
without modifying your core collector configuration, you must define your settings through
the ObservabilityPipeline Custom Resource and Kubernetes
Secrets.
Understanding telemetry data export in Cloudera Observability Cloudera Observability exports collected telemetry data by using any exporter that the Cloudera distribution of OpenTelemetry collector supports. The exporter specification describes the encoding, transport, and delivery of telemetry data between telemetry sources, intermediate nodes such as collectors, and telemetry backends. This capability allows you to integrate Cloudera Observability with your existing services.Telemetry export to third party through OpenTelemetry ObservabilityPipeline Custom Resource (CR) and already deployed Kubernetes Secrets. This replication pipeline receives and processes telemetry that the system has collected.Export configuration SignalExportConfig allows you to send a copy of OpenTelemetry collector telemetry data to third party exporters. This does not modify your core collector configuration. You can manage your telemetry export destinations for metrics and logs. This process duplicates the data stream so that your existing collector pipelines continue to function without interruption while distributing data into the new destinations.Configuring exporter Cloudera Data Services on premises to external destinations. You can also create and deploy credential secrets to the Observability namespace to authorize this configuration, and run a validation script to confirm your OpenTelemetry pipeline connections.Advanced exporter 