Skip to end of metadata
Go to start of metadata

About Agent Log Files

Agent log files can help you resolve agent configuration and application instrumentation issues that prevent you from obtaining the information you need to optimize the performance of your environment. When submitting log files to AppDynamics Support, ensure you send the entire contents of the agent logs directory available as a zip file for download when you request the agent logs.

Agent log files are created automatically when the agent starts up. The logs available are agent dependent. 

The log files that you will probably find most useful to resolve instrumentation challenges and assist you in configuring your environment are: 

The following topics provide a brief overview of these logs:

Logging Levels

These are the five levels of logging, in the descending order of amount of information collected:

  • all:  Logs all events.
  • trace:  Reports finer-grained informational events than the debug level that may be useful to debug an application.
  • debug:  Reports fine-grained informational events that may be useful to debug an application.
  • info:  Default log level. Reports informational messages that highlight the progress of the application a coarse-grained level.
  • warn:  Reports on potentially harmful situations.
  • error:  Reports on error events that may allow the application to continue running. 

Controlling the Logging Level (Java and PHP)

By default, the logging level for most log files is set to "info". The finer the granularity, the faster the log file consumes disk space.

You can control the logging level for the App Agent for Java and App Agent for PHP agent by changing the value of the "level value" parameter in the log4j.xml file in the agent installation\logs directory. 

<logger name="com.singularity" additivity="false">
 <!--  to control the logging level of the agent log files, use the level attribute below. value="all|trace|debug|info|warn|error"-->
<level value="info"/>
<appender-ref ref="AgentLogger"/>
<appender-ref ref="RESTLogger"/>
</logger>

Controlling the Logging Level (.Net)

You can control the logging level for the App Agent for .Net by changing the value of the "min level" parameter in the AppDynamicsAgentLog.config file in the agent installation directory. The log configuration is per server. The coordinator/.NET machine agent and the .NET agents all read the same configuration file and write to the same set of output files.

<rules>
    <logger name="com.appdynamics.REST.HeartBeatLog" minLevel="Info" writeTo="RESTHearbeat" final="true" />
    <logger name="*" minLevel="Warn" writeTo="warnfile" />
    <logger name="com.appdynamics.BusinessTransactions" minLevel="Info" writeTo="btlog" final="true" />
    <logger name="com.appdynamics.bci.*" minLevel="Info" writeTo="bcifile" final="true" />
    <logger name="com.appdynamics.REST.*" minLevel="Info" writeTo="RESTfile" final="true" />
    <logger name="AppDynamics.Agent.Coordinator.Recovery.*" minLevel="Info" writeTo="CoordinatorRecovery" final="true" />
    <logger name="com.appdynamics.METRICS.MetricSender" minLevel="Info" writeTo="RESTfile" final="true" />
    <logger name="AppDynamics.Winston.*" minLevel="Info" writeTo="Winston" final="true" />
    <logger name="com.appdynamics.tm.AFastBackendResolver" minLevel="Warn" writeTo="logfile" final="true" />
    <logger name="com.appdynamics.ManagedAgentAPI.DumpStats" minLevel="Trace" writeTo=" SamplingInfo" final="true" />
    <logger name="*" minLevel="Info" writeTo="logfile" />
  </rules>

Log File Sizes and Life Cycle Details

Log File

App Agent for...

Max Size

Agent

Java, .Net

5 MB

Agent

PHP (PHP extension module)

20 MB

Proxy

PHP (Java proxy)

5 MB

Business Transaction

Java, .Net, PHP

5 MB

ByteCode Transformer

Java, .Net

20 MB

JMX

Java

5 MB

Machine Agent

Machine

5 MB

REST

Java, .Net, PHP

5 MB

  • When the maximum file size is reached, a new log is created. First file is named ...0.log, second file is ...1,log, and so on.
  • maximum of five files per set.
  • maximum of five sets. If the maximum number of sets is reached, when a new set is created, the oldest set is deleted.

Agent Log

App Agent for ...

Log Name

Java

agentYear_mon_day_hr_min.#.log

PHP (PHP extension component)

agent.#.log

PHP (Java proxy)

proxyYear_mon_day_hr_min.#.log

.NET

AgentLog.#.txt

These logs are generated by all App agents and report the activity of the agents as they monitor your applications. At the beginning of the log file, it shows the start up of the agent monitoring services and displays configuration settings. The agent log also contains the sequence of agent runtime activity and exceptions that are encountered. When you are troubleshooting various issues in an AppDynamics deployment, you can find useful information in this log. 

Examples of information in the log:

  • agent version and build date
  • JVM runtime version - Java only
  • configuration changes
  • backend detection
  • exceptions 
  • output from Logging Session requests

Proxy Log

App Agent for ...

Log Name

PHP (proxy)

proxyYear_mon_day_hr_min.#.log

The Proxy log is generated by the App Agent for PHP. This log file is useful for determining why snapshots are not being taken and for diagnosing communication issues with the controller.

Business Transactions Log

App Agent for ...

Log Name

Java

BusinessTransactionsYear_mon_day_hr_min.#.log

.Net (proxy)

BusinessTransactionsLog.#.txt

PHP

BusinessTransactionsYear_mon_day_hr_min.#.log

The Business Transactions log is generated by all agents and logs the following information:

  • discovered business transactions 
  • discovery stack trace for each entry point
  • dropped business transactions, which show up in the "default BT" when there is business transaction overflow.  Only executed methods show up in the business transaction log. If the business functionality is not exercised by the application, the code is not executed, and the methods are not examined as potential entry points.

Bytecode Transformer Log

App Agent for ...

Log Name

Java

ByteCodeTransformerYear_mon_day_hr_min.#.log

.Net

ByteCode.txt

The ByteCode Transformer log is generated by the App Agent for Java and App Agent for .Net and contains the information associated with the AppDynamics bytecode instrumentation (BCI) engine. The BCI engine is used to inject interceptors. The BCI engine logs the classes being loaded in the application.

This log is critical for troubleshooting all the things that depend on bytecode instrumentation including: Java entry points, exit points, loggers, errors, exceptions, and async threads.
Examples of information in the log:

  • agent version and build date
  • each Java class that was examined and whether the methods were considered for bytecode instrumentation
  • each method that was instrumented

This log file is useful to:

  • verify entry point instrumentation
  • verify backend instrumentation
  • troubleshoot missing metrics

JMX Log

App Agent for...

Log Name

Java

JMXYear_mon_day_hr_min.#.log.log

JMX log entries contain information about JMX interactions between the AppDynamics agent and the monitored server's JMX domains. These log entries are useful for diagnosing problems associated with JMX metrics, or issues with JVM metrics, which are reliant on JMX.

The JMX entries can be useful in debugging why MBeans don't appear or why metrics created from MBeans do not appear in the controller UI.

Standalone Machine Agent Log

Agent

Log Name

Standalone Machine

machine-agent.#.log

The machine agent log captures information from the Standalone Machine Agent as it monitors the health of the server in terms of the server's usage of CPU, memory, disk, and network interfaces. 

REST Log

App Agent for...

Log Name

Java

RESTYear_mon_day_hr_min.#.log

.Net

RESTCommunications.#.txt

PHP (proxy)

RESTYear_mon_day_hr_min.#.log

This log contains information about the AppDynamics agent and controller communication. The log contains request and response payload data between the agent and the controller, the raw details of communications between the agent and the controller. By default, the REST log contains INFO level logging for all registration requests up to a limit of 1MB every five minutes.

You can use this log to troubleshoot issues with detecting and reporting business transactions, backends, events, and metric reporting.

The communication between the agent and controller consists of the following:

  • configuration data
  • node identification
  • machine registration
  • business transaction registration
  • metric registration
  • event registration
  • snapshot capture/upload to controller database
  • metric data upload to controller database
  • event data upload to controller database
  • output from Logging Session requests

Learn More

Request Agent Log Files

  • No labels