open-telemetry
/
semantic-conventions
mirror of https://github.com/open-telemetry/semantic-conventions.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Remove outdated `http.request.header.host` guidance (#479) 

Co-authored-by: Alexander Wert <AlexanderWert@users.noreply.github.com>
This commit is contained in:
Trask Stalnaker 2023-11-01 01:09:56 -07:00 committed by GitHub
parent 69d6d4fd67
commit 1eb70c4d74
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
CHANGELOG.md
View File

@ -50,6 +50,8 @@ release.
([#469](https://github.com/open-telemetry/semantic-conventions/pull/469)) ([#469](https://github.com/open-telemetry/semantic-conventions/pull/469))
- Change `network.protocol.name` from opt-in to conditionally required. - Change `network.protocol.name` from opt-in to conditionally required.
([#478](https://github.com/open-telemetry/semantic-conventions/pull/478)) ([#478](https://github.com/open-telemetry/semantic-conventions/pull/478))
- Remove outdated `http.request.header.host` guidance
([#479](https://github.com/open-telemetry/semantic-conventions/pull/479))
### Features ### Features

4
docs/http/http-spans.md
View File

@ -256,8 +256,6 @@ Following attributes MUST be provided **at span creation time** (when provided a
* [`url.full`](../attributes-registry/url.md) * [`url.full`](../attributes-registry/url.md)
<!-- endsemconv --> <!-- endsemconv -->
Note that in some cases host and port identifiers in the `Host` header might be different from the `server.address` and `server.port`, in this case instrumentation MAY populate `Host` header on `http.request.header.host` attribute even if it's not enabled by user.
### HTTP client span duration ### HTTP client span duration
There are some minimal constraints that SHOULD be honored: There are some minimal constraints that SHOULD be honored:
@ -380,8 +378,6 @@ Following attributes MUST be provided **at span creation time** (when provided a
`http.route` MUST be provided at span creation time if and only if it's already available. If it becomes available after span starts, instrumentation MUST populate it anytime before span ends. `http.route` MUST be provided at span creation time if and only if it's already available. If it becomes available after span starts, instrumentation MUST populate it anytime before span ends.
Note that in some cases host and port identifiers in the `Host` header might be different from the `server.address` and `server.port`, in this case instrumentation MAY populate `Host` header on `http.request.header.host` attribute even if it's not enabled by user.
## Examples ## Examples
### HTTP client-server example ### HTTP client-server example