rpc.request.metadata
Developmenttemplate[string[]]as of v1.44.0
RPC request metadata, <key> being the normalized RPC metadata key (lowercase), the value being the metadata values.
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"]
Examples
- ["1.2.3.4","1.2.3.5"]
Used by
spans (6)
- span.rpc.connect_rpc.call.client (opt-in)
- span.rpc.connect_rpc.call.server (opt-in)
- span.rpc.dubbo.call.client (opt-in)
- span.rpc.dubbo.call.server (opt-in)
- span.rpc.grpc.call.client (opt-in)
- span.rpc.grpc.call.server (opt-in)
* required on that signal.
History
Now referenced by
span.rpc.dubbo.call.clientandspan.rpc.dubbo.call.server(opt in).Added as development.