APM logs and how to enable Debug.

Document ID : KB000033600
Last Modified Date : 14/02/2018
Show Technical Document Details

Introduction:

This document contains the location of the logs of different components of the APM and how to debug the logs. The components are EM, Webview, Agent (Java , .Net and EPagent), workstation and TIM.

 

Instructions:

A. Enterprise Manager:

Location/filename of the log: <EM home directory>\logs\IntroscopeEnterpriseManager.log

To DEBUG:

1. Go to <EM home directory>\config

2. Locate and open IntroscopeEnterpriseManager.properties in editor.

3. Search for log4j.logger.Manager=INFO, console, logfile

4. Change from INFO to DEBUG like log4j.logger.Manager=DEBUG, console, logfile

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 

B. Webview:

Location/filename of the log: <EM home directory>\logs\IntroscopeWebview.log

To DEBUG:

1. <EM home directory>\config

2. Locate and open IntroscopeWebView.properties in editor.

3. Search for log4j.logger.WebView=INFO, console, logfile

4. Change from INFO to DEBUG like log4j.logger.WebView=DEBUG, console, logfile

--------------------------------------------------------------------------------------------------------------------------------------------------------------

C.  Agent – JAVA:

Location/filename of the log:  <Agent home directory>\wily\logs\IntroscopeAgent.log

To DEBUG:

1. Go to <Agent home directory>\wily\core\config

2. Locate and open IntroscopeAgent.profile in editor.

3. Search for log4j.logger.IntroscopeAgent=INFO, logfile

4. Change from INFO to DEBUG like log4j.logger.IntroscopeAgent=DEBUG, logfile

--------------------------------------------------------------------------------------------------------------------------------------------------------------

D. Agent - .Net:

Location/filename of the log:  <Agent home directory>\wily\logs\IntroscopeAgent.log

To DEBUG:

1. Go to <Agent home directory>\wily.

2. Locate and open logging.config.xml file editor.

3. Search for <level value="INFO"></level>.

4. Change from INFO to DEBUG like <level value="DEBUG"></level>.

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

E. EP Agent:

Location/filename of the log:  <EPAgent home directory>\logs\IntroscopeEPA.log

To DEBUG:

1. Go to <EPAgent home directory>

2. Locate and open IntroscopeEPAgent.profile in editor.

3. Search for log4j.logger.EPAgent=INFO, logfile

4. Change from INFO to DEBUG like log4j.logger.EPAgent=DEBUG, logfile

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

F. Workstation:

Location/filename of the log:   <Workstation home directory>\logs\IntroscopeWorkstation.log

To DEBUG:

1. Go to <Workstation home directory>\config

2. Locate and open IntroscopeEPAgent.profile in editor.

3. Search for log4j.logger.Workstation=INFO, console, logfile

4. Change from INFO to DEBUG like log4j.logger.Workstation=DEBUG, console, logfile 

--------------------------------------------------------------------------------------------------------------------------------------------------------------

G. TIM:

To collect the logs:

1. Go to TIM setup page : http://<hostname>/cgi-bin/wily/packages/cem/tim/index

2.  Using the link “Collect Tim Log and Configuration files” the logs, configuration, Packet statistics, Transaction statistics and core dump files can be downloaded in the timlogs.data file which is aleady zipped.

To increase the log size:

1. Go to TIM setup page : http://<hostname>/cgi-bin/wily/packages/cem/tim/index

2. Using link "Configure Tim Settings" and set MaxLogSizeInMB = 200 will give the size of the logs.

To enable the traces:

1. Go to TIM setup page : http://<hostname>/cgi-bin/wily/packages/cem/tim/index

2. Using the link “Configure Tim Trace Options” and Enable all the Tim Trace options (Left column). CA Support may advise on specific trace options to set for a particular problem scenario. Also note that setting all trace options on an MTP TIM can cause TIM processing of pcap files from MTP feed directory to be impacted. 

To capture a pcap file on the Standard TIM server:

1. SSH to the TIM server. 

2. Run this command to capture packets:

    tcpdump -s 50000 -i eth0 -w test.pcap 

3. Once the command is running it will start to listen the packets on the port.

4. After few minutes please do ctrl+c to stop the listening.The captured packets file will be on the directory where the command ran. 

Note: change the eth* port according to which TIM NIC is the monitoring port.

To capture a pcap file on the MTP TIM server:

1. SSH to the MTP as user netqos

2. The command /opt/NetQoS/bin/buildpcap command can be used to extract a pcap from the MTP vertica database. To see a full list of parameter options type:

/opt/NetQoS/bin/buildpcap --help

An example command to capture data for web server 10.0.0.1 for a 5 minute period between 10.30-10.35 AM on Nov 25 would be:

opt/NetQoS/bin/buildpcap --feed 0 --start-datetime 20151125-10:30:00 --end-datetime 20151125-10:35:00 --filter-server-address 10.0.0.1 --filter-server-port 443 --output-file /tmp/test1.pcap

 

Additional Information:

Please refer to the CA wiki documentation link for your CA Application Performance Management version for further information: http://wiki.ca.com