Chronosphere Collector or OpenTelemetry Collector
Your Collector selection depends on the telemetry data you plan to ingest. Chronosphere recommends using the vendor-supported, optimized, and highly performant Chronosphere Collector for Prometheus discovery and scrape workloads. This use case typically works best with metrics data. Use the OpenTelemetry Collector if your organization uses OpenTelemetry SDKs for app instrumentation. An added benefit of using the OpenTelemetry Collector is you can configure dynamic, remotely configurable head sampling, which is a powerful control mechanism for managing your tracing costs. Observability Platform supports the OpenTelemetry JaegerRemoteSampler head sampling standard for remotely controlling the sampling configuration of OpenTelemetry SDKs.| Chronosphere Collector | OpenTelemetry Collector |
|---|---|
| Proprietary | Open source |
| Fully supported by Chronosphere Support | Exporter configuration support |
| No remote trace sampling support | Remote trace sampling support |
Chronosphere doesn’t provide customer support for OpenTelemetry components.
Integrations
Observability Platform supports these metrics integrations:AWS Cloudwatch metrics
Configure AWS to stream metrics to Observability Platform through CloudWatch Metrics Streams.
Azure metrics
Connect Observability Platform with Azure Monitor to ingest metrics.
Google Cloud metrics
Connect Observability Platform with Google Cloud to ingest metrics from Google Cloud projects.
OpenTelemetry
Use the OpenTelemetry protocol (OTLP) HTTP endpoint to route metrics from OpenTelemetry.