Q. We have a customer that is attempting to reduce jtapi logging in high call flow environment. If they need to reduce JTAPI log volumes, what is the minimum output values required for debugging, and which ones can be safely turned off?
That is, which of these can be eliminated:
INFORMATIONAL
DEBUG
WARNING
JTAPI_DEBUGGING
JTAPIIMPL_DEBUGGING
CTI_DEBUGGING
CTIIMPL_DEBUGGING
PROTOCOL_DEBUGGING
MISC_DEBUGGING
If we have corresponding CTIManager logs we could potentially turn off the following
CTI_DEBUGGING
CTIIMPL_DEBUGGING
PROTOCOL_DEBUGGING
Are there any that could be turned of even without CTIManager logs?
A. PROTOCOL_DEBUGGING is one that takes up space and can be turned off if we have CTI logs to tell us what events are sent out. Without CTI logs and PROTOCOL_DEBUGGING we will loose debugging capability for some scenarios.
Only combination we had success is with CTIManager logs with JTAPI PROTOCOL_DEBUGGING turned off.
Comments
0 comments
Please sign in to leave a comment.