Tracing and troubleshooting

To trace potential issues, a client application can provide trace context information in HTTP headers when calling the Ingestion API.

The support team can identify the request based on the received tracing information. The information that is provided in the header is logged, no matter what type of tracing is used. The trace context headers and values are only used for support logging purposes. They are not stored in data objects or data object properties in Data Lake.

The trace context values that are sent are not validated. We recommend that you follow the W3W standard. See https://www.w3.org/TR/trace-context-1/.

For example, you can use one of these fields, which are introduced as part of the W3W standard:

trace-id

The ID of the whole trace forest. The ID is used to uniquely identify a distributed trace through a system. It is represented as a 16-byte array, for example, 4bf92f3577b34da6a3ce929d0e0e4736. All bytes as zero (00000000000000000000000000000000) is considered an invalid value.

parent-id

The ID of the request as known by the caller. The ID is represented as an 8-byte array, for example, 00f067aa0ba902b7. All bytes as zero (0000000000000000) is considered an invalid value.

If you run into issues and you use context trace headers in your Ingestion API requests, then provide the trace information in your support incident.