docs(cpt): feedback

Author: nerda-codes

pages/cockpit/reference-content/cockpit-supported-endpoints.mdx

@@ -7,8 +7,8 @@ content:
   paragraph: 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-04-25
-  posted: 2025-04-25
+  validation: 2025-05-05
+  posted: 2025-05-05
 categories:
   - observability
 ---
@@ -18,25 +18,27 @@ Cockpit supports telemetry ingestion and querying using the following open-sourc
 - [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://grafana.com/oss/prometheus/) for the alert manager
+- [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.
+     Scaleway does not support all endpoints from these upstream APIs. Refer to the exact lists below to find out which endpoints are supported.
     </Message>
 
 <Macro id="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
+  - [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.
+
 <Concept>
   ## Mimir write endpoints
 
@@ -73,21 +75,13 @@ The base URL pattern for metrics is the following: `https://<data-source-id>.met
     - Path: `/prometheus/config/v1/rules/*`
 </Concept>
 
-<Concept>
-  ##  Mimir admin endpoints
-
-    Methods: `GET` and `POST`.
-
-    - Path: `/ruler/delete_tenant_config`
-    - Path: `/compactor/delete_tenant`
-    - Path: `/compactor/delete_tenant_status`
-</Concept>
-
 
 ## 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.
+
 <Concept>
   ## Loki write endpoints
 
@@ -128,6 +122,8 @@ The base URL pattern for logs is the following: `https://<data-source-id>.logs.c
 
 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.
+
 <Concept>
   ## Tempo write endpoints
 
@@ -153,12 +149,14 @@ The base URL pattern for traces is the following: `https://<data-source-id>.trac
     - Path: `/api/v2/search/tag/*/values`
 </Concept>
 
-## Pometheus supported endpoints
+## 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`).
 
-The base URL pattern for the alert manager is the following: `https://<data-source-id>.alertmanager.cockpit.<region>.scw.cloud`. You must replace `<data-source-id>` with the ID of your data source 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 URL.
+  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>
 
 <Concept>
@@ -168,14 +166,4 @@ The base URL pattern for the alert manager is the following: `https://<data-sour
 
     - Path: `/alertmanager/*`
     - Path: `/api/v1/alerts`
-</Concept>
-
-<Concept>
-  ## Alert manager admin endpoints
-
-    Method: `POST`.
-
-    Path: `/multitenant_alertmanager/delete_tenant_config`
-</Concept>
-
-
+</Concept>