Skip to main content

Prometheus

Coroot uses Prometheus to store metrics. To integrate Coroot with Prometheus, go to the Project Settings, click on Prometheus, and define the Prometheus address and credentials as shown in the following example:

Prometheus Configuration

Multi-tenancy mode​

Coroot supports a multi-tenancy mode, allowing a single Prometheus server to store metrics for multiple projects (or clusters).

In this mode, all Coroot agents (both coroot-node-agent and coroot-cluster-agent) are configured to push metrics to Coroot using the Prometheus Remote Write Protocol. Coroot automatically adds the coroot_project_id label to each metric and uses {coroot_project_id="XXXX"} as an additional selector when querying metrics for a specific project.

Metric cache​

For faster access, Coroot maintains its own on-disk metric cache, continuously retrieving metrics from Prometheus. As a result, Coroot treats the time series database as a source for updating its cache. This allows you to configure Prometheus with a shorter retention period, such as a few hours.

The retention of Coroot's metric cache can be configured using the --cache-ttl CLI argument of the CACHE_TTL environment variable. Check the CLI arguments section for more details.