ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

APM 20 - Modifying agent config in container environments

book

Article ID: 212463

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

Do you know how other customers deal with updating properties inside extensions in containerised environments, i.e. if they are not using ACC? At the moment I have to untar, ungzip the whole package, change the bundle.properties and then tar/gzip it again, followed by encapsulating it into the sidecar container agent image, so not exactly straightforward.

Environment

Release : 20.2

Component : APM Agents

Resolution

Most agent properties including the bundle properties etc can be passed in as java arguments on the command line e.g.

 

For a WebSphere Liberty Agent the following arguments were set in the jvm.options file

-javaagent:/WLP/wily/Agent.jar
-Dorg.osgi.framework.bootdelegation=com.wily.*
-DagentName=Liberty19_0_0_5
-Dintroscope.agent.remotejmx.system.s1.mbeanPatternsWhiteList=WebSphere:*

The bundle.properties for the jmx extension had the value set as 

introscope.agent.remotejmx.system.s1.mbeanPatternsWhiteList=*:*

 

The only JMX metrics that then reported were the ones below the branch JMX|Default|WebSphere as per the definition in the passed in property

 

 

Bundles can be enabled/disabled  via passing properties in on JVM command line (assuming that are present in the agent hierarchy)