CollectorCtrlWorks With Every OTLP Backend
CollectorCtrl governs the collectors. Your telemetry goes wherever you want it — send data to multiple destinations simultaneously, or switch backends tomorrow without touching a single server.
Supported Observability Backends
CollectorCtrl configures and governs standard OpenTelemetry Collector pipelines shipping to any destination supporting OTLP over gRPC or HTTP:
Datadog
Send OTLP telemetry directly to Datadog using the standard OpenTelemetry datadog or otlphttp exporter. CollectorCtrl manages your collector pipelines, label targeting, and hot-reloads — Datadog ingests the telemetry unchanged without requiring proprietary agent daemons.
Elastic (Elasticsearch & Kibana)
Stream logs, metrics, and distributed APM traces to your Elastic deployment using the elasticsearch or otlp exporter. CollectorCtrl automates version upgrades, drift remediation, and Canary rollouts across your nodes while preserving your existing index templates.
Splunk & Splunk Observability Cloud
Route high-throughput log streams and distributed traces to Splunk Enterprise or Splunk Cloud using the splunk_hec or otlp exporter. Manage edge sampling, batch processors, and pipeline fallbacks centrally without touching host YAML.
Grafana Cloud & LGTM Stack
Deploy collectors that fan out traces to Grafana Tempo, logs to Loki, and metrics to Mimir via standard OTLP gRPC. CollectorCtrl provides a single control plane across all environments, letting you update pipeline configurations with zero service restarts.
Honeycomb
Export rich, high-cardinality telemetry events to Honeycomb over native OTLP. Leverage CollectorCtrl's built-in OCB Builder to compile tail-sampling and attribute processors into tailored binaries, optimizing event volume before it leaves your network.
New Relic
Ship OTLP metrics, logs, and APM spans to New Relic with standard API key headers. CollectorCtrl's dynamic label targeting lets you classify and roll out environment-specific pipeline rules to staging and production rings safely.
Prometheus & Cortex / Thanos
Scrape Kubernetes endpoints or system metrics and forward them to Prometheus, Cortex, or Thanos via the prometheusremotewrite exporter. Maintain consistent scrape interval configs across thousands of nodes with automatic drift prevention.
Any OTLP-Compatible Destination
Because CollectorCtrl supervises standard OpenTelemetry Collectors, you can route telemetry to Apache Kafka, ClickHouse, AWS S3 / Athena data lakes, or custom in-house ingestion gateways. You are never locked to any single observability provider.
Adding a New Backend in CollectorCtrl
You never need to build special plugins or proprietary connectors to integrate a new backend. Adding an observability destination takes three simple steps:
- Define the OTLP Exporter: Add the standard exporter configuration (endpoint, headers, authentication) in your policy YAML.
- Attach to Pipelines: Reference the exporter under the traces, metrics, or logs pipelines in your CollectorCtrl Fleet Orchestration policy.
- Canary Deploy: Push the updated policy to a test ring of collectors. Once telemetry continuity is verified, promote the change fleet-wide with zero downtime.
Need deeper fleet governance? Read our guide on OpenTelemetry Fleet Management Best Practices →