Ingest metrics using Prometheus remote write
This feature isn’t available to all Chronosphere Observability Platform users and might not be visible in your app. For information about enabling this feature in your environment, contact Chronosphere Support.
The Prometheus Remote-Write 2.0 API (opens in a new tab) provides a standard interface for sending metrics data from Prometheus servers to compatible receivers.
Chronosphere Observability Platform supports metrics ingestion by providing Prometheus remote write HTTP ingestion endpoints.
Observability Platform supports only Prometheus Remote-Write Protocol versions 2.0.0 or later and Prometheus server 3.0.0 or later. All requests must be encrypted using TLS, compressed payloads should be smaller than 16 MB, and metric payloads must contain fewer than 10,000 items.
Remote write endpoints
The Prometheus Remote-Write 2.0 API provides a standard interface for sending metrics data from Prometheus servers to compatible receivers. For Chronosphere Observability Platform, the best practice is to use the Prometheus Agent to send metrics with batching and retries.
However, when using the OpenTelemetry Collector, use the OTLP exporter to send metrics instead of the Prometheus Remote Write exporter.
The remote write endpoint URL is:
https://<COMPANY>.chronosphere.io/data/metrics/api/v1/prom/remote/writeReplace <COMPANY> with your tenant name as used in your Observability Platform
URL.
Prometheus Agent
To get started with Prometheus remote write, configure Prometheus Agent.