Oracle Cloud Infrastructure Documentation

Verify APM Java Agent Deployment

You can verify if the APM Java agent deployment was successful by checking the user interface and examining the logs.

Check the User Interface: Trace Explorer

After the APM Java agent is successfully deployed, you can go to Trace Explorer and verify if the trace data from the application server is being uploaded. For information, see Monitor Traces in Trace Explorer.

Examine the APM Java Agent Logs

After an APM Java agent is successfully deployed, a new log directory is created in <Destination Directory>/oracle-apm-agent. Note that the <Destination Directory> is where the APM Java agent is provisioned, for example, $DOMAIN_HOME for the Oracle WebLogic Server.

To verify if the APM Java agent deployment was successful:

  1. Verify that the log directory is created by running the following command:
    cd <Destination Directory>/oracle-apm-agent
ls -l
  2. Verify that the log directory contains the following log files:
    • AgentErrors.log
    • Agent.log
    • AgentStartup.log
    • AgentStatus.log

    Note that if all the expected log files were not created, then the APM Java agent deployment was not successful.

  3. Open the AgentStartup.log file and verify if the following message is displayed:

    Agent successfully initialized

  4. Look for agent activity in the AgentStatus.log file.

    As the APM Java agent starts gathering and uploading trace data to Application Performance Monitoring, it logs short status messages in the AgentStatus.log file. This indicates that the APM Java agent is active.

If the above verification steps fail, check that the running process for the application server has the javaagent in the command line.

For example: Execute the below command to list the application server process with the APM Agent:
ps -ef | grep ApmAgent
If the above command does not list the application process, ensure that any environment variable is not overriding the application server startup options. For example: If you are using Apache Tomcat, ensure the CATALINA_OPTS is not overriden elsewhere via setenv.sh or any external setting.