Skip to main content
You can configure the Collector to accept text-exposition payloads in either Prometheus or OpenMetrics formats. To enable the Prometheus and OpenMetrics ingestion for the Collector, add importPrometheus and importOpenMetrics under the push YAML collection in the Collector configuration:
Traffic is served from /import/openmetrics and /import/prometheus from the listenAddress, which defaults to 0.0.0.0:3030.
Additional query parameters:
  • extra_label: pass in repeated, default labels for all time series, formatted as name=value.
  • default_timestamp: provide a default timestamp in Unix milliseconds for any time series that doesn’t have one. Otherwise, the value defaults to Now() on the Chronosphere backend.
The following command includes both of these additional query parameters:

Export Prometheus assets

You can use Chronoctl to sync Prometheus rule definitions and Alertmanager configuration into Observability Platform over the Chronosphere API.
You need Chronoctl installed and configured. Read the Chronoctl documentation for more details.
For example, to export rules from a Prometheus Operator cluster and sync them:
  1. In your Prometheus installation, retrieve your Prometheus rules into a YAML file:
  2. Gather the Alertmanager configuration you want evaluated with those rules (for example, your existing alertmanager.yml).
  3. Run chronoctl sync prometheus. You must pass both Prometheus rules and Alertmanager YAML (-p and -a):
    Chronoctl prints a changelog of changes applied in Observability Platform. To preview changes without writing them, add --dry-run. To control how rules map to teams and collections, pass a Chronosphere mapping file with -c:
For flags and output formats, run chronoctl sync prometheus --help or see the Chronoctl documentation.