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: packages/opentelemetry-semantic-conventions/src/trace/SemanticAttributes.ts
+51-2Lines changed: 51 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -372,7 +372,9 @@ clear whether the exception will escape.
372
372
HTTP_TARGET: 'http.target',
373
373
374
374
/**
375
-
* The value of the [HTTP host header](https://tools.ietf.org/html/rfc7230#section-5.4). When the header is empty or not present, this attribute should be the same.
375
+
* The value of the [HTTP host header](https://tools.ietf.org/html/rfc7230#section-5.4). An empty Host header should also be reported, see note.
376
+
*
377
+
* Note: When the header is present but empty the attribute SHOULD be set to the empty string. Note that this is a valid situation that is expected in certain cases, according the aforementioned [section of RFC 7230](https://tools.ietf.org/html/rfc7230#section-5.4). When the header is not set the attribute MUST NOT be set.
376
378
*/
377
379
HTTP_HOST: 'http.host',
378
380
@@ -433,7 +435,17 @@ clear whether the exception will escape.
433
435
/**
434
436
* The IP address of the original client behind all proxies, if known (e.g. from [X-Forwarded-For](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For)).
435
437
*
436
-
* Note: This is not necessarily the same as `net.peer.ip`, which would identify the network-level peer, which may be a proxy.
438
+
* Note: This is not necessarily the same as `net.peer.ip`, which would
439
+
identify the network-level peer, which may be a proxy.
440
+
441
+
This attribute should be set when a source of information different
442
+
from the one used for `net.peer.ip`, is available even if that other
443
+
source just confirms the same value as `net.peer.ip`.
444
+
Rationale: For `net.peer.ip`, one typically does not know if it
445
+
comes from a proxy, reverse proxy, or the actual client. Setting
446
+
`http.client_ip` when it's the same as `net.peer.ip` means that
447
+
one is at least somewhat confident that the address is not that of
448
+
the closest proxy.
437
449
*/
438
450
HTTP_CLIENT_IP: 'http.client_ip',
439
451
@@ -607,6 +619,11 @@ clear whether the exception will escape.
607
619
*/
608
620
MESSAGING_OPERATION: 'messaging.operation',
609
621
622
+
/**
623
+
* The identifier for the consumer receiving a message. For Kafka, set it to `{messaging.kafka.consumer_group} - {messaging.kafka.client_id}`, if both are present, or only `messaging.kafka.consumer_group`. For brokers, such as RabbitMQ and Artemis, set it to the `client_id` of the client consuming the message.
624
+
*/
625
+
MESSAGING_CONSUMER_ID: 'messaging.consumer_id',
626
+
610
627
/**
611
628
* RabbitMQ message routing key.
612
629
*/
@@ -682,6 +699,28 @@ clear whether the exception will escape.
682
699
* `error.message` property of response if it is an error response.
0 commit comments