Ingest telemetry data
Chronosphere supports multiple methods to ingest telemetry data, which depends on which type of data you want to ingest.
| Ingestion method | Events | Logs | Metrics | Traces |
|---|---|---|---|---|
| Chronosphere Collector | ||||
| OpenTelemetry Collector | ||||
| Calyptia Core or Calyptia Core Agent | ||||
| Existing pipeline | ||||
| Direct to Chronosphere |
After ingesting telemetry data, use the control mechanisms that Chronosphere provides to control costs and ensure you're ingesting only the data you care about.
Metric and trace data
Chronosphere supports two Collectors to ingest metric and trace data, the Chronosphere Collector and the OpenTelemetry Collector. Chronosphere also supports direct metric imports from Google Cloud Platform.
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. Chronosphere supports the OpenTelemetry JaegerRemoteSampler (opens in a new tab) 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.
Google Cloud Platform
Chronosphere can import metrics data directly from Google Cloud Platform (GCP). GCP metrics map closely to the Chronosphere default Prometheus metrics.
Log data
To ingest log data, Chronosphere recommends using Calyptia Core Agent or a combination of Calyptia Core Agent plus Calyptia Core. Chronosphere also supports using your existing ingest pipeline to ingest log data, such as Fluent Bit, LogStash, or the OpenTelemetry Collector.
Event data
Event data gets sent directly to Chronosphere, and doesn't require an independent collection mechanism. Use the Chronosphere app or CreateEvent API to send your change events (opens in a new tab) to Chronosphere.
You can also ingest change events directly from supported third-party tools such as AWS EventBridge, Buildkite, and LaunchDarkly.
Control costs
Ingesting more telemetry data increases your overall data and storage costs. Chronosphere provides several control mechanisms to manage the data you ingest.
Metric data
Use the following methods to control the metric data you ingest:
- Profile and analyze metrics for their usage and cost.
- Create drop rules to drop incoming metrics based on labels.
- Shape metric data with quotas.
- Reduce the persisted metrics and cardinality at the cost of increased writes.
Tracing data
Use the following methods to control the tracing data you ingest:
- Create sampling rules to control costs and maximize the usefulness of your tracing data.
- Create datasets to map sets of traces to named groups relevant to your organization, and then track processed and persisted bytes for those groups over time.