linkerd

Value Members

1. object DelayedRelease

   

2. object Headers

   

   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 Headers 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, linkerd 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.
   • l5d-retryable: if true, the request for this response is known to be safe to retry (for example, because it was not delivered to its destination)

3. object HttpTraceInitializer

   

   Uses Headers.Ctx.Trace and Headers.Sample headers to propagate/control tracing.