Skip to main content
edited title
Link
identigral
  • 7.8k
  • 34
  • 33
  • 45

How to audit changes to Find out who modified a TraceFlag?

Source Link
Adrian Larson
  • 151.3k
  • 38
  • 247
  • 431

How to audit changes to TraceFlag?

We have a team structure where dozens of developers share one sandbox. A lot of corporate machinery is involved, but we are working on splitting out development into a greater number of environments. However, that could still take a while, and every day that I need to debug something, we get the lovely error message that our daily limit of debug logs is over 1000MB, and I have to go in and delete ~100 ApexLog records just to change my own log levels.

I asked our entire dev team if they were okay with us lowering the default settings (SFDC_DevConsole) to NONE everywhere, then asking people to use different trace flags if they actually need more granularity. Everyone signed off on the change, I made it, then the next morning, the ApexCode level was right back to FINEST. It has happened a few times.

I tried to dig into who keeps reverting my change, so I can broaden the conversation. But these changes do not show up in the Setup Audit Trail. We have Event Monitoring in this org, so I have some tools to dig deeper, but I do not know how to use them.

Is there a way to find out who modified a TraceFlag?