docs(cpt): add menu

Author: nerda-codes

menu/navigation.json

@@ -3849,6 +3849,10 @@
                   {
                     "label": "Cockpit capabilities and limits",
                     "slug": "cockpit-limitations"
+                  },
+                  {
+                    "label": "Cockpit supported API endpoints for data source management",
+                    "slug": "cockpit-supported-endpoints"
                   }
                 ],
                 "label": "Additional Content",

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

@@ -1,11 +1,11 @@
 ---
 meta:
-  title: Cockpit supported API endpoints
-  description: Discover how to manage your telemetry data sources using the Scaleway-supported Mimir and Loki endpoints
+  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
 content:
-  h1: Cockpit supported API endpoints
-  paragraph: Discover how to manage your telemetry data sources using the Scaleway-supported Mimir and Loki endpoints
-tags: observability cockpit endpoints mimir loki telemetry
+  h1: Cockpit supported API endpoints for data source management
+  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
@@ -18,7 +18,7 @@ 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 for the alert manager
+- [Prometheus](https://grafana.com/oss/prometheus/) for the alert manager
 
 Cockpit exposes a subset of their HTTP APIs so users can push, query, and manage telemetry data from Cockpit.
 
@@ -42,45 +42,45 @@ The base URL pattern for metrics is the following: `https://<data-source-id>.met
 
     Method: `POST`.
 
-    Path: `/api/v1/push`
-    Path: `/otlp/v1/metrics`
+    - Path: `/api/v1/push`
+    - Path: `/otlp/v1/metrics`
 </Concept>
 
 <Concept>
   ## 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`
+    - 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`
 </Concept>
 
 <Concept>
   ## 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/*`
+    - Path: `/prometheus/api/v1/rules`
+    - Path: `/prometheus/api/v1/alerts`
+    - Path: `/prometheus/config/v1/rules`
+    - 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`
+    - Path: `/ruler/delete_tenant_config`
+    - Path: `/compactor/delete_tenant`
+    - Path: `/compactor/delete_tenant_status`
 </Concept>
 
 
@@ -93,35 +93,35 @@ The base URL pattern for logs is the following: `https://<data-source-id>.logs.c
 
     Method: `POST`.
 
-    Path: /loki/api/v1/push
-    Path: /otlp/v1/logs
+    - Path: `/loki/api/v1/push`
+    - Path: `/otlp/v1/logs`
 </Concept>
 
 <Concept>
   ## 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
+    - 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`
 </Concept>
 
 <Concept>
   ## 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
+    - 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`
 </Concept>
 
 ## Tempo supported endpoints (traces)
@@ -133,29 +133,29 @@ The base URL pattern for traces is the following: `https://<data-source-id>.trac
 
     Method: `POST`.
 
-    path /otlp/v1/traces
-    path /opentelemetry.proto.collector.trace.v1.TraceService/Export
-    path /jaeger
-    path /zipkin
+    - Path: `/otlp/v1/traces`
+    - Path: `/opentelemetry.proto.collector.trace.v1.TraceService/Export`
+    - Path: `/jaeger`
+    - Path: `/zipkin`
 </Concept>
 
 <Concept>
   ## 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
+    - 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`
 </Concept>
 
 ## Pometheus supported endpoints
 
-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 your data source is located (`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`).
 
 <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.
@@ -166,16 +166,16 @@ The base URL pattern for the alert manager is the following: `https://<data-sour
 
     Methods: `GET`, `POST`, and `DELETE`.
 
-    Path: /alertmanager/*
-    Path: /api/v1/alerts
+    - Path: `/alertmanager/*`
+    - Path: `/api/v1/alerts`
 </Concept>
 
 <Concept>
   ## Alert manager admin endpoints
 
     Method: `POST`.
 
-    Path: /multitenant_alertmanager/delete_tenant_config
+    Path: `/multitenant_alertmanager/delete_tenant_config`
 </Concept>