cdaccc8e4a
Moved HTTP semantic conventions to a dedicated topic-based structure ( #141 )
2023-06-28 08:14:15 -07:00
2055854c0c
Change `server.address` and `server.port` from required to recommended on HTTP Server Spans ( #114 )
2023-06-21 16:01:51 -07:00
be0fab156d
Limit HTTP request method cardinality: original_method (option A) ( #17 )
2023-06-20 09:20:14 -07:00
d31b014b1f
Make `url.query` conditionally required for HTTP spans ( #118 )
2023-06-19 10:34:08 -07:00
614dbefc77
BREAKING: Introduce common `url.*` attributes, and improve use of namespacing under `http.*` ( #3355 )
2023-05-08 19:55:53 -07:00
9e3e528ccc
BREAKING: Rename remaining network attributes from `net.*` to `network.*` and align definitions with ECS ( #3426 )
2023-05-08 17:46:55 -07:00
5b8861e8c5
BREAKING: Replace `net.peer.*`/`net.host.*` with `client.*`/`server.*` (and `source.*`/`destination.*`) ( #3402 )
2023-05-08 16:19:51 -07:00
40a91717ba
Show relationship between http target and route in example usage ( #3292 )
...
## Changes
Clarify relationship between `http.target` and `http.route` by using the
same pattern in the example usage. Having different patterns for the
attribute values distorts the relationship between the two attributes.
A similar pattern is seen in the docs for
[`aws-lambda.md`](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/instrumentation/aws-lambda.md#api-gateway-request-proxy-lambda-tracing-passive ),
where `http.target` is `/pets/10` and `http.route` is `/pets/{petId}`.
It's a minor adjustment but should help provide clarity for new users.
---------
Co-authored-by: Joshua MacDonald <jmacd@users.noreply.github.com>
2023-03-08 09:12:28 -08:00
489fea52c8
net.peer.name clarification for HTTP client semconv ( #3276 )
...
Fixes #3273
## Changes
Clarifies that if an HTTP client request is explicitly made to an IP
address, e.g. `http://x.x.x.x:8080 `, then
`net.peer.name` SHOULD be the IP address `x.x.x.x`.
2023-03-06 09:33:35 -06:00
6d7b233c80
Rename http.user_agent to user_agent.original ( #3190 )
...
Fixes #3180
## Changes
Renames `http.user_agent` to `user_agent.original`.
2023-03-02 14:47:29 -06:00
47cabcf799
Rename Optional attribute requirement level to Opt-In ( #3228 )
2023-03-01 15:13:24 -08:00
3a0a197f4c
Use attribute_group for cross-signal HTTP attributes ( #3183 )
2023-02-13 16:00:14 -08:00
2165c692f9
Http route should contain application root ( #3164 )
2023-02-06 12:50:01 -08:00
34093ed204
Clarify the HTTP client `http.retry_count` spec ( #2743 )
2022-10-18 10:46:16 -07:00
298c566cf9
Remove alternative attribute sets from HTTP semantic conventions ( #2469 )
2022-07-27 11:31:21 -07:00
6a3df0d52d
Add 'type' to all groups ( #2693 )
2022-07-27 11:30:47 +02:00
216beba6cc
Define net.sock attributes and clarify logical net.peer|host.name attributes ( #2614 )
2022-07-13 10:01:44 -07:00
3f7b7d02f9
Adopt attribute requirement levels in semantic conventions ( #2594 )
2022-06-14 08:02:55 -07:00
6d6aa8df6e
Add HTTP/3 ( #2507 )
2022-04-27 14:09:05 -07:00
fc0090a6ef
Move net.peer.name from http common to http client ( #2446 )
2022-04-01 22:29:15 -07:00
20fda6a90e
Define span structure for HTTP retries and redirects ( #2078 )
...
This PR clarifies semantic conventions for HTTP retries and redirects and defines a span structure and linking as well as span attributes for retries. Changes were discussed recently at Instrumentation SIG meetings.
This change addresses a scenario which is in the scope for bringing the existing HTTP semantic conventions for tracing to an initial stable state, see related [otep #174 ](https://github.com/open-telemetry/oteps/pull/174 ).
2022-03-08 20:22:45 -05:00
8c7fb44a4e
Define HTTP attributes that should be provided at span creation time ( #1916 )
2021-10-14 14:49:14 +02:00
30fed0f050
Clarify some cases for http.host and http.client_ip. ( #1890 )
...
* Clarify some cases for http.host and http.client_ip.
* Fill in PR#.
2021-09-07 19:18:49 +00:00
3fffd053af
Consistently format enums, fix non-identifier IDs. ( #1863 )
2021-08-20 16:12:03 +02:00
1b0a64202d
Lint YAML files (mainly semantic conventions). ( #1814 )
...
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2021-07-15 10:12:05 +02:00
ecec5145dc
Remove examples from enums. ( #1779 )
2021-06-29 12:54:59 -07:00
561ad88d7f
Update semantic conventions to distinguish int from double ( #1550 )
2021-03-18 17:06:10 +01:00
c3d71dffc8
http.url MUST NOT contain credentials ( #1502 )
2021-03-05 15:20:04 +01:00
f6cd4c2e1a
Remove obsolete `http.status_text` from semantic conventions ( #972 )
2020-09-22 11:49:09 +02:00
521dfd99aa
YAML Model for Semantic Conventions ( #571 )
...
* First model draft
* Fix checkstyle
* Generate network table from YAML
* HTTP semantic convention tables
* Fix requirements order
* Add code and basic documentation
* Missing \n
* Remove tool
* Add General and HTTP semantic convention
* Update table style
* yaml->semantic_conventions
* Fix small errors
* Fix docfx errors
* Update Makefile to use otel Docker repo
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
2020-08-27 13:18:51 -07:00
Alexander Wert