From f1ae8d75fefc16a285b69cf7b1afb827e817903f Mon Sep 17 00:00:00 2001 From: nerda-codes Date: Thu, 24 Apr 2025 10:26:33 +0200 Subject: [PATCH 1/4] docs(add): endpts part 1 --- .../cockpit-supported-endpoints.mdx | 113 ++++++++++++++++++ 1 file changed, 113 insertions(+) create mode 100644 pages/cockpit/reference-content/cockpit-supported-endpoints.mdx diff --git a/pages/cockpit/reference-content/cockpit-supported-endpoints.mdx b/pages/cockpit/reference-content/cockpit-supported-endpoints.mdx new file mode 100644 index 0000000000..7a177325b9 --- /dev/null +++ b/pages/cockpit/reference-content/cockpit-supported-endpoints.mdx @@ -0,0 +1,113 @@ +--- +meta: + title: Cockpit supported API endpoints + description: Discover how to manage your telemetry data sources using the Scaleway-supported Mimir and Loki 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 +dates: + validation: 2025-05-17 + posted: 2025-05-17 +categories: + - observability +--- + +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 Alertmanager for alerting. + +Cockpit exposes a subset of their HTTP APIs so users can push, query, and manage telemetry data from Cockpit. + + + Scaleway does not support all endpoints from these upstream APIs. refer to the exact lists below to find out which endpoints are supported. + + + + + - 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 + - [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://.metrics.cockpit..scw.cloud`. + + + ### Mimir remote write endpoints + + method GET POST DELETE + + Path: `/api/v1/push` + Path: `/otlp/v1/metrics` + + ### Mimir query endpoints + 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 + + # Ruler endpoints + path /prometheus/api/v1/rules + path /prometheus/api/v1/alerts + path /prometheus/config/v1/rules + path /prometheus/config/v1/rules/* + + # Admin endpoints + path /ruler/delete_tenant_config + path /compactor/delete_tenant + path /compactor/delete_tenant_status + } + + @mimir_write_endpoints { + method POST + path /api/v1/push + path /otlp/v1/metrics + } + + @mimir_query_endpoints { + method GET 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 + } + + @mimir_rules_endpoints { + method GET POST DELETE + path /prometheus/api/v1/rules + path /prometheus/api/v1/alerts + path /prometheus/config/v1/rules + path /prometheus/config/v1/rules/* + } + + @mimir_admin_endpoints { + method GET POST + path /ruler/delete_tenant_config + path /compactor/delete_tenant + path /compactor/delete_tenant_status + } + + @mimir_query_range_endpoints { + method GET POST + path /prometheus/api/v1/query_range + } + + @mimir_ruler_write_endpoints { + method POST DELETE + + From 98f5f955992c3e6323bd4b8dd9eb5e385c6c2ad9 Mon Sep 17 00:00:00 2001 From: nerda-codes Date: Fri, 25 Apr 2025 10:48:51 +0200 Subject: [PATCH 2/4] docs(add): all endpoints --- .../cockpit-supported-endpoints.mdx | 206 ++++++++++++------ 1 file changed, 137 insertions(+), 69 deletions(-) diff --git a/pages/cockpit/reference-content/cockpit-supported-endpoints.mdx b/pages/cockpit/reference-content/cockpit-supported-endpoints.mdx index 7a177325b9..2146d04e5a 100644 --- a/pages/cockpit/reference-content/cockpit-supported-endpoints.mdx +++ b/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 and Loki endpoints tags: observability cockpit endpoints mimir loki telemetry dates: - validation: 2025-05-17 - posted: 2025-05-17 + validation: 2025-04-25 + posted: 2025-04-25 categories: - observability --- @@ -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 Alertmanager for alerting. +- Prometheus for the alert manager Cockpit exposes a subset of their HTTP APIs so users can push, query, and manage telemetry data from Cockpit. @@ -35,79 +35,147 @@ Cockpit exposes a subset of their HTTP APIs so users can push, query, and manage ## Mimir supported endpoints (metrics) -The base URL pattern for metrics is the following: `https://.metrics.cockpit..scw.cloud`. +The base URL pattern for metrics is the following: `https://.metrics.cockpit..scw.cloud`. You must replace `` with the ID of your data source and `` with the region where your data source is located (`fr-par`, `nl-ams`, or `pl-waw`). + + ## Mimir write endpoints - ### Mimir remote write endpoints - - method GET POST DELETE + Method: `POST`. Path: `/api/v1/push` Path: `/otlp/v1/metrics` + - ### Mimir query endpoints - 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 - - # Ruler endpoints - path /prometheus/api/v1/rules - path /prometheus/api/v1/alerts - path /prometheus/config/v1/rules - path /prometheus/config/v1/rules/* - - # Admin endpoints - path /ruler/delete_tenant_config - path /compactor/delete_tenant - path /compactor/delete_tenant_status - } - - @mimir_write_endpoints { - method POST - path /api/v1/push - path /otlp/v1/metrics - } - - @mimir_query_endpoints { - method GET 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 - } - - @mimir_rules_endpoints { - method GET POST DELETE + + ## 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` + + + + ## 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/*` + + + + ## Mimir admin endpoints + + Methods: `GET` and `POST`. + + Path: `/ruler/delete_tenant_config` + Path: `/compactor/delete_tenant` + Path: `/compactor/delete_tenant_status` + + + +## Loki supported endpoints (logs) + +The base URL pattern for logs is the following: `https://.logs.cockpit..scw.cloud`. You must replace `` with the ID of your data source and `` with the region where your data source is located (`fr-par`, `nl-ams`, or `pl-waw`). + + + ## Loki write endpoints + + Method: `POST`. + + Path: /loki/api/v1/push + Path: /otlp/v1/logs + + + + ## 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 + + + + ## 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 /prometheus/config/v1/rules - path /prometheus/config/v1/rules/* - } - - @mimir_admin_endpoints { - method GET POST - path /ruler/delete_tenant_config - path /compactor/delete_tenant - path /compactor/delete_tenant_status - } - - @mimir_query_range_endpoints { - method GET POST - path /prometheus/api/v1/query_range - } - - @mimir_ruler_write_endpoints { - method POST DELETE + + +## Tempo supported endpoints (traces) + +The base URL pattern for traces is the following: `https://.traces.cockpit..scw.cloud`. You must replace `` with the ID of your data source and `` with the region where your data source is located (`fr-par`, `nl-ams`, or `pl-waw`). + + + ## Tempo write endpoints + + Method: `POST`. + + path /otlp/v1/traces + path /opentelemetry.proto.collector.trace.v1.TraceService/Export + path /jaeger + path /zipkin + + + + ## 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 + + +## Pometheus supported endpoints + +The base URL pattern for the alert manager is the following: `https://.alertmanager.cockpit..scw.cloud`. You must replace `` with the ID of your data source and `` with the region where your data source is located (`fr-par`, `nl-ams`, or `pl-waw`). + + + 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. + + + + ## Alert manager endpoints + + Methods: `GET`, `POST`, and `DELETE`. + + Path: /alertmanager/* + Path: /api/v1/alerts + + + + ## Alert manager admin endpoints + + Method: `POST`. + + Path: /multitenant_alertmanager/delete_tenant_config + From cee331cdfe37be357559d71626042925cb8e9368 Mon Sep 17 00:00:00 2001 From: nerda-codes Date: Fri, 25 Apr 2025 14:48:55 +0200 Subject: [PATCH 3/4] docs(cpt): add menu --- menu/navigation.json | 4 + .../cockpit-supported-endpoints.mdx | 108 +++++++++--------- 2 files changed, 58 insertions(+), 54 deletions(-) diff --git a/menu/navigation.json b/menu/navigation.json index e347a21d35..b9244d4c7d 100644 --- a/menu/navigation.json +++ b/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", diff --git a/pages/cockpit/reference-content/cockpit-supported-endpoints.mdx b/pages/cockpit/reference-content/cockpit-supported-endpoints.mdx index 2146d04e5a..23a363a7e2 100644 --- a/pages/cockpit/reference-content/cockpit-supported-endpoints.mdx +++ b/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,8 +42,8 @@ The base URL pattern for metrics is the following: `https://.met Method: `POST`. - Path: `/api/v1/push` - Path: `/otlp/v1/metrics` + - Path: `/api/v1/push` + - Path: `/otlp/v1/metrics` @@ -51,15 +51,15 @@ The base URL pattern for metrics is the following: `https://.met 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` @@ -67,10 +67,10 @@ The base URL pattern for metrics is the following: `https://.met 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/*` @@ -78,9 +78,9 @@ The base URL pattern for metrics is the following: `https://.met 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` @@ -93,8 +93,8 @@ The base URL pattern for logs is the following: `https://.logs.c Method: `POST`. - Path: /loki/api/v1/push - Path: /otlp/v1/logs + - Path: `/loki/api/v1/push` + - Path: `/otlp/v1/logs` @@ -102,13 +102,13 @@ The base URL pattern for logs is the following: `https://.logs.c 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` @@ -116,12 +116,12 @@ The base URL pattern for logs is the following: `https://.logs.c 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` ## Tempo supported endpoints (traces) @@ -133,10 +133,10 @@ The base URL pattern for traces is the following: `https://.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` @@ -144,18 +144,18 @@ The base URL pattern for traces is the following: `https://.trac 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` ## Pometheus supported endpoints -The base URL pattern for the alert manager is the following: `https://.alertmanager.cockpit..scw.cloud`. You must replace `` with the ID of your data source and `` 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://.alertmanager.cockpit..scw.cloud`. You must replace `` with the ID of your data source and `` with the region where the alert manager is enabled (`fr-par`, `nl-ams`, or `pl-waw`). 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,8 +166,8 @@ The base URL pattern for the alert manager is the following: `https:// @@ -175,7 +175,7 @@ The base URL pattern for the alert manager is the following: `https:// From cd85591345db2b7fbd9fb0a52eaa366a1c37823d Mon Sep 17 00:00:00 2001 From: nerda-codes Date: Mon, 5 May 2025 14:59:44 +0200 Subject: [PATCH 4/4] docs(cpt): feedback --- .../cockpit-supported-endpoints.mdx | 46 +++++++------------ 1 file changed, 17 insertions(+), 29 deletions(-) diff --git a/pages/cockpit/reference-content/cockpit-supported-endpoints.mdx b/pages/cockpit/reference-content/cockpit-supported-endpoints.mdx index 23a363a7e2..2c245a01b0 100644 --- a/pages/cockpit/reference-content/cockpit-supported-endpoints.mdx +++ b/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,18 +18,18 @@ 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. - 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. - 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) @@ -37,6 +37,8 @@ Cockpit exposes a subset of their HTTP APIs so users can push, query, and manage The base URL pattern for metrics is the following: `https://.metrics.cockpit..scw.cloud`. You must replace `` with the ID of your data source and `` 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. + ## Mimir write endpoints @@ -73,21 +75,13 @@ The base URL pattern for metrics is the following: `https://.met - Path: `/prometheus/config/v1/rules/*` - - ## Mimir admin endpoints - - Methods: `GET` and `POST`. - - - Path: `/ruler/delete_tenant_config` - - Path: `/compactor/delete_tenant` - - Path: `/compactor/delete_tenant_status` - - ## Loki supported endpoints (logs) The base URL pattern for logs is the following: `https://.logs.cockpit..scw.cloud`. You must replace `` with the ID of your data source and `` 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. + ## Loki write endpoints @@ -128,6 +122,8 @@ The base URL pattern for logs is the following: `https://.logs.c The base URL pattern for traces is the following: `https://.traces.cockpit..scw.cloud`. You must replace `` with the ID of your data source and `` 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. + ## Tempo write endpoints @@ -153,12 +149,14 @@ The base URL pattern for traces is the following: `https://.trac - Path: `/api/v2/search/tag/*/values` -## Pometheus supported endpoints +## Prometheus alert manager supported endpoints + +The base URL pattern for the alert manager is the following: `https://.alertmanager.cockpit..scw.cloud`. You must replace `` with the ID of your alert manager and `` 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://.alertmanager.cockpit..scw.cloud`. You must replace `` with the ID of your data source and `` 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. - 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. @@ -168,14 +166,4 @@ The base URL pattern for the alert manager is the following: `https:// - - - ## Alert manager admin endpoints - - Method: `POST`. - - Path: `/multitenant_alertmanager/delete_tenant_config` - - - + \ No newline at end of file