I am trying to use the “Disable logging for” option under Advanced for a query. When I add a field under this option and push to production, the field is still populated under the audit logs. I have tried this for multiple queries and multiple pages.
Hello @Jack_T , this is happening on the cloud platform. I tested this a little bit ago and the issue is still present. Any suggestions on how to resolve this?
I was testing this out on a REST query and it was able to hide query params, but my Advanced options looked different from yours
Mine was titled "Remove parameters from logs" as opposed to yours being titled "Disable logging for". Also mine did not populate with either of the two headers I had added as options.
My instance is also on cloud so it shouldn't be a version discrepancy. Let me know how I can best reproduce this bug so I can file a request to fix this to our engineering team!
I just checked the ticket and it looks like it has been moved to a high priority. It hasn't been assigned to an engineer yet, I am guessing they have a lot on their plate.
I just added a +1 from you to the ticket so that should further increase the tickets weight in getting attention. Will update this post with any further details I get