---
title: Cockpit supported API endpoints for data source management
description: Discover how to manage your telemetry data sources using the Scaleway-supported Mimir, Loki, Tempo and Prometheus endpoints
tags: observability cockpit endpoints mimir loki telemetry prometheus tempo datasource-management
dates:
  validation: 2025-11-10
  posted: 2025-05-05
---
import Requirements from '@macros/iam/requirements.mdx'


Cockpit supports telemetry ingestion and querying using the following open-source technologies:

- [Mimir](https://grafana.com/oss/mimir/) for metrics
- [Loki](https://grafana.com/oss/loki/) for logs
- [Tempo](https://grafana.com/oss/tempo/) for traces
- [Prometheus](https://prometheus.io/docs/alerting/latest/alertmanager/) for the alert manager

Cockpit exposes a subset of their HTTP APIs so users can push, query, and manage telemetry data from Cockpit.

    <Message type="important">
     Scaleway does not support all endpoints from these upstream APIs. Refer to the exact lists below to find out which endpoints are supported.
    </Message>

<Requirements />

  - A Scaleway account logged into the [console](https://console.scaleway.com)
  - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization or Project
  - [Created](/cockpit/how-to/create-token/) a Cockpit token with the right [permissions](/cockpit/concepts/#cockpit-tokens)
  - Retrieved the URL of your data source from the [Scaleway console](https://console.scaleway.com/cockpit/dataSource) or the [API](https://www.scaleway.com/en/developers/api/cockpit/regional-api/#path-data-sources-list-data-sources)

## Mimir supported endpoints (metrics)

The base URL pattern for metrics is the following: `https://<data-source-id>.metrics.cockpit.<region>.scw.cloud`. You must replace `<data-source-id>` with the ID of your data source and `<region>` with the region where your data source is located (`fr-par`, `nl-ams`, or `pl-waw`).

Refer to the [official Mimir documentation](https://grafana.com/docs/mimir/latest/references/http-api/) for more details about the endpoints below.

<Accordion>
  ## Mimir write endpoints

    <Message type="note">
     You can only use the write endpoints with custom data sources.
    </Message>

    Method: `POST`.

    - Path: `/api/v1/push`
    - Path: `/otlp/v1/metrics`
</Accordion>

<Accordion>
  ## Mimir query endpoints

    Methods: `GET` and `POST`.

    - Path: `/prometheus/api/v1/query`
    - Path: `/prometheus/api/v1/query_range`
    - Path: `/prometheus/api/v1/query_exemplars`
    - Path: `/prometheus/api/v1/series`
    - Path: `/prometheus/api/v1/labels`
    - Path: `/prometheus/api/v1/label/*`
    - Path: `/prometheus/api/v1/metadata`
    - Path: `/prometheus/api/v1/read`
    - Path: `/prometheus/api/v1/status/buildinfo`
</Accordion>

<Accordion>
  ## Additional endpoints

  Methods: `GET`

  - Path: `/federate`

  The `/federate` endpoint aims to **replicate the behavior** of the classic Prometheus `/federate` endpoint, but **it is not an official Mimir endpoint**.
  Refer to the [How to federate metrics](/cockpit/how-to/federate-scaleway-metrics) documentation page for more information.

  <Message type="important">
   The `/federate` endpoint will not be billed during the beta phase. After the beta, the endpoint may incur additional costs.
  </Message>
</Accordion>

<Accordion>
  ## Mimir rules endpoints

    Methods: `GET`, `POST`, and `DELETE`.

    - Path: `/prometheus/api/v1/rules`
    - Path: `/prometheus/api/v1/alerts`
    - Path: `/prometheus/config/v1/rules`
    - Path: `/prometheus/config/v1/rules/*`
</Accordion>


## Loki supported endpoints (logs)

The base URL pattern for logs is the following: `https://<data-source-id>.logs.cockpit.<region>.scw.cloud`. You must replace `<data-source-id>` with the ID of your data source and `<region>` with the region where your data source is located (`fr-par`, `nl-ams`, or `pl-waw`).

Refer to the [official Loki documentation](https://grafana.com/docs/loki/latest/reference/loki-http-api/) for more details about the endpoints below.

<Accordion>
  ## Loki write endpoints

    <Message type="note">
     You can only use the write endpoints with custom data sources.
    </Message>

    Method: `POST`.

    - Path: `/loki/api/v1/push`
    - Path: `/otlp/v1/logs`
</Accordion>

<Accordion>
  ## Loki query endpoints

    Methods: `GET` and `POST`.

    - Path: `/loki/api/v1/query`
    - Path: `/loki/api/v1/query_range`
    - Path: `/loki/api/v1/labels`
    - Path: `/loki/api/v1/label`
    - Path: `/loki/api/v1/label/*`
    - Path: `/loki/api/v1/tail`
    - Path: `/loki/api/v1/series`
</Accordion>

<Accordion>
  ## Loki rules endpoints

    Methods: `GET`, `POST`, and `DELETE`.

    - Path: `/loki/api/v1/rules`
    - Path: `/loki/api/v1/rules/*`
    - Path: `/api/prom/rules`
    - Path: `/api/prom/rules/*`
    - Path: `/prometheus/api/v1/rules`
    - Path: `/prometheus/api/v1/alerts`
</Accordion>

## Tempo supported endpoints (traces)

The base URL pattern for traces is the following: `https://<data-source-id>.traces.cockpit.<region>.scw.cloud`. You must replace `<data-source-id>` with the ID of your data source and `<region>` with the region where your data source is located (`fr-par`, `nl-ams`, or `pl-waw`).

Refer to the [official Tempo documentation](https://grafana.com/docs/tempo/latest/api_docs/) for more details about the endpoints below.

<Accordion>
  ## Tempo write endpoints

    Method: `POST`.

    - Path: `/otlp/v1/traces`
    - Path: `/opentelemetry.proto.collector.trace.v1.TraceService/Export`
    - Path: `/jaeger`
    - Path: `/zipkin`
</Accordion>

<Accordion>
  ## Tempo query endpoints

    Method: `GET`.

    - Path: `/api/echo`
    - Path: `/api/traces/*`
    - Path: `/api/search`
    - Path: `/api/search/tags`
    - Path: `/api/v2/search/tags`
    - Path: `/api/search/tag/*/values`
    - Path: `/api/v2/search/tag/*/values`
</Accordion>

## Prometheus alert manager supported endpoints

The base URL pattern for the alert manager is the following: `https://<alert-manager-id>.alertmanager.cockpit.<region>.scw.cloud`. You must replace `<alert-manager-id>` with the ID of your alert manager and `<region>` with the region where the alert manager is enabled (`fr-par`, `nl-ams`, or `pl-waw`).

Refer to the [official Prometheus alert manager documentation](https://prometheus.io/docs/prometheus/latest/querying/api/#alerts) for more details about the endpoints below.

<Message type="important">
  You must use the [Cockpit API](https://www.scaleway.com/en/developers/api/cockpit/regional-api/#path-alert-manager-get-the-alert-manager) to retrieve the ID of the alert manager.
</Message>

<Accordion>
  ## Alert manager endpoints

    Methods: `GET`, `POST`, and `DELETE`.

    - Path: `/alertmanager/*`
    - Path: `/api/v1/alerts`
</Accordion>