From f6f4a999803f58b669289248915fd0c779b763ed Mon Sep 17 00:00:00 2001 From: Liudmila Molkova Date: Mon, 8 Jul 2024 12:48:34 -0700 Subject: [PATCH] lint --- docs/dotnet/dotnet-network-traces.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/dotnet/dotnet-network-traces.md b/docs/dotnet/dotnet-network-traces.md index 65080bbc6a..af5a5adcf6 100644 --- a/docs/dotnet/dotnet-network-traces.md +++ b/docs/dotnet/dotnet-network-traces.md @@ -14,8 +14,8 @@ This article defines semantic conventions for HTTP client, DNS and TLS spans emi - [HTTP client request: wait for connection](#http-client-request-wait-for-connection) - [HTTP connection setup](#http-connection-setup) - [Socket connect](#socket-connect) -- [DNS](#dns-resolution) -- [TLS](#tls-handshake) +- [DNS resolution](#dns-resolution) +- [TLS handshake](#tls-handshake) - [Examples](#examples) - [HTTP request was performed on a connection that was immediately available](#http-request-was-performed-on-a-connection-that-was-immediately-available) - [HTTP request has to wait for connection setup](#http-request-has-to-wait-for-connection-setup) @@ -96,7 +96,6 @@ The time it takes to get a connection from the pool is also reported by the The span describes the establishment of the HTTP connection. It includes the time it takes to resolve the DNS, establish the socket connection, and perform the TLS handshake. - Span name SHOULD be `HTTP connection_setup {address}:{server.port}`. The `{address}` SHOULD be `server.address` when it's available and `network.peer.address` otherwise.