You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/database/elasticsearch.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,8 +58,9 @@ with the endpoint identifier stored in `db.operation.name`, and the index stored
58
58
For batch operations, if the individual operations are known to have the same operation name then that operation name SHOULD be used prepended by `bulk `, otherwise `db.operation.name` SHOULD be `bulk`.
59
59
60
60
**[2]`http.request.method`:** HTTP request method value SHOULD be "known" to the instrumentation.
61
-
By default, this convention defines "known" methods as the ones listed in [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-methods)
62
-
and the PATCH method defined in [RFC5789](https://www.rfc-editor.org/rfc/rfc5789.html).
61
+
By default, this convention defines "known" methods as the ones listed in [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-methods),
62
+
the PATCH method defined in [RFC5789](https://www.rfc-editor.org/rfc/rfc5789.html)
63
+
and the QUERY method defined in [httpbis-safe-method-w-body](https://datatracker.ietf.org/doc/draft-ietf-httpbis-safe-method-w-body/?include_text=1).
63
64
64
65
If the HTTP request method is not known to instrumentation, it MUST set the `http.request.method` attribute to `_OTHER`.
65
66
@@ -159,6 +160,7 @@ and SHOULD be provided **at span creation time** (if provided at all):
|[`user_agent.synthetic.type`](/docs/registry/attributes/user-agent.md)| string | Specifies the category of synthetic traffic, such as tests or bots. [10]|`bot`; `test`|`Opt-In`||
93
93
94
94
**[1]`http.request.method`:** HTTP request method value SHOULD be "known" to the instrumentation.
95
-
By default, this convention defines "known" methods as the ones listed in [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-methods)
96
-
and the PATCH method defined in [RFC5789](https://www.rfc-editor.org/rfc/rfc5789.html).
95
+
By default, this convention defines "known" methods as the ones listed in [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-methods),
96
+
the PATCH method defined in [RFC5789](https://www.rfc-editor.org/rfc/rfc5789.html)
97
+
and the QUERY method defined in [httpbis-safe-method-w-body](https://datatracker.ietf.org/doc/draft-ietf-httpbis-safe-method-w-body/?include_text=1).
97
98
98
99
If the HTTP request method is not known to instrumentation, it MUST set the `http.request.method` attribute to `_OTHER`.
99
100
@@ -169,6 +170,7 @@ SHOULD include the [application root](/docs/http/http-spans.md#http-server-defin
|[`server.port`](/docs/registry/attributes/server.md)| int | Port of the local HTTP server that received the request. [3]|`80`; `8080`; `443`|`Opt-In`||
209
211
210
212
**[1]`http.request.method`:** HTTP request method value SHOULD be "known" to the instrumentation.
211
-
By default, this convention defines "known" methods as the ones listed in [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-methods)
212
-
and the PATCH method defined in [RFC5789](https://www.rfc-editor.org/rfc/rfc5789.html).
213
+
By default, this convention defines "known" methods as the ones listed in [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-methods),
214
+
the PATCH method defined in [RFC5789](https://www.rfc-editor.org/rfc/rfc5789.html)
215
+
and the QUERY method defined in [httpbis-safe-method-w-body](https://datatracker.ietf.org/doc/draft-ietf-httpbis-safe-method-w-body/?include_text=1).
213
216
214
217
If the HTTP request method is not known to instrumentation, it MUST set the `http.request.method` attribute to `_OTHER`.
215
218
@@ -247,6 +250,7 @@ Tracing instrumentations that do so, MUST also set `http.request.method_original
|[`user_agent.synthetic.type`](/docs/registry/attributes/user-agent.md)| string | Specifies the category of synthetic traffic, such as tests or bots. [10]|`bot`; `test`|`Opt-In`||
286
290
287
291
**[1]`http.request.method`:** HTTP request method value SHOULD be "known" to the instrumentation.
288
-
By default, this convention defines "known" methods as the ones listed in [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-methods)
289
-
and the PATCH method defined in [RFC5789](https://www.rfc-editor.org/rfc/rfc5789.html).
292
+
By default, this convention defines "known" methods as the ones listed in [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-methods),
293
+
the PATCH method defined in [RFC5789](https://www.rfc-editor.org/rfc/rfc5789.html)
294
+
and the QUERY method defined in [httpbis-safe-method-w-body](https://datatracker.ietf.org/doc/draft-ietf-httpbis-safe-method-w-body/?include_text=1).
290
295
291
296
If the HTTP request method is not known to instrumentation, it MUST set the `http.request.method` attribute to `_OTHER`.
292
297
@@ -362,6 +367,7 @@ SHOULD include the [application root](/docs/http/http-spans.md#http-server-defin
|[`user_agent.synthetic.type`](/docs/registry/attributes/user-agent.md)| string | Specifies the category of synthetic traffic, such as tests or bots. [10]|`bot`; `test`|`Opt-In`||
410
416
411
417
**[1]`http.request.method`:** HTTP request method value SHOULD be "known" to the instrumentation.
412
-
By default, this convention defines "known" methods as the ones listed in [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-methods)
413
-
and the PATCH method defined in [RFC5789](https://www.rfc-editor.org/rfc/rfc5789.html).
418
+
By default, this convention defines "known" methods as the ones listed in [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-methods),
419
+
the PATCH method defined in [RFC5789](https://www.rfc-editor.org/rfc/rfc5789.html)
420
+
and the QUERY method defined in [httpbis-safe-method-w-body](https://datatracker.ietf.org/doc/draft-ietf-httpbis-safe-method-w-body/?include_text=1).
414
421
415
422
If the HTTP request method is not known to instrumentation, it MUST set the `http.request.method` attribute to `_OTHER`.
416
423
@@ -486,6 +493,7 @@ SHOULD include the [application root](/docs/http/http-spans.md#http-server-defin
|[`url.template`](/docs/registry/attributes/url.md)| string | The low-cardinality template of an [absolute path reference](https://www.rfc-editor.org/rfc/rfc3986#section-4.2). [8]|`/users/{id}`; `/users/:id`; `/users?id={id}`|`Opt-In`||
539
547
540
548
**[1]`http.request.method`:** HTTP request method value SHOULD be "known" to the instrumentation.
541
-
By default, this convention defines "known" methods as the ones listed in [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-methods)
542
-
and the PATCH method defined in [RFC5789](https://www.rfc-editor.org/rfc/rfc5789.html).
549
+
By default, this convention defines "known" methods as the ones listed in [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-methods),
550
+
the PATCH method defined in [RFC5789](https://www.rfc-editor.org/rfc/rfc5789.html)
551
+
and the QUERY method defined in [httpbis-safe-method-w-body](https://datatracker.ietf.org/doc/draft-ietf-httpbis-safe-method-w-body/?include_text=1).
543
552
544
553
If the HTTP request method is not known to instrumentation, it MUST set the `http.request.method` attribute to `_OTHER`.
545
554
@@ -614,6 +623,7 @@ If the request has completed successfully, instrumentations SHOULD NOT set `erro
|[`url.scheme`](/docs/registry/attributes/url.md)| string | The [URI scheme](https://www.rfc-editor.org/rfc/rfc3986#section-3.1) component identifying the used protocol. |`http`; `https`|`Opt-In`||
652
662
653
663
**[1]`http.request.method`:** HTTP request method value SHOULD be "known" to the instrumentation.
654
-
By default, this convention defines "known" methods as the ones listed in [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-methods)
655
-
and the PATCH method defined in [RFC5789](https://www.rfc-editor.org/rfc/rfc5789.html).
664
+
By default, this convention defines "known" methods as the ones listed in [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-methods),
665
+
the PATCH method defined in [RFC5789](https://www.rfc-editor.org/rfc/rfc5789.html)
666
+
and the QUERY method defined in [httpbis-safe-method-w-body](https://datatracker.ietf.org/doc/draft-ietf-httpbis-safe-method-w-body/?include_text=1).
656
667
657
668
If the HTTP request method is not known to instrumentation, it MUST set the `http.request.method` attribute to `_OTHER`.
658
669
@@ -727,6 +738,7 @@ If the request has completed successfully, instrumentations SHOULD NOT set `erro
|[`url.scheme`](/docs/registry/attributes/url.md)| string | The [URI scheme](https://www.rfc-editor.org/rfc/rfc3986#section-3.1) component identifying the used protocol. |`http`; `https`|`Opt-In`||
765
777
766
778
**[1]`http.request.method`:** HTTP request method value SHOULD be "known" to the instrumentation.
767
-
By default, this convention defines "known" methods as the ones listed in [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-methods)
768
-
and the PATCH method defined in [RFC5789](https://www.rfc-editor.org/rfc/rfc5789.html).
779
+
By default, this convention defines "known" methods as the ones listed in [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-methods),
780
+
the PATCH method defined in [RFC5789](https://www.rfc-editor.org/rfc/rfc5789.html)
781
+
and the QUERY method defined in [httpbis-safe-method-w-body](https://datatracker.ietf.org/doc/draft-ietf-httpbis-safe-method-w-body/?include_text=1).
769
782
770
783
If the HTTP request method is not known to instrumentation, it MUST set the `http.request.method` attribute to `_OTHER`.
771
784
@@ -840,6 +853,7 @@ If the request has completed successfully, instrumentations SHOULD NOT set `erro
@@ -971,8 +985,9 @@ In all other cases, `server.port` SHOULD match the port component of the
971
985
**[3]`url.template`:** The `url.template` MUST have low cardinality. It is not usually available on HTTP clients, but may be known by the application or specialized HTTP instrumentation.
972
986
973
987
**[4]`http.request.method`:** HTTP request method value SHOULD be "known" to the instrumentation.
974
-
By default, this convention defines "known" methods as the ones listed in [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-methods)
975
-
and the PATCH method defined in [RFC5789](https://www.rfc-editor.org/rfc/rfc5789.html).
988
+
By default, this convention defines "known" methods as the ones listed in [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-methods),
989
+
the PATCH method defined in [RFC5789](https://www.rfc-editor.org/rfc/rfc5789.html)
990
+
and the QUERY method defined in [httpbis-safe-method-w-body](https://datatracker.ietf.org/doc/draft-ietf-httpbis-safe-method-w-body/?include_text=1).
976
991
977
992
If the HTTP request method is not known to instrumentation, it MUST set the `http.request.method` attribute to `_OTHER`.
978
993
@@ -1000,6 +1015,7 @@ Tracing instrumentations that do so, MUST also set `http.request.method_original
Copy file name to clipboardExpand all lines: docs/http/http-spans.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -171,8 +171,9 @@ There are two ways HTTP client spans can be implemented in an instrumentation:
171
171
|[`user_agent.synthetic.type`](/docs/registry/attributes/user-agent.md)| string | Specifies the category of synthetic traffic, such as tests or bots. [15]|`bot`; `test`|`Opt-In`||
172
172
173
173
**[1]`http.request.method`:** HTTP request method value SHOULD be "known" to the instrumentation.
174
-
By default, this convention defines "known" methods as the ones listed in [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-methods)
175
-
and the PATCH method defined in [RFC5789](https://www.rfc-editor.org/rfc/rfc5789.html).
174
+
By default, this convention defines "known" methods as the ones listed in [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-methods),
175
+
the PATCH method defined in [RFC5789](https://www.rfc-editor.org/rfc/rfc5789.html)
176
+
and the QUERY method defined in [httpbis-safe-method-w-body](https://datatracker.ietf.org/doc/draft-ietf-httpbis-safe-method-w-body/?include_text=1).
176
177
177
178
If the HTTP request method is not known to instrumentation, it MUST set the `http.request.method` attribute to `_OTHER`.
178
179
@@ -320,6 +321,7 @@ and SHOULD be provided **at span creation time** (if provided at all):
@@ -472,8 +474,9 @@ This span represents an inbound HTTP request.
472
474
|[`user_agent.synthetic.type`](/docs/registry/attributes/user-agent.md)| string | Specifies the category of synthetic traffic, such as tests or bots. [18]|`bot`; `test`|`Opt-In`||
473
475
474
476
**[1]`http.request.method`:** HTTP request method value SHOULD be "known" to the instrumentation.
475
-
By default, this convention defines "known" methods as the ones listed in [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-methods)
476
-
and the PATCH method defined in [RFC5789](https://www.rfc-editor.org/rfc/rfc5789.html).
477
+
By default, this convention defines "known" methods as the ones listed in [RFC9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-methods),
478
+
the PATCH method defined in [RFC5789](https://www.rfc-editor.org/rfc/rfc5789.html)
479
+
and the QUERY method defined in [httpbis-safe-method-w-body](https://datatracker.ietf.org/doc/draft-ietf-httpbis-safe-method-w-body/?include_text=1).
477
480
478
481
If the HTTP request method is not known to instrumentation, it MUST set the `http.request.method` attribute to `_OTHER`.
479
482
@@ -614,6 +617,7 @@ and SHOULD be provided **at span creation time** (if provided at all):
0 commit comments