Configuring Trace Logging

Trace logging is useful for quickly resolving issues for specific sessions that are currently active. They are temporary filters that are generated based on a qualifier that is independent of the global event log filter configured using the logging filter command in the Exec mode. Like event logs, however, the information generated by the logs is stored in the active memory buffer.

All debug level events associated with the selected call are stored.

Important

Trace logs impact session processing. They should be implemented for debug purposes only.

Use the following example to configure trace logs in the Exec mode:

logging trace { callid call_id | ipaddr ip_address | msid ms_id | username username } 

Once all of the necessary information has been gathered, the trace log can be deleted by entering the following command:

no logging trace { callid call_id | ipaddr ip_address | msid ms_id | username username }