From 03a5e6673956ea83b2536489b80f894bef86dd66 Mon Sep 17 00:00:00 2001 From: klauco Date: Mon, 6 May 2024 22:38:14 +0200 Subject: [PATCH] span kind specification Co-authored-by: Trask Stalnaker --- docs/http/http-spans.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/http/http-spans.md b/docs/http/http-spans.md index fef055fefd..33dd4832df 100644 --- a/docs/http/http-spans.md +++ b/docs/http/http-spans.md @@ -83,7 +83,7 @@ In other cases (when `{http.request.method}` is set to `_OTHER`), `{method}` MUS The `{target}` SHOULD be one of the following: - [`http.route`](/docs/attributes-registry/http.md) for HTTP Server spans -- [`url.template`](/docs/attributes-registry/url.md) if enabled and available (![Experimental](https://img.shields.io/badge/-experimental-blue)) +- [`url.template`](/docs/attributes-registry/url.md) for HTTP Client spans if enabled and available (![Experimental](https://img.shields.io/badge/-experimental-blue)) - Other value MAY be provided through custom hooks at span start time or later. Instrumentation MUST NOT default to using URI path as a `{target}`.