Various UMA and RemoteJMX Questions

Products

• DX Application Performance Management

Issue/Introduction

Q1 Why does the property jmx: enabled: true appear in the uma_cr.yaml file, but JMX metrics do not appear?

 Q2. We have defined the environment variable com.wily.introscope.agentProfile as seen in the deployment-quarkus.yml file, yet it still takes the Micro profile. Why is this happening?"

 Q3. If in the deployment-quarkus.yml file we wanted to add another property to the annotation ca.broadcom.com/autoattach.java.agent.overrides:, what would the syntax be?

 

Resolution

A1.  By default, UMA is configured to use IntroscopeAgentMicro profile and does not report JMX metrics. For better performance, we suggest to use remote JMX configuration for UMA. Our dev team and techpub team are working to update the online documentation with better clarifications and option details for configuring JMX metrics.

A2.  This is likely due to the system property specified to use IntroscopeAgentMicro profile having precedence over the corresponding environment variable for specifying a custom agent profile. The online documentation is changing.

A3. Since the annotation ca.broadcom.com/autoattach.java.agent.overrides supports a comma-delimited list of agent property specifications, it will not work well with agent property value also containing a comma. As a workaround, the customer can consider defining the agent property via its corresponding environment variable.