Cloudera Docs

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.

Cloudera supported exporters:

  1. AWS EMF Exporter
  2. Azure Monitor Exporter
  3. Datadog Exporter
  4. FileExporter
  5. Load Balancing Exporter
  6. Prometheus Exporter
  7. Prometheus Remote Write Exporter
  8. Syslog Exporter
  9. Splunk HTTP Event Collector (HEC) Exporter
  10. Debug Exporter
  11. nop (no-operation) exporter
  12. OTLP (OpenTelemetry Protocol) Exporter
  13. OTLP HTTP Exporter

To allow data delivery to the backend, Cloudera Observability supports multiple components from the OpenTelemetry Collector. You can route infrastructure metrics and application metrics. Exporters currently export these metrics.

Cloudera Observability collects and exports infrastructure and application or service metrics of the Cloudera Base on premises environment. The OpenTelemetry Collector periodically scrapes running and completed jobs by calling internal APIs to gather status data.