RPC request metadata, <key> being the normalized RPC metadata key (lowercase), the value being the metadata values.
Example
["1.2.3.4", "1.2.3.5"]
Note
Instrumentations SHOULD require an explicit configuration of which metadata values are to be captured.
Including all request metadata values can be a security risk - explicit configuration helps avoid leaking sensitive information.
For example, a property my-custom-key with value ["1.2.3.4", "1.2.3.5"]SHOULD be recorded as
rpc.request.metadata.my-custom-key attribute with value ["1.2.3.4", "1.2.3.5"]
This attribute is experimental and is subject to breaking changes in minor releases of @opentelemetry/semantic-conventions.
RPC request metadata,
<key>being the normalized RPC metadata key (lowercase), the value being the metadata values.Example
Note
Instrumentations SHOULD require an explicit configuration of which metadata values are to be captured. Including all request metadata values can be a security risk - explicit configuration helps avoid leaking sensitive information.
For example, a property
my-custom-keywith value["1.2.3.4", "1.2.3.5"]SHOULD be recorded asrpc.request.metadata.my-custom-keyattribute with value["1.2.3.4", "1.2.3.5"]This attribute is experimental and is subject to breaking changes in minor releases of
@opentelemetry/semantic-conventions.