Discussion Feed

Hi Neha   Would you be able to provide more information?   The Java Agent is added to the startup of the Application it's instrumenting, so a server restart would not affect the agent, as when the application starts , the agent will start with it.   Can you validate that the Appdynamics Java Agent is still part of the Application Java Process, you can check using any command e.g ps aux | grep "javaagent".   It might be possible that the following occurred 1. Java Agent directory itself was removed, or permissions changed with patching 2. Server firewall turned on, blocking the Java Agent from communicating to the Controller 3. Application was patched, which removed the Java Agent startup parameters.   Ciao ... View more

Hi Wayne   What type of Java application are you referring to?   AppDynamics has the built in capability to collect the Parameters, headers & Cookies using the Data Collector section within the Controller.   This will work for most supported servlets, webservices etc.   Ciao ... View more

Thanks Dennis   Might have been a bug that allowed that in your current version that you are running for some reason:)   Due to you having dependencies with regards to your LDAP Groups, it would be best to reach out to AppD Support to advise what the best way would be to manage your requirements, to not run into any problems going forward.   Hope you get some good feedback   Ciao ... View more

Hi Dennis   My apologies, I believe my previous reply was unclear.   I mean you can't create 2 application names which are identical between the different sections in AppD, The machine agent & App Agents are part of Core APM, and you can of course use the same application name to link all those agents together.   EUM is a separate component, and since Controller 4.3, it is no longer possible to use the same name under Applications & EUM.   This is by design, due to underlying Architecture.   Ciao     ... View more

Hi   That is how AppDynamics works, you cannot have 2 applications with the same name, across Normal Agents, EUM etc.   You can just name your EUM application "test_eum" or "test_web" or similar. It has no affect on the monitoring by not having 100% the same name.    Ciao ... View more

Hi Dennis   Would you possibly elaborate on what you are trying to achieve?   Ciao ... View more

Thank you @Claudia.Landivar , now on to the other certs:) ... View more

Hi Rakesh   I believe there can be an improvement to that page of documentation:), It makes the assumption that you know how to put the full script in the place where it needs to go.   Going forward, always create the EUM Application and it will provide you with the complete script you need to inject into your application   You access this, by going into the EUM application, click on configuration and then selecting Configure JavaScript agent.    ... View more

Hi Rakesh   You are missing the following sections in your script, the agent needs to know where to send the data to   Below is the EMEA Details, please add these in as my example above, redeploy and test again   config.adrumExtUrlHttp = "http://cdn.appdynamics.com"; config.adrumExtUrlHttps = "https://cdn.appdynamics.com"; config.beaconUrlHttp = "http://fra-col.eum-appdynamics.com"; config.beaconUrlHttps = "https://fra-col.eum-appdynamics.com";   When you open the web page, use developer options. In the network options after reloading the page, you should see 3 adrum pieces  Please see screenshot attached   I believe due to you not having the beacon section, it doesn't know where to send the data to.   The complete script with Beacon Details you should be able to find under Configuration of the EUM app, under Javascript instrumentation     ... View more