Discussion Feed

If you have available Server Visibility licenses (separate from machine agent licenses) then to enable server vis on those machine agents you'll need to go into the controller-info.xml file and flip the following attribute to "true" to enable that machine agent o report itself in correctly: <sim-enabled>true</sim-enabled>   To verify you have the right licenses, go into your Controller GUI, click on the cog wheel in the top right, and then go to "License" and check under "Infrastructure Visibility" ... View more

Looks like it's working correctly, what you're seeing are the calls it is making.  What exactly are you wanting? Are you wanting to configure the identification rules? Those can be found on he left-hand side of your application under Configuration > Instrumentation. ... View more

Are you sure you're starting the correct javaagent.jar? No logs generally means the agent didn't start. Did you follow all the steps in this document? https://docs.appdynamics.com/display/PRO45/Install+the+Standalone+Machine+Agent   ... View more

You should be able to compare your scripts. In your Controller, when you go to User Experience > APPLICATIONNAME > Configuration > Configure JavaScript Agent, under 3. Save Config and Generate HTML Snippet, you should see a line similar to this: <script src='//cdn.appdynamics.com/adrum/adrum-4.5.13.2640.js'></script> (or whevever you're hosting your adrum)   If you look at the code you're serving up in your application header you should be able to compare the adrum-4.5.13.2640.js to yours.   ... View more

Essentially it's just a javascript injected in the header of your application, so the delay in IE might be in the way or order that it tried to run through the header. It'll be an interesting experiment to try and run F12/inspect element on an IE and a couple other browsers when running your application site to see if there is a difference.   As for the adrum, are you locally hosting your own or using the AppDynamics cdn? If it's local (or an old one) that may account for the delay?  ... View more

Since you're using a config file (.yml) and not the env, make sure you're using the correct syntax, I don't think you use " in .yml. Also, I'm assuming in your code, you're actually passing a correct port, account and access key, and not just "test?"  Here's the documentation which may help: https://docs.appdynamics.com/display/RUBY/Install+the+Ruby+Agent   ... View more

If I understand your question correctly then what you'll want to do is install a Database Agent on your Controller (or some other place where your DB server can reach). You can find a diagram of how it works here: https://docs.appdynamics.com/display/PRO45/Overview+of+Database+Visibility From there you can setup individual "collectors" inside the Controller GUI which essentially makes monitoring individual DBs agentless from a db server perspective. The notes on how to install the agent are here: https://docs.appdynamics.com/display/PRO45/Install+the+Database+Agent and once you have it up and correct sa permissions you setup the collectors for each individual db here: https://docs.appdynamics.com/display/PRO45/Add+Database+Collectors   ... View more

I'm a bit new to the cluster agents myself, but my understanding is that the Cluster agent is newer and so it provides a bit more detail into the pods and clusters, it's also a different license. Whereas the traditional machine agent with server visibility enabled is the traditional approach for non-containerized environments. When you deploy a machine agent into your build process it requires a lot more overhead to upkeep them, but a cluster agent gets added as a mount with a shared .yml in your build process and so it gets managed and distributed much more easily. ... View more