Impact when debug "Enable All" is enabled
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2023 02:48 PM
What is the impact on the environment when session debugging "Enable All" is enabled? Found lots of articles regarding session debugging and how it is used however I did not find any mention of system impact.
The System Administrator does not like the idea of enabling session debugging for all developers and developers have resorted to adding logging statements so now there are a lot more system logs which bothers the Admins.
Thank you for your replies in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2023 03:36 PM - edited 09-13-2023 03:38 PM
Is this for production or non-production environments? In my experience debugging should be done in a non-production environment anyway, as long as you're up to date with cloning back prod. In any environment, it's not something I leave on and only use when tracing an error.
As for sending stuff into the system log, at times I've created a system property turn off and on my logging function. You really want to keep that production log as noiseless as possible.
If you want to know system impact, you can ask a question through to NowSupport. Still though, it's something to be used when there is an issue and not left on all the time.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2023 04:15 PM
Hi coyoteRay1,
when I enable all in Session Debug Enable All, I get a new browser window to see debug info. It is not for all developers, just my session. As stated by bpgeh, why do admins of dev instances care what's in the logs? What activity do they complain about on a dev or test instance? Where testing is expected.
