Kirk Steffke - 4 years ago
@Miguel - when up against the issue and looking specifically for system.debugs, I find myself lowering the "Apex Code" Log Level down low enough that the ENTERING_MANAGED_PKGs no longer apply. I think "Warn" is the first level it stops including those. Then explicitly set my sys.debug levels to be "Warn" or lower.
Kirk Steffke - 5 years ago
I think it's important to note that there are actually two items to address in this idea:
a) The ability to filter out ENTERING_MANAGED_PKG messages - all orgs (dev or customer), regardless of the issue. In app-heavy orgs, you can quickly get to the log size limit.
b) Address the issue that causes the logging of ENTERING_MANAGED_PKG entries from within the org the package is being developed. It's entirely possible to see a debug log full of these entries, in the development org of a package, where no other Apps are installed.
David Mosher - 5 years ago
This has been going on for years now. Clearly Salesforce doesn't care about how much time app developers are wasting trying to debug problems with the log files overflowing with this message even when you are in the source org with only 2 (TWO) methods. When you are in the source org this message clearly can be suppressed by the debug filter. This appears to happen when you define an object or structure in your package and then access (insert, update) outside of the package including in its own testmethod class that is in the package!!!!
When is Salesforce going to get serious about supporting its package developers????
Mike Katulka - 6 years ago
@mandar - That's unfortunate for you! I hope you can figure out a way to debug what you need. I've had to resort to a backup plan. Here are some ideas for you:
Overall, wrap more code in try/catch blocks so you can depend on the following options (don't forget to use database.rollback(savepoint) within the catch where necessary. Also track limits to leave room for the logging if you have issues with limits.
Keith Clarke - 6 years ago
I'm doing some debugging in Winter '15 with all categories set to "None" except Apex Code which is set to "Error" (to filter out as much as possible). Even after getting support to up the log size to the maximum of 10M bytes the information I need is off the end of the log because it is swamped by useless ENTERING_MANAGED_PKG entries. This is in the packaging org of one of our maaged packages.
So it looks to me like the problem still exists.