You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use Integrant to do state management and use middleware to attach the subsystems to each request: (-> req (assoc :system/db (:db system)) ...). Occasionally, there's a faulty connection (hard to tell exactly why or how, we're still diving into a related issue) and the :client-id is nil, which trips the line below. This logs the gigantic request to our logs, which includes things like production secrets that are stored in memory only.
Would it be possible to add a flag or some configuration to allow us to avoid logging in this case? We're already dealing with the thrown exception and can log a redacted form of the request as desired.
Motivations for change:
1. Full ring req is an unnecessary amount of info, and may
produce a lot of log noise.
2. Sensitive info can be (and often is) in ring requests.
3. Users can anyway catch the exception which includes the
request if they really need it.
Thanks to @NoahTheDuke for the report!
Hey Peter!
We use Integrant to do state management and use middleware to attach the subsystems to each request:
(-> req (assoc :system/db (:db system)) ...)
. Occasionally, there's a faulty connection (hard to tell exactly why or how, we're still diving into a related issue) and the:client-id
isnil
, which trips the line below. This logs the gigantic request to our logs, which includes things like production secrets that are stored in memory only.Would it be possible to add a flag or some configuration to allow us to avoid logging in this case? We're already dealing with the thrown exception and can log a redacted form of the request as desired.
sente/src/taoensso/sente.cljc
Line 752 in b746080
The text was updated successfully, but these errors were encountered: