Hi Nick,
Please find our response to your queries inline:
>>>>> Firstly, is this possible with a single licence?
Answer: If you referring to license.lic under <controller_install_Dir>/ path having property property_no-of-app-agent-license-units=1 then you cannot as long the other agent is monitor still. But if the above mentioned property have more than value 1 and you are only monitoring 1 agent associated to controller, if this is the case, we confirm you can configure -javagent on test env with different node-name in addition to same controller host and port, (same/different) app,tier details to monitor the other jvm as well with upgraded agent.
>>>>> Secondly, will we lose the statistics for the production java agent if we shutdown the production java agent and hook in a dev java agent into the controller?
Answer: We confirm you will not lose the statistics for node dashboard in UI which earlier reported as long as you have not deleted the node from ui, we request you to use different node-name for dev/test environment to monitor JVM once you shutdown the production JVM so that you controller will consider that you are utilising only 1 java agent and if you have only 1 appserver agent license unit here.
Other option to associate node:
if you shutdown(Or removed -javaagent entry and restarted) the production jvm with agent configured and then you can point to same node-name in test env java agent but the node will also have both prod and test/dev agent reported data and this option will be fine if no machine agent node associated to same appserver agent node we are referring to. We recommend to shutdown or remove -javaagent on prod environment jvm and start dev with new node-name under controller-info.xml to avoid confusion in future.
Let us know if that answers your queries.
Regards,
Arun
