5

I am developing in a namespaced DE org (not packaged yet) and using standard SFDC_DevConsole debug levels (Apex = Debug, System = Debug, DB = Info) with no trace overrides. But all I see in the logs are my debug statements, queries, profiling info, and rows showing ENTERING_MANAGED_PKG.

This is a relatively newer org (created in late Feb 2016) and I haven't seen this behaviour in other managed DE orgs. So I can't tell where the problem is.

Btw I'm not sure if others have noticed this but the debugger has become somewhat unreliable as of late. For instance overriding debug levels for Apex classes does not always kick into effect. This was experienced recently in a customer org.

2

My understanding is that it should be possible to avoid the ENTERING_MANAGED_PKG log entries by using an Apex Code logging level above INFO. I.e. WARN or ERROR.

Generally this works. However, there have been cases reported where changing the log level doesn't filter it out as expected. Voting for Debug logging level that will prevent ENTERING_MANAGED_PKG appearing in the log may help here.

With regards to the Developer Console not always applying the selected log levels. I found an oddity that was introduced in Winter `16 - Salesforce Debug logs with the Winter '16 Developer Console. Basically, by default all users share the same DebugLevel configuration. So if one user makes changes it affects all the users who are using the default configuration.

  • It sounds like another case of a resurfacing bug. I have one more reason to build my own debugger now! – Mossi May 31 '16 at 18:17
  • @Mossi I've always found the ENTERING_MANAGED_PKG entries a bit odd. I'm yet to see the value in them and they can consume 80%+ of the log file at times. I made my own log parser to filter them out. – Daniel Ballinger May 31 '16 at 19:44
  • Is this suddenly worse in Summer 17? With my logging set to Apex: ERROR and all other categories set to NONE, I'm hitting the log size limits with only CODE_UNIT_STARTED, CODE_UNIT_FINISHED, and ENTERING_MANAGED_PKG lines. Trying class-level filters (Set all to NONE) on the triggers invoking the managed code is useless as well. At this point my log files are unusable. – Jason Clark Jun 28 '17 at 14:08
  • Removing logging statements from the non-test-class code seems to have caused the system to start suppressing ENTERING_MANAGED_PKG messages according to my current log level. I don't have a solid set of repro steps, but I'm able to produce debug output from my test class again. – Jason Clark Jun 28 '17 at 17:23

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.