What is collected by default when using the Collect TIM Logs menu options?

Products

• CA Application Performance Management Agent (APM / Wily / Introscope)
• INTROSCOPE

Issue/Introduction

Description:

This article goes into detail about the TIM logs collected including the previously undocumented stats "directory".

Solution:

Here is an overview of what is collected for a non MTP TIM:

File/Directory/How produced	Directory/File name in TIM zip	What/Why
/etc/wily/cem/tim/config directory including javapluginsconfig and javaplugins directory	Config	The key TIM configuration files including TIM settings, Trace options, domainconfig.xml, interfaces, plugins, etc. Wrong configuration settings can cause a variety of TIM performance issues.
/etc/wily/cem/tim/logs including inspection,protocolstats, threaddump, and timfiles directories	Logs	The logs to show TIM performance and handling of transaction definition monitoring.
/etc/wily/cem/tim/status	Status	This directory does not exist on the TIM. The files listed below are the output typically of UNIX commands. This can show if there are any operating system or disk/CPU issues.
/etc/timlock	timlock	The process lock used to review performance conditions
-system-file-locks is using the flock command	system-file-locks	Shows current file locks created by flock command. Useful for lock contention issues.
Output of rpm -qa	installed-packages	Displays currently installed rpm packages and their versions
Output of ifconfig	interfaces-config	Displays currently loaded interfaces and if they are seeing traffic and are having any error or dropped packets. This is a way to quickly evaluate network quality. Note the packet information is not captured on MTP TIMs since that uses a different logical interface.
Output of /proc/pid/statm	process-statm	Provides information about process state and memory usage. Useful for TIM performance issues
list of core files	coredumplist	Displays core files in /etc/wily/cem/tim. The number of core files kept is a configurable TIM watchdog setting. The default is one.
Output of netstat -i	interfaces	Displays current network interfaces and their status.
Out of ps to capture TIM pid number	pid	TIM pid number. Useful for tracking performance issues.
Output of netstat -a	connections	Displays current network connections and their status. This is useful in debugging network problems.
Output of netstat -r	routing	Displays current TIM network routing information. This is useful in debugging TIM connectivity issues.
Output of ps	process-stat	Displays the current status of TIM processes.
Output of /etc/wily/cem/tim/bin/configtool -f timsettings.db -l	settings	Displays current TIM setting in clear text. Useful in debugging configuration issues.
Output of uptime command	sys	Displays system availability, load average and more.
Output of ps command	processes	Displays process information. This is useful in debugging performance issues.
Output of cat /proc/pid/maps	process-map	Displays memory map, heap, and stack information This is useful in debugging TIM memory issues.
Output of /proc/pid/status	process-status	Displays process run state and memory information. This is useful in TIM performance issues.
Output of /etc/wily/cem/tim/bin/ TimMonXml	mon	Reads Tim status from shared memory and outputs it as XML. Useful in debugging memory issues.
Output of /proc/fd list	proces-fd	Displays TIM file descriptors. This is useful in debugging TIM memory/performance issues.

Note that core files are not collected by default unless explicitly checked. A MTP TIM will have additional files/folders collected such as the napatech (network card) information.

Environment

Release:
Component: APMCEM