A replacement for the default error logger which depends on a configured reporter.
The intended use for the exposed function is to find its way in a
server configuration, in the blueprint.handler.error/logger key.
If a reporter is configured - say, through exoscale/mania - you can merge:
{:blueprint.handler.error/logger blueprint.handler.reporter/report}
onto your server options. If you wish to extract more standard keys
from your context when reporting to sentry, build the appropriate
plucking with report-fn.
A replacement for the default error logger which depends on a
configured reporter.
The intended use for the exposed function is to find its way in a
server configuration, in the `blueprint.handler.error/logger` key.
If a reporter is configured - say, through exoscale/mania - you
can merge:
{:blueprint.handler.error/logger blueprint.handler.reporter/report}
onto your server options. If you wish to extract more standard keys
from your context when reporting to sentry, build the appropriate
plucking with `report-fn`.(pluck-fn paths)A closure which yields a function to select keys out of the context.
The path specification may either be a collection, in which case, it must contain keywords which will be selected out of the context.
If paths is a map it is expected to a dictionary of key to path in the input.
A closure which yields a function to select keys out of the context. The path specification may either be a collection, in which case, it must contain keywords which will be selected out of the context. If paths is a map it is expected to a dictionary of key to path in the input.
Default reporting function, only plucks :request-id from
a blueprint context, use report-fn to build your reporting
function if you want more keys to be selected out
Default reporting function, only plucks `:request-id` from a blueprint context, use `report-fn` to build your reporting function if you want more keys to be selected out
(report-fn paths)Build a reporting function, valid for use as an alternative logger for a blueprint error interceptor. Uses a path specification for keys to pluck out of the context
The path specification may either be a collection, in which case, it must contain keywords which will be selected out of the context.
If paths is a map it is expected to a dictionary of key to path in the input.
Build a reporting function, valid for use as an alternative logger for a blueprint error interceptor. Uses a path specification for keys to pluck out of the context The path specification may either be a collection, in which case, it must contain keywords which will be selected out of the context. If paths is a map it is expected to a dictionary of key to path in the input.
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |