Skip to main content

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.

Before you can use Chronosphere Observability Platform to view and manage your telemetry data (of whatever type), you need to get that data into Observability Platform.

​
Supported ingestion methods

Observability Platform supports multiple methods to ingest telemetry data, which depend on which type of data you want to ingest:
Ingestion methodChange eventsLogsMetricsTraces
Chronosphere Collector
OpenTelemetry
Telemetry Pipeline
Existing pipeline
Direct to Observability Platform
After ingesting telemetry data, you can use the control mechanisms that Observability Platform provides to control costs and ensure you’re ingesting only the data you care about.

​
OpenTelemetry support

For more information about using OpenTelemetry to ingest logs, metrics, and traces, see OpenTelemetry support in Observability Platform.

​
Ingestion models

Chronosphere utilizes push and pull models of ingestion, depending on the data collected and the method of ingestion.
Telemetry typePushPull
Metrics
Traces
Logs
Pull models, like the Chronosphere Collector, scrape telemetry data from external sources and pull it in. These metrics have consistent reporting intervals. Push models, like tracing, send telemetry data to Chronosphere, which is then processed. These metrics can have a broad spectrum of reporting frequency, from large bursts of data to long periods with no data reporting. The ingestion model depends on the telemetry data source. Metrics pushed to Observability Platform can have latency delays or sparse time series, which can result in unexpected query results.