Should I enable glide.rest.debug in production instances

[newdev111]

I enable "glide.rest.debug" in our development and testing instances.  Should I enable it in production instance? What is the impact if I enable it in our production instance?  I can't find ServiceNow documents about it.

Thank you

[Kieran Anson]

Hi,

What are you needing to debug? This property enables full REST API debugging across the instance and has a strong performance impact if left on for an extended period of time. 

1. Are you able to diagnose the issue in a sub-prod environment?
2. Can you clone the prod environment, or ask ServiceNow for a temporary clone to complete your debugging
3. If no to the above, are you able to identify a time-window to complete your debugging? Logs are sent to the node log, so you'll need to make sure you're checking the node logs. Restrict the time the property is enabled to as a few-transactions as you need to prevent excess logging

[newdev111]

Hi,

We are using it to debug inbound web services calls, mainly looking at the request parameters.  I suspect it would have performance impact, while not sure about it.  Is there a document regarding its performance impact?  

A reasonable solution might be turning it on then asking our client to reproduce/retry REST calls to our production instance.

[Kieran Anson]

Not aware of any documentation outside of asking SN directly via support.

But knowing that it logs all work related to inbound REST calls, and that this is logged directly to the node logs gives an idea of the potential scale. The more integrations to your environment, the more logging that'll occur. You also need to take into account interactive sessions (users) who's interactions with SN will also trigger REST api calls.

[newdev111]

Ok, I will turn it on only when actively debugging an REST web services issue.