request-id.core

Liking cljdoc? Tell your friends :D

Clojure only.

add-request-id-timbre-middleware
current-header-name
default-header-key
request-id
url-friendly-guid
with-request-id-stamping
wrap-request-id

add-request-id-timbre-middleware^clj

(add-request-id-timbre-middleware request-id)

current-header-name^clj

default-header-key^clj

request-id^clj

(request-id {:keys [headers]})

Given an HTTP request (a la ring), get the current request ID. Must be called from within an invocation of the wrap-request-id middleware

Given an HTTP request (a la ring), get the current request ID. Must be called
from within an invocation of the `wrap-request-id` middleware

raw docstring

url-friendly-guid^clj

(url-friendly-guid)

See https://www.ietf.org/rfc/rfc3986.txt

See <https://www.ietf.org/rfc/rfc3986.txt>

raw docstring

with-request-id-stamping^cljmacro

(with-request-id-stamping request-id & body)

Given a request-id, make sure every log message is stamped with the request-id in brackets at the beginning

Given a `request-id`, make sure every log message is stamped with the
`request-id` in brackets at the beginning

raw docstring

wrap-request-id^clj

(wrap-request-id handler)

(wrap-request-id request-id-header-name handler)

Wrap a handler function in a function that causes a unique request ID to be stamped on every log message using a timbre middleware. If you give it a request-id-header-name, it will grab/generate the header on the request and response using the given name. If a value is already present in the headers it will use the existing value instead of making a new one.

Wrap a handler function in a function that causes a unique request ID to
be stamped on every log message using a timbre middleware. If you give it
a `request-id-header-name`, it will grab/generate the header on the request
and response using the given name. If a value is already present in the
headers it will use the existing value instead of making a new one.

raw docstring