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 repeatedly find ourselves in situations where we need to debug things via debug statements (on staging or production for example), yet we are very skittish about leaving these debug statements in place due to their tendency to leak PII into the logs.
It would be nice to have the logger class do some kind of PII-masking for us so that a logging statement like:
We repeatedly find ourselves in situations where we need to debug things via debug statements (on staging or production for example), yet we are very skittish about leaving these debug statements in place due to their tendency to leak PII into the logs.
It would be nice to have the logger class do some kind of PII-masking for us so that a logging statement like:
user joe.public@fake.gov has phone +15555555555
would auto-magically become
user xxx.xxxxxx@fake.gov has phone +1555555XXXX
or something like that. That way the debug statements could be left in permanently.
The text was updated successfully, but these errors were encountered: