From 1a40807ab63ec593b346bd04b73471ac35e8b195 Mon Sep 17 00:00:00 2001 From: Cyrille Le Clerc Date: Tue, 22 Mar 2022 09:51:46 +0100 Subject: [PATCH] Fix asciidoc hyperlink syntax --- docs/open-telemetry.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/open-telemetry.asciidoc b/docs/open-telemetry.asciidoc index e5545f114a5..70dd554a723 100644 --- a/docs/open-telemetry.asciidoc +++ b/docs/open-telemetry.asciidoc @@ -415,4 +415,4 @@ Here is an example of AWS Lambda Node.js function managed with Terraform and the [[open-telemetry-otlp-limitations]] ===== OpenTelemetry Line Protocol (OTLP) -* The [OTLP/HTTP protocol](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/otlp.md#otlphttp) is not yet supported by Elastic, use [OTLP/gRPC protocol](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/otlp.md#otlpgrpc). If architecture constraints require to use HTTP rather than gRPC on some segments of the network, please consider deploying an OpenTelemetry Collector to convert OTLP/HTTP to OTLP/gRPC to send those signals to Elastic. +* The https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/otlp.md#otlphttp[OTLP/HTTP protocol] is not yet supported by Elastic, use https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/otlp.md#otlpgrpc[OTLP/gRPC protocol]. If architecture constraints require to use HTTP rather than gRPC on some segments of the network, please consider deploying an OpenTelemetry Collector to convert OTLP/HTTP to OTLP/gRPC to send those signals to Elastic.