Syed Share the machine agent logs if you can. Without that it would be diffcult to tell what happened. ... View more

Hi, Technically there shouldn't be any issue running a Db agent on controller machine. Since the Db agent process will be running standalone. However recommend not to run the Db agent on controller machine as it would add overhead to your controller machine.  Db agents require some minimum heap space to monitor Database instance.  That is, 1 GB of heap space and an additional 512 MB of heap space for each monitored database instance. Example, Monitoring 5 databases instances requires ( 5 x 512 MB ) + 1024 MB = 3,584 MB of heap space and this is definitely going to stress you controller hardware.  Better run the Db agent on a separate host. Thanks, VJ ... View more

@ankjain You can try to use only 1 machine agent package however run 3 different machine agent process to pair and associate with your 3 JVms each of which is pointing to different Tier. In the machine agent config DON'T specify app name, tier or node name.  Just start 3 different machine agent process by just passing uniqueHostId only. This way each machine agent process should pair and associate with each JVMs reporting in different tiers.  Let me know how it goes. Something like below nohup <path_to_java>/bin/java -Dappdynamics.agent.uniqueHostId=myapp1 -jar <path_to_machineagent>/machineagent/machineagent.jar & nohup <path_to_java>/bin/java -Dappdynamics.agent.uniqueHostId=myapp2 -jar <path_to_machineagent>/machineagent/machineagent.jar & nohup <path_to_java>/bin/java -Dappdynamics.agent.uniqueHostId=myapp3 -jar <path_to_machineagent>/machineagent/machineagent.jar & ... View more