Question:
When should I use specific TIM Trace options?
<Please see attached file for image>
Answer:
The following are common settings. But these may change depending on the type of issues that you are having.
Note: Running full Tim Trace Options in a production environment can cause memory and disk issues.
If having traffic issues, set
- Trace connections
- Trace HTTP components
- Trace HTTP parameters.
If having SSL issues, set
- Trace connections (Optional)
- Trace HTTP components
- Trace HTTP parameters
- Trace SSL errors.
If having User/User Group issues, set
- Trace sessions and logins.
If having Defect/Definition issues, set
- Trace Defects
- Trace Business Transactions
- Trace Transactions
- Trace Transaction Components
- Trace HTTP Components/Parameters.
Additional Information:
How to parse a TIM log by IP address.
http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec610515.aspx
Can full TIM logging create a nospace or frequent TIM Restart condition in a production MTP?
http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec600884.aspx