App Visibility component log files

This topic presents the location and purpose of log files for App Visibility components.

App Visibility server log files

For the App Visibility server components (portal, collector, proxy), check for errors reported in log files from the following locations:

Windows
- server_installationDirectory\collector\logs\collector.log
- server_installationDirectory\portal\logs\portal.log
- server_installationDirectory\apm-proxy\logs\apm-proxy.log
Linux
- server_installationDirectory/collector/logs/collector.log
- server_installationDirectory/portal/logs/portal.log
- server_installationDirectory/apm-proxy/logs/apm-proxy.log

For App Visibility agents, check for errors reported in the agent log files.

Check for installation or upgrade errors in the installation log file:
bmc_ad_agent_install.log, located in the %temp% (Windows) or temp (Linux) directory.

If you install the agent for Java from a Central Monitoring Administration installation package, the installation log file is located in the following folder:
- (Windows) %PATROL_HOME%
- (Linux) $PATROL_HOME
Check for errors reported in the App Visibility agent log file from the following location. The instance_name variable is a name that is generated dynamically when the agent first starts.
- (Windows) agent_installationDirectory/instances/instance_name/logs/aps_agent.log
- (Linux) agent_installationDirectory\instances|instance_name\logs\aps_agent.log

Check for installation errors in the agentinstaller_install_log.txt file, located in the %temp% folder.
Check for upgrade errors in the agentinstaller_upgrade_log.txt file, located in the %temp% folder.
Check for errors in the App Visibility agent log file from the following location: agent_installationDirectory\Agent for .NET\logs\current.log
Check for CRITICAL (0) or ERROR (1) events for the App Visibility agent service (BmcAdAgentDotNet) in the Windows event log.