Documentation Index
Fetch the complete documentation index at: https://docs.chronosphere.io/llms.txt
Use this file to discover all available pages before exploring further.
Chronosphere Observability Platform supports OpenTelemetry ingestion for logs,
metrics, and traces.
This ingestion process varies depending on your environment, configuration settings,
and telemetry type, but always follows the same general path:
- Your app is instrumented with the OpenTelemetry SDK to emit telemetry data.
- The OpenTelemetry Collector aggregates and processes this telemetry data.
- Observability Platform ingests this telemetry data through the
OpenTelemetry protocol (OTLP) ingestion endpoints.
OpenTelemetry support for metrics
You can use the OpenTelemetry Collector to send
metrics to Observability Platform. Observability Platform ingests these metrics through
OpenTelemetry protocol gRPC and HTTP ingestion endpoints.
To ingest DogStatsD metrics, add
the StatsD receiver to the
OpenTelemetry Collector.
When Observability Platform ingests metrics from OpenTelemetry, it
converts those metrics to a Prometheus-compatible format.
The Live Telemetry Analyzer
displays special request metadata
relevant to OpenTelemetry metrics.
OpenTelemetry support for traces
You can use the OpenTelemetry Collector to send
traces to Observability Platform. Observability Platform ingests these traces through
OpenTelemetry protocol gRPC and HTTP ingestion endpoints.
You can also use the OpenTelemetry Collector to
configure head sampling
for traces.
OpenTelemetry support for logs
You can use the OpenTelemetry Collector to send
logs to Observability Platform.
Observability Platform ingests these logs through an
OpenTelemetry protocol HTTP ingestion endpoint.
Monitor your OpenTelemetry Collector health and ingestion volume
When you configure the OpenTelemetry Collector to ingest metrics or traces, you can
send operational metrics about the OpenTelemetry Collector
to Observability Platform.
Chronosphere provides the
OpenTelemetry Ingestion & Health
dashboard, which displays information about the health of your OpenTelemetry Collector
instances and the amount of data they’re ingesting and processing.