Splunk AppDynamics

JVM agent does not work

Kong_xiaohui
New Member

Hi,

I have installed the javaagent on my Linux server, and I append javaagent script after my startup script.

The whole script: "$JAVA_HOME/bin/java -jar /tmp/my-api.jar -ms64m -mx256m -javaagent:/opt/appdyn/javaagent/4.4.3.22593/javaagent.jar -Dappdynamics.controller.ssl.enabled=true -Dappdynamics.force.default.ssl.certificate.validation=true -Dappdynamics.agent.accountName=customer1 -Dappdynamics.agent.accountAccessKey=........ -Dappdynamics.controller.hostName=........ -Dappdynamics.controller.port=..... -Dappdynamics.agent.applicationName=........ -Dappdynamics.agent.tierName=my-api -Dappdynamics.agent.nodeName=_my-api"

my-api is a spring boot web application. After running this script, seems there is no log generated.

Labels (1)
0 Karma

Allan_Schiebold
Communicator

Hi. There is likely an error in the application logs about the app being unable to call the agent. This could be due to permissions issues. 

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...