From 9ac8f701d692cceccea294fd99e9172b8c029fcd Mon Sep 17 00:00:00 2001 From: Liudmila Molkova Date: Tue, 5 Sep 2023 14:36:46 -0700 Subject: [PATCH] clean up --- docs/http/http-spans.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/http/http-spans.md b/docs/http/http-spans.md index d3abf48a99..452627536a 100644 --- a/docs/http/http-spans.md +++ b/docs/http/http-spans.md @@ -63,17 +63,17 @@ and various HTTP versions like 1.1, 2 and SPDY. HTTP spans MUST follow the overall [guidelines for span names](https://github.com/open-telemetry/opentelemetry-specification/tree/v1.22.0/specification/trace/api.md#span). -HTTP server span names SHOULD be `{method} {http.route}` (see below for the exact definition of the `{method}` placeholder) if there is a -(low-cardinality) `http.route` available, +HTTP server span names SHOULD be `{method} {http.route}` if there is a +(low-cardinality) `http.route` available (see below for the exact definition of the [`{method}`](#method-placeholder) placeholder). If there is no (low-cardinality) `http.route` available, HTTP server span names -SHOULD be `{method}` (see below for the exact definition of the `{method}` placeholder) +SHOULD be [`{method}`](#method-placeholder). HTTP client spans have no `http.route` attribute since client-side instrumentation is not generally aware of the "route", and therefore HTTP client spans SHOULD be -`{method}`. +[`{method}`](#method-placeholder). -The `{method}` MUST be `{http.request.method}` if the method represents the original method known to the instrumentation. +The `{method}` MUST be `{http.request.method}` if the method represents the original method known to the instrumentation. In other cases (when `{http.request.method}` is set to `_OTHER`), `{method}` MUST be `HTTP`. Instrumentation MUST NOT default to using URI