Splunk AppDynamics

Java agent Configuration Options and Precedence

adrianblakey
New Member

Is the precedence of configuration options "correct"? 

From this: https://docs.appdynamics.com/display/PRO45/Administer+the+Java+Agent

I understand and have verified that system properties are overridden by environment variables. This is exactly the opposite of what I would expect and would like and is different from every other convention I have encountered.

It also makes it hard to do things like setting up a default configuration baked into a docker image and be able to override those settings in a "run.sh" script on the java command line.

Labels (1)
0 Karma

iamryan
Community Manager
Community Manager

Hi Adrian,

I spoke with some staff and they have confirmed with me, "Environment variables have precedence over the system properties."

With that in mind, customers may log in to view, vote, and comment on Ideas here:

https://community.appdynamics.com/t5/Idea-Exchange/idb-p/ideas

Before posting, please have a read of the guidelines here: https://community.appdynamics.com/t5/Knowledge-Base/Idea-Exchange-Submission-Guidelines/ta-p/38092

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 ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...