HTTP/2 200 server: GitHub.com content-type: text/html; charset=utf-8 last-modified: Mon, 16 Jun 2025 23:02:12 GMT access-control-allow-origin: * etag: W/"6850a274-11b7" expires: Tue, 14 Oct 2025 06:16:49 GMT cache-control: max-age=600 content-encoding: gzip x-proxy-cache: MISS x-github-request-id: 8C38:147592:42CA4:5488C:68EDE879 accept-ranges: bytes age: 0 date: Tue, 14 Oct 2025 06:06:49 GMT via: 1.1 varnish x-served-by: cache-bom-vanm7210032-BOM x-cache: MISS x-cache-hits: 0 x-timer: S1760422009.135260,VS0,VE316 vary: Accept-Encoding x-fastly-request-id: 14597b37d80031f5e094fb0d3a68bdf4fee47f43 content-length: 1541

Glossary

Distributed trace

A distributed trace is a set of events, triggered as a result of a single logical operation, consolidated across various components of an application. A distributed trace contains events that cross process, network and security boundaries. A distributed trace may be initiated when someone presses a button to start an action on a website - in this example, the trace will represent calls made between the downstream services that handled the chain of requests initiated by this button being pressed.

Opaque value

An opaque value refers to a value that can only be understood or processed in any way by the distributed trace participant that generated this value. Any other participant must treat it as a blob of bytes.