The finagle http stack manages a set of context headers that are
read from server requests and written to client requests.
The finagle http stack manages a set of context headers that are
read from server requests and written to client requests. The
LinkerdHeaders module replaces these headers with
linkerd-specific headers (prefixed by l5d-).
Context headers, read and written by each linkerd instance, include:
l5d-ctx-deadline
l5d-ctx-dtab
l5d-ctx-trace
Additionally, linkerd honors the following headers on incoming requests:
l5d-dtab: a client-specified delegation override
l5d-sample: a client-specified trace sample rate override
In addition to the context headers, linkerd may emit the following
headers on outgoing requests:
l5d-dst-logical: the logical name of the request as identified by linkerd
l5d-dst-concrete: the concrete client name after delegation
l5d-dst-residual: an optional residual path remaining after delegation
l5d-reqid: a token that may be used to correlate requests in
a callgraph across services and linkerd instances
And in addition to the context headers, lay may emit the following
headers on outgoing responses:
l5d-err: indicates a linkerd-generated error. Error responses
that do not have this header are application errors.
The finagle http stack manages a set of context headers that are read from server requests and written to client requests. The LinkerdHeaders module replaces these headers with linkerd-specific headers (prefixed by l5d-).
Context headers, read and written by each linkerd instance, include:
l5d-ctx-deadline
l5d-ctx-dtab
l5d-ctx-trace
Additionally, linkerd honors the following headers on incoming requests:
l5d-dtab
: a client-specified delegation overridel5d-sample
: a client-specified trace sample rate overrideIn addition to the context headers, linkerd may emit the following headers on outgoing requests:
l5d-dst-logical
: the logical name of the request as identified by linkerdl5d-dst-concrete
: the concrete client name after delegationl5d-dst-residual
: an optional residual path remaining after delegationl5d-reqid
: a token that may be used to correlate requests in a callgraph across services and linkerd instancesAnd in addition to the context headers, lay may emit the following headers on outgoing responses:
l5d-err
: indicates a linkerd-generated error. Error responses that do not have this header are application errors.