From 95d97fbcfa80e844527d314b33263e45df191c84 Mon Sep 17 00:00:00 2001 From: Maurizio Branca Date: Wed, 5 Aug 2026 18:31:58 +0200 Subject: [PATCH 1/2] Document managed PRW support on ECH --- .../managed-inputs/prometheus-remote-write.md | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/docs/reference/managed-inputs/prometheus-remote-write.md b/docs/reference/managed-inputs/prometheus-remote-write.md index 374ff44c..c595250a 100644 --- a/docs/reference/managed-inputs/prometheus-remote-write.md +++ b/docs/reference/managed-inputs/prometheus-remote-write.md @@ -5,8 +5,11 @@ applies_to: serverless: observability: ga security: ga + deployment: + ech: ga products: - id: cloud-serverless + - id: cloud-hosted - id: observability --- @@ -16,21 +19,21 @@ The Managed Prometheus Remote Write endpoint ingests metrics sent in the [Promet ## When to use the Managed Prometheus Remote Write endpoint -For {{serverless-full}} projects, the Managed Prometheus Remote Write endpoint is the recommended way to ingest Prometheus metrics. Compared to sending metrics directly to the [{{es}} Prometheus Remote Write endpoint](docs-content://manage-data/data-store/data-streams/tsds-ingest-prometheus-remote-write.md), it provides: +For {{serverless-full}} projects and {{ech}} deployments, the Managed Prometheus Remote Write endpoint is the recommended way to ingest Prometheus metrics. Compared to sending metrics directly to the [{{es}} Prometheus Remote Write endpoint](docs-content://manage-data/data-store/data-streams/tsds-ingest-prometheus-remote-write.md), it provides: - A single ingest endpoint and API key shared with the other [managed inputs](index.md). - Durable buffering, back-pressure, and retry on `429 Too Many Requests`. - The same Prometheus-to-TSDS mapping as the {{es}} PRW endpoint, so the resulting data is identical. :::{warning} -On {{serverless-full}}, use the Managed Prometheus Remote Write endpoint rather than sending metrics directly to the [{{es}} Prometheus Remote Write endpoint](docs-content://manage-data/data-store/data-streams/tsds-ingest-prometheus-remote-write.md). +On {{serverless-full}} and {{ech}}, use the Managed Prometheus Remote Write endpoint rather than sending metrics directly to the [{{es}} Prometheus Remote Write endpoint](docs-content://manage-data/data-store/data-streams/tsds-ingest-prometheus-remote-write.md). -Direct ingest bypasses managed inputs and has no buffering or processing before data reaches {{es}}. It also authenticates differently: the direct {{es}} endpoint uses {{es}} credentials or an API key with index privileges, while the Managed Prometheus Remote Write endpoint uses an API key with the `event:write` privilege for the `apm` application. Use the direct {{es}} endpoint only for self-managed deployments, where managed inputs aren't available. {{ech}} support for the Managed Prometheus Remote Write endpoint is planned. +Direct ingest bypasses managed inputs and has no buffering or processing before data reaches {{es}}. It also authenticates differently: the direct {{es}} endpoint uses {{es}} credentials or an API key with index privileges, while the Managed Prometheus Remote Write endpoint uses an API key with the `event:write` privilege for the `apm` application. Use the direct {{es}} endpoint only for self-managed deployments, where managed inputs aren't available. ::: ## Prerequisites -- An {{serverless-full}} Observability or Security project. +- An {{serverless-full}} Observability or Security project, or an {{ech}} deployment. - An API key with the `event:write` privilege for the `apm` application. Refer to [Authentication](authentication-delivery-and-failure-handling.md#authentication) for the required key format and generation steps. ## Send Prometheus metrics through managed inputs @@ -54,7 +57,9 @@ remote_write: To find ``: 1. Log in to the {{ecloud}} Console. -2. Find your project and select **Manage**. +2. Do one of the following: + - **{{serverless-full}}**: Find your project and select **Manage**. + - **{{ech}}**: Find your deployment in **Hosted deployments** and select **Manage**. 3. In the **Application endpoints, cluster and component IDs** section, select **Prometheus**. 4. Copy the **Prometheus** endpoint value, which looks similar to `https://.ingest...elastic.cloud/api/v1/write` @@ -110,5 +115,4 @@ For back-pressure and `429` responses, refer to [Managed inputs rate limiting](r ## Limitations - URL-path routing (for example, `/_prometheus/metrics/{dataset}/api/v1/write`) to custom data streams is not supported through managed inputs. Use [label-based routing](docs-content://manage-data/data-store/data-streams/tsds-ingest-prometheus-remote-write.md#route-by-labels) instead. -- Available on {{serverless-full}} only. - Samples with non-finite values (NaN, Infinity) are silently dropped by {{es}}, and staleness markers are not supported. From ddcdf27971f98419de63a3e77beaebc99e721591 Mon Sep 17 00:00:00 2001 From: Maurizio Branca Date: Thu, 6 Aug 2026 10:33:09 +0200 Subject: [PATCH 2/2] Add security as product --- docs/reference/managed-inputs/prometheus-remote-write.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/reference/managed-inputs/prometheus-remote-write.md b/docs/reference/managed-inputs/prometheus-remote-write.md index c595250a..d9cae4d6 100644 --- a/docs/reference/managed-inputs/prometheus-remote-write.md +++ b/docs/reference/managed-inputs/prometheus-remote-write.md @@ -11,6 +11,7 @@ products: - id: cloud-serverless - id: cloud-hosted - id: observability + - id: security --- # Ingest Prometheus metrics with the Managed Prometheus Remote Write endpoint [prometheus-remote-write]