Discussion Feed

Hi Jeremy,   We confirm we already have a feature request in road map as of now no ETA yet on this. ... View more

Hi John,   By default internal agent is configured to my understanding and the related entry is in domain.xml at path <Controller_install_dir>/appserver/glassfish/domains/domain1/config/ path like below under xml section <config name="server-config"> and the path of agent directory is  <Controller_install_dir>/appserver/glassfish/domains/domain1/appagent/ and it is auto filled with config details during installation of controller itself.   <jvm-options>-javaagent:${com.sun.aas.instanceRoot}/appagent/javaagent.jar</jvm-options>   Regarding no load on flow map query: We see it could be that either agent have reporting issue OR transaction config for Servlet/ EJB/ auto discovery entries are disabled, Can you check below:   1) Under Configure -> Instrumentation -> Transacion detection screen, check if "app server" tier have Servlet and EJB both entry and auto discovery checkbox section are enabled, if using new config 2.0 view, edit "java auto discovery rule" and check above entry settings and enable checkbox if not enabed in UI and see how it goes. (refer sample section we are referring in attached view)   2) If 1) does not help share agent node logs folder for our review in this post we will suggest next steps, That is attach logs folder from  <Controller_install_dir>/appserver/glassfish/domains/domain1/appagent/ <ver>/logs/Node1/ path   Regards, Arun   ... View more

Hi Venkat,   I could not locate any such docs, we see 4.3.x is still available as of now in our download site, however as the agent is couple of years back around mid year of 2017 released we request users to upgrade agent on next scheduled restart , first try agent upgrade on couple of instance instead all at once and if agent upgrade on few instance went well try agent upgrade on other instances.   We have few customers using old agent version we still support debugging but if you face any functionality issue we encourage users to upgrade agent and check behaviour as many enhancements and fixes are in place in recent version. ... View more

Hi Archana,   We see as of now java AppServerAgent.zip installation monitored JVM instance itself, that is all requests part of target JVM process with multiple web application deployed. We suggest to configure -javaagent entry on JVM with target two apps deployed as part of JVM startup setting and try below steps:   - As each web application have its own context URI say /bankapp /orderapp are two web context name of two different apps for all sub requests like /orderapp/login /bankapp/checkout, we suggest to create a Servlet rule matching context name so that all requests for one app will be grouped as single BT   - You can use split for other segments as in sample view attached above, see if that information helps.   https://docs.appdynamics.com/display/PRO44/Install+the+Java+Agent https://docs.appdynamics.com/display/PRO44/Monitor+JVMs   ... View more

Hi,   We understood you are referring to view below in UI and if above is the case and if you are looking for each process level using machien agent SIM feature, we see using SIM we get class level instead each process as of now, We suggest to see if using extension below helps? https://www.appdynamics.com/community/exchange/extension/process-monitoring-extension/ that is see if customising below setting in config.yml under monitor config helps here? # regex/pid/pidFile - process is fetched using this field instances: ... View more