Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
09-30-2021 01:33 PM
We've had good success auto-instrumenting an all-java kubernetes application with the cluster agent, but require the ability to use a custom APPDYNAMICS_AGENT_NODE_NAME. During manual instrumentation, this property can be set as an ENV in the container the java agent is attaching to, but it's not clear from the documentation the way to do this from the cluster agent config.
I am utilizing the latest cluster agent operator and cluster agent, with a cluster-agent.yaml as follows:
```
apiVersion: appdynamics.com/v1alpha1
kind: Clusteragent
metadata:
name: k8s-cluster-agent
namespace: appdynamics
spec:
appName: "demo"
controllerUrl: "http://xxx.com:80"
account: "xxx"
logLevel: "DEBUG"
# docker image info
image: "docker.io/appdynamics/cluster-agent:latest"
serviceAccountName: appdynamics-cluster-agent
nsToMonitor: [demo]
instrumentationMethod: Env
nsToInstrumentRegex: demo
appNameStrategy: manual
defaultAppName: demo
#defaultCustomConfig: "-Dappdynamics.agent.nodeName=manual-test"
defaultEnv: JAVA_TOOL_OPTIONS
resourcesToInstrument: [ Deployment, StatefulSet ]
instrumentationRules:
- namespaceRegex: demo
language: java
appName: demo
# customAgentConfig: -Dappdynamics.agent.nodeName="manual-test"
# customAgentConfig: -Dappdynamics.agent.nodeName=${APPDYNAMICS_AGENT_NODE_NAME}
customAgentConfig: APPDYNAMICS_AGENT_NODE_NAME="manual-test"
imageInfo:
image: docker.io/appdynamics/java-agent:20.3.0
agentMountPath: /opt/appdynamics
With all 3 variations of the customAgentConfig above and an APPDYNAMICS_AGENT_NODE_NAME in the target deployment set. Any help would be much appreciated
06-25-2022 05:12 AM
03-18-2024 10:32 AM
Also looking for a solution to this and for using a variable with:
customAgentConfig: -Dappdynamics.agent.reuse.nodename.prefix=$name
I can set this to a specific name, but would like for the microservice name to be picked up instead so I can have one entry in my yaml config.
03-18-2024 11:40 AM
This ended up working for me, I add the below to my CA yaml.
customAgentConfig:
-Dappdynamics.agent.reuse.nodeName=true
-Dappdynamics.agent.reuse.nodeName.prefix=$(APP_NAME)
03-19-2024 09:27 AM
Hi @Marcie.Sirbaugh,
Thanks for following up and sharing your solution! I love to see it.
Thanks,
Ryan, Cisco AppDynamics Community Manager
Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.
Check out Observabiity in Action
new deep dive videos weekly in the Knowledge Base.
User | Count |
---|---|
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form