Outputting to the file share also sidesteps the [redacted] messages.
But agreed, we need a way to turn-off this "feature" (not just dial it back), as it makes debugging logic much more difficult.
It would seem a far better way to handle the redacting would be to write unredacted message to the ErrorLog, and only apply the redacting the entire message (not just amounts containing a certain number of zeros) when displaying the log if the user looking at the log is not the owner of the log entry or is not a member of an authorized group.
we need a way to turn-off this "feature"
I am not the biggest fan of this feature, but there are legitimate concerns about outputting passwords, api keys, and the likes, so it likely won't be something you can just disable. It will become smarter very soon, though, so hopefully it won't be a real problem anymore.
