From 8bcd3642c327ceef654f7caa10ec40bc5ddd0436 Mon Sep 17 00:00:00 2001 From: "Eric D. Schabell" Date: Fri, 20 Mar 2026 20:53:20 +0100 Subject: [PATCH] docs: inputs: opentelemetry: update metrics HTTP1/JSON support status and classic config examples - Update the transport protocol support matrix to reflect that HTTP/1.1 JSON is now Stable for metrics, added in commits 4a844c98b, f90bf0d7a, and e8ab3ab62 - Fix classic .conf example to use Title_Case config parameter keys Fixes #2496 Signed-off-by: Eric D. Schabell --- pipeline/inputs/opentelemetry.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/pipeline/inputs/opentelemetry.md b/pipeline/inputs/opentelemetry.md index 6ab0efe9f..721a0d00c 100644 --- a/pipeline/inputs/opentelemetry.md +++ b/pipeline/inputs/opentelemetry.md @@ -98,7 +98,7 @@ The OpenTelemetry input plugin supports the following telemetry data types: | Type | HTTP1/JSON | HTTP1/Protobuf | HTTP2/gRPC | |---------|---------------|----------------|------------| | Logs | Stable | Stable | Stable | -| Metrics | Unimplemented | Stable | Stable | +| Metrics | Stable | Stable | Stable | | Traces | Stable | Stable | Stable | A sample configuration file to get started will look something like the following: @@ -123,13 +123,13 @@ pipeline: ```text [INPUT] - name opentelemetry - listen 127.0.0.1 - port 4318 + Name opentelemetry + Listen 127.0.0.1 + Port 4318 [OUTPUT] - name stdout - match * + Name stdout + Match * ``` {% endtab %}