From 87610ff5198f8a77701a80fd2a25cb957824000d Mon Sep 17 00:00:00 2001 From: liudmila molkova Date: Mon, 24 Nov 2025 18:38:12 -0800 Subject: [PATCH] Fix link to DB semconv --- specification/trace/api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification/trace/api.md b/specification/trace/api.md index e1ebccf6285..2efaa18459e 100644 --- a/specification/trace/api.md +++ b/specification/trace/api.md @@ -764,7 +764,7 @@ are built and instrumented. [Semantic conventions](../overview.md#semantic-conventions) for specific technologies should document kind for each span they define. -For instance, [Database Client Semantic Conventions](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/database/database-spans.md) +For instance, [Database Client Semantic Conventions](https://opentelemetry.io/docs/specs/semconv/database/database-spans/) recommend using `CLIENT` span kind to describes database calls. If the database client communicates to the server over HTTP, the HTTP instrumentation (when enabled) creates nested `CLIENT` spans to track individual