Traces Reference

The following table provides information for Traces for Service Communication Proxy.

Table 4-3 Traces Reference

Field Name	Request/ Response Type	Description
component	common	The software package, framework, library, or module that generated the associated Span.
node_id	common	Local information
:method	request,common	HTTP method of the request for the associated Span. Example: "GET","POST"
:scheme	request	Url scheme is http
:authority	request	Authority give you details about registered name or server address, along with optional port and user information
:path	request	A path consists of a sequence of path segments separated by a slash ("/") character.
3gpp-sbi-message-priority	request	This header shall be included in HTTP/2 messages when a priority for the message needs to be conveyed
x-forwarded-for	request	To identify the originating IP address of a client.
x-forwarded-proto	request	To determine the protocol used between the client and the spf.
x-envoy-internal	request	service wants to know whether a request is internal origin or not
via	request	It is used for tracking message forwards, avoiding request loops, and identifying the protocol capabilities of senders along the request/response chain
x-request-id	common	The x-request-idheader is used to uniquely identify a request as well as perform stable access logging and tracing
payload	request, common	http request body.
:status	response	To determine the http request has been succeeded or not.
content-type	response	The Content-Type entity header is used to indicate the media type of the resource
content-length	response	The Content-Length header indicates the size of the entity body in the message, in bytes
server	response	The Server response-header field contains information about the software used by the origin server to handle the request
date	response	The time and date, when the request is processed.
x-envoy-upstream-service-time	response	Contains the time in milliseconds spent by the upstream host processing the request
location	response	To provide information about the location of a newly created resource
payload	response	http response body.
http.url	request,common	Specifies the request's URL.
downstream_cluster	common	A downstream host connects to Envoy, sends requests, and receives responses
user_agent	request,common	When your browser connects to a website, it includes a User-Agentfield in itsHTTPheader
http.protocol	common	The communication between client and server over HTTP/2.
request_size	common	HTTP header size.
upstream_cluster	common	An upstream host receives connections and requests from Envoy and returns responses.
http.ststus_code	common	HTTP response status code for the associated Span. Example: 200, 503, 404
response_size	common	HTTP header size.
response_flag	common	Additional details about the response or connection, if any
span.kind	common	Specifies the role of the Span in a RPC communication. In the case of HTTP communication it is seeingclientandservervalues for this tag.
error	common	True, if and only if, the application considers the operation represented by the Span to have failed
x-request-id	request	The x-request-idheader is used by Envoy to uniquely identify a request as well as perform stable access logging and tracing
x-b3-traceid	request	The x-b3-traceidHTTP header is used by the Zipkin tracer in Envoy. The TraceId is 64-bit in length and indicates the overall ID of the trace. Every span in a trace shares this ID
x-b3-spanid	request	The x-b3-spanidHTTP header is used by the Zipkin tracer in Envoy. The SpanId is 64-bit in length and indicates the position of the current operation in the trace tree
x-b3-sampled	request	The x-b3-sampledHTTP header is used by the Zipkin tracer in Envoy. When the Sampled flag is either not specified or set to 1, the span will be reported to the tracing system
ueidentitytype	request	NF type.
ueidentityvalue	request	supi range for NF type .
x-envoy-expected-rq-timeout-ms	request	This is the time in milliseconds the router expects the request to be completed