All Ideas

Idea Details

Post an Idea

This idea has been delivered and can no longer be voted or commented on. If you’d like to add to this conversation, please post a new idea.

930 Points voting closed

Delivered in Spring 18

Daniel Ballinger

Debug logging level that will prevent ENTERING_MANAGED_PKG appearing in the log

Apex & Visualforce

Currently during unit testing in a development packaging org the log file can be completely consumed with ENTERING_MANAGED_PKG messages regardless of what the logging levels are set to.

With more complicated tests this can consume the entire log until the maximum log sized is reached, making it difficult to retrieve useful logging messages.

Can the ENTERING_MANAGED_PKG message be tied to a logging level (preferably Finest) so it can be excluded from the logs?

· Flag

Latest Comment from Salesforce

Chris Peterson - 3 years ago

In looking into this idea we discovered a bug where calls to some methods on the System class would generate erroneous ENTERING_MANAGED_PKG log lines. This is now fixed in Spring '18. In addition we're also changd the log level from INFO to FINE so that this doesn't cause the truncation of DEBUG level events.

Flag

Comments ( 27 )

Sort By

Ken Gibson - 3 years ago

Could we also add exclusion for

Database.QueryLocatorIterator.hasNext()

I'm sure at some level this is useful - maybe we need a "Super Fine" level, or "Everything"? Honestly "Heap Size" and other JVM performance metrics aren't much use to me, either.

Thanks!

Flag

Alex Sutherland - 3 years ago

Huzzah!
- Flag
Eric Kintzer - 3 years ago

This is some of the best news ever for developers
- Flag
Chris Peterson - 3 years ago

@Lee Fang - next release, so Spring '18
- Flag
Lee Fang - 3 years ago

OMG!!!
FINALLY!!!
THANK YOU SO MUCH!!!
so when will it be available? I still have this issue today.
- Flag
Phillip Southern - 3 years ago

Wow, great update. You must be a PM.
- Flag

Chris Peterson - 3 years ago

Flag

Roger Bertilsson - 3 years ago

This would be very useful
- Flag
Yogesh Shukla - 3 years ago

Upvoted this much needed feature when we have mountain of managed code running in each action, specially in case of some CPQ products.
- Flag
Marcus Harikian - 3 years ago

This is an extremely important request for developers. Since Salesforce is unwilling to extend the debug log sizes, please add this to the debug configuration.
- Flag
Dan Crowdus - 3 years ago

*********** MAXIMUM DEBUG LOG SIZE REACHED ***********

::quiet sobbing::
- Flag
Ben Burbridge - 3 years ago

The debug logs are now worthless given the ENTERING_MANAGED_PKG statements crowd out my debug statements!
- Flag

Jason Clark - 3 years ago

As of Summer 17, I cannot disable these warnings. I've tried setting Apex logging to WARN and ERROR. Even with all logging set to NONE (including Apex), and System set to DEBUG (to make sure a log is produced), I still get a log full of ENTERING_MANAGED_PKG messages.

Flag

Tad Aalgaard - 3 years ago

I agree with others comments. Development in the SFDC environment is severely hampered by simple things like terrible logging.
- Flag
Lee Fang - 4 years ago

need 2500 points. still a long way to go. salesforce couldn't be careless about the developers.
- Flag

Daniel Ballinger

7 years ago

930 Points Delivered in Spring 18

Ideas

Apps

from AppExchange

Questions

No results found.

COVID-19