The idea is:
Currently when you decide to save succesful execution logs, it’s either all or nothing. You can highlight certain data, using the “Execution Data” node, but I suggest the opposite is added too, scrubbing sensitive data (e.g. PII, passwords/keys, confidential IP) so that it is not visible to the user and/or isn’t stored in a location that doesn’t follow the same security procedures as say a database.
My use case:
I process a lot of lead data from different forms into databases, this contains data such as user emails, address details et cetera. I am not interested in seeing this data anywhere outside of the database. Currently, I have disabled succesful execution logging, which is quite annoying as I can’t easily see how many times certain workflows have been executed.
I think it would be beneficial to add this because:
First of all you would have a better view of the executions that have run succesfully, without being exposed to PII.
Secondly it would help the debugging process, by allowing the log to contain succesful executions without sensitive data, it is a lot safer to keep succesful executions in the log. Whenever a execution goes wrong, you can easily compare it with succesful executions without being exposed to data you shouldn’t normally see.
Any resources to support this?
Sentry does this amazingly, so do services like Microsoft Clarity, see:
-
[Scrubbing Sensitive Data | Sentry for Python](Scrubbing Sensitive Data | Sentry Docs)
-
[Frequently asked questions | Microsoft Learn](Masking and unmasking content | Microsoft Clarity)