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