Customize Java Agent naming based on Application.
Article ID: 17161
Updated On:
Products
Issue/Introduction
Each Java Agent running in your Introscope environment has a name, whether assigned explicitly, configured a method of automatically assigning a name, or simply started an instrumented application that the Java Agent monitors.
The Java Agent name is central to many views in the Introscope Workstation and Investigator, and it is key to the process of associating monitoring logic with target applications.
Why is the Agent name not picked up when setting introscope.agent.agentNameSystemPropertyKey property?
Environment
APM 10.xWebsphere
Resolution
There are a few possibilities as to why this could be happening.
1. The flag -Dcom.wily.introscope.agent.agentName has been added to the WAS startup script. Any -Dcom.wily property will supersede any setting in the IntroscopeAgent.profile
-Dcom.wily.introscope.agent.agentName=<myagentname>
OR
2. It is possible that the flag has been added after the JVM arguments and the property in the Agent profile 'introscope.agent.agentNameSystemPropertyKey' is not set. In this case, either set the -Dcom.wily.introscope.agent.agentName in the JVM arguments or set introscope.agent.agentNameSystemPropertyKey=<myagentname> in the Agent profile.
Or
3. If you use certain versions of WebLogic or WebSphere, the agent name can be automatically obtained from the application server using automatic agent naming functionality. However if not set up properly, then the name will not be passed to the Agent, thus having the Agent show as "Unknown Agent". In this case you would use the below property in IntroscopeAgent.profile and set your Agent name.
introscope.agent.agentNameSystemPropertyKey=<myagentname>
Additional Information
Feedback
