prone.middleware — prone 2019-07-08

The Prone middleware can be used to catch exceptions from your app and present them in an interactive explorer UI. Stack traces will by default be filtered to focus on your app's stack frames, and environment data is available for inspection, along with data passed to Prone via prone.debug/debug

asset-name->contents clj

asset-name->url clj

asset-url->contents clj

assets clj

create-exception-page clj

(create-exception-page e {:keys [debug-data request app-namespaces]})

debug-response clj

(debug-response req data)

Ring Response for prone debug data.

exceptions-response clj

(exceptions-response req e app-namespaces)

Ring Response for prone exceptions data.

find-application-name-in-project-clj clj

(find-application-name-in-project-clj s)

pages clj

render-self-contained-page clj

(render-self-contained-page data)

wrap-exceptions clj

(wrap-exceptions handler
                 &
                 [{:keys [app-namespaces skip-prone? print-stacktraces?]
                   :or {print-stacktraces? true}
                   :as opts}])

Let Prone handle exeptions instead of Ring. This way, instead of a centered stack trace, errors will give you a nice interactive page where you can browse data, filter the stack trace and generally get a good grip of what is happening.

Optionally, supply a opts map to specify namespaces to include, a predicate function to exclude certain requests from prone, and a boolean value to silence printing of exception stacktraces e.g.:

=> (wrap-exceptions handler {:app-namespaces ['your-ns-1 'my.ns.to-show] :skip-prone? (fn [req] (not-browser? req) :print-stacktraces? false})