Discussion Feed

Issue When clicking on certain screens in the Controller, you may encounter the message "Please install Flash to use this feature." This is due to the fact that a few screens in the Controller UI leverage Flash and require Flash Player 10 or greater. AppDynamics recommends version 11.   This behavior is specific to Chrome and you must explicitly enable Flash. While we are moving away from Flash to HTLM5, there is no ETA on when Flash will be completely removed.   Solution To resolve this, click on lock icon to the left of the address bar. Under the Flash select, click "always allow on this site." You will be prompted to reload the page, after which you should no longer see this message.      Alternatively, go to chrome://settings/content/flash and add the controller URL as an "allowed" site.     ... View more

To configure missing entry points for any business transactions (BTs) that are not detected out of the box, set the  find-entry-points node property to true. See the step-by-step instructions below.   This will dump all eligible entry points with priority to the business transaction logs, which are located in the agent logs directory.   Once eligible entry points have been identified, custom entry points can be created based on them.    Note: This method works only when the application invokes methods supported by AppDynamics, such as HTTP exit calls, or SQL exit calls. The output of the find-entry-points property is a thread call stack each time an exit point or detected thread handoff happens without a business transaction. Within these stacks are candidates to act as BTs.   Instructions:   Navigate to node-level agent configuration and set the   find-entry-points   property   to true. For more information on how to edit a node-level property: Edit a Registered Node Property Apply the property either tier-level or node-level. Note: Do not turn on this property tier-level within a production environment. The find-entry-points property is meant to be used under pre-prod and non-prod environments. Once the property is applied, apply sufficient load on the application and start collecting agent logs from the Controller UI, or view them from agent installation folder. Debug logging is not needed for this property.  A complete call stack from the instrumentor to the top of the thread will dump to the  BusinessTransactions<X>.log file. Example: BusinessTransactions.2017_11_27__12_54_08.0.log The BT log mixes the output of find-entry-points with the "normal" BT discovery logging.  To distinguish between the two types of call stacks, identify the text after the INFO log level keyword.  Example : [pool-1-thread-1] 17 Oct 2016 18:02:09,758  INFO - Logging request stack for Thread pool-1-thread-1 >>    Entire stack trace with eligible entry point prioritized: com.squareup.okhttp.internal.http.HttpEngine.<init>(HttpEngine.java:190) ... com.xyz.abc.service.rest.standard.abcDefaultApi.execute(abcDefaultApi.java:136) com.xyz.abc.service.rest.standard.abcRestService.healthCheck(abcRestService.java:217) com.xyz.abc.domain.pqr.Health.checkHealth(Health.java:83) com.xyz.abc.domain.pqr.Health.run(Health.java:125) java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) java.util.concurrent.FutureTask.run(FutureTask.java:266) .... java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) java.lang.Thread.run(Thread.java:745) Based on this output, the user can find eligible candidates and create custom POJO entry points.   [pool-2-thread-1] 26 Dec 2017 21:18:01,794 INFO - 0. POJO com.xyz.abc.domain.pqr.Health run [pool-2-thread-1] 26 Dec 2017 21:18:01,794 INFO - 1. POJO com.xyz.abc.domain.pqr.Health checkHealth [pool-2-thread-1] 26 Dec 2017 21:18:01,794 INFO - 2. POJO com.xyz.abc.service.rest.standard.abcRestService healthCheck [pool-2-thread-1] 26 Dec 2017 21:18:01,794 INFO - 3. POJO com.xyz.abc.service.rest.standard.abcDefaultApi  One can create a custom POJO entry point on class  com.xyz.abc.domain.pqr.Health and method run. In the above example, 0th is considered as most eligible entry priority. Based on the output, a custom entry point rule can be created on any type (ex: Servlet, EJB, Spring or POJO).  More information: Custom Match Rules.   Note: Setting the property value to true causes verbose logging to be output until the value is switched to false, so it is unwise to leave this property value set to true.  ... View more

L aunch the NSA console  Navigate to CSA properties -> Application tab Under "Application Server" select Apache Tomcat as the vendor and edit the Java VM parameters as follows: Add AppDynamics Agent entry:   -javaagent:<agent_home>/javaagent.jar   For more information: Load the Java Agent in a JVM    ... View more

After upgrading or installing AppDynamics version 4.3.x, users may see the following error  when accessing the "Servers" tab in the Controller UI.   Error: The requested URL /controller/restui/userPreferenceManager/setGeneralUserPreference/SIMMachinesListController-stateId--SIM_MODE-4.3-metricToggles/[{"selected":false,"label":"Availability (%)","type":0,"metricName":"Hardware Resources|Machine|Availability"},{"selected":false,"label":"Availability (%) Trend","type":1,"metricName":"Hardware Resources|Machine|Availability"},{"selected":true,"label":"CPU (%)","type":0,"metricName":"Hardware Resources|CPU|%Busy"},{"selected":true,"label":"CPU (%) Trend","type":1,"metricName":"Hardware Resources|CPU|%Busy"},{"selected":false,"label":"CPU Steal (%)","type":0,"metricName":"Hardware Resources|CPU|%Stolen"},{"selected":false,"label":"CPU Steal (%) Trend","type":1,"metricName":"Hardware Resources|CPU|%Stolen"},{"selected":true,"label":"Disk I/O (%)","type":0,"metricName":"Hardware Resources|Disks|Avg IO Utilization (%)"},{"selected":true,"label":"Disk I/O (%) Trend","type":1,"metricName":"Hardware Resources|Disks|Avg IO Utilization (%)"},{"selected":true,"label":"Disk Usage (%)","type":0,"metricName":"Hardware Resources|Volumes|Used (%)"},{"selected":true,"label":"Disk Usage (%) Trend","type":1,"metricName":"Hardware Resources|Volumes|Used (%)"},{"selected":false,"label":"Load - 1min","type":0,"metricName":"Hardware Resources|Load|Last 1 minute"},{"selected":false,"label":"Load - 1min Trend","type":1,"metricName":"Hardware Resources|Load|Last 1 minute"},{"selected":true,"label":"Memory (%)","type":0,"metricName":"Hardware Resources|Memory|Used %"},{"selected":true,"label":"Memory (%) Trend","type":1,"metricName":"Hardware Resources|Memory|Used %"},{"selected":false,"label":"Memory Swap Used (%)","type":0,"metricName":"Hardware Resources|Memory|Swap Used %"},{"selected":false,"label":"Memory Swap Used (%) Trend","type":1,"metricName":"Hardware Resources|Memory|Swap Used %"},{"selected":true,"label":"Network I/O (%)","type":0,"metricName":"Hardware Resources|Network|Avg Utilization (%)"},{"selected":true,"label":"Network I/O (%) Trend","type":1,"metricName":"Hardware Resources|Network|Avg Utilization (%)"}] was not found on this server.   Screenshot:       The cause of this issue is due to some versions of Apache being unable to parse slashes in POST query parameters.   As of version 4.3, the view options are persistent for users. To do this, AppDynamics keeps track of what tab the user selected last time using an API call. This is a POST request, with query parameter of '/' which cannot be parsed by Apache, unless it is defined in the config file.   The solution is to turn on the AllowEncodedSlashes NoDecode  option in the Controller server's Apache config file ( httpd.conf) .   For more information, see this Stack Overflow discussion: Need to allow encoded slashes on Apache   ... View more

When creating database custom query metrics, if the queries are complex, they may return a timeout error message in the Database Agent logs.    For example from DB2 database:   Caused by: com.ibm.db2.jcc.am.SqlTimeoutException: DB2 SQL Error: SQLCODE=-952, SQLSTATE=57014, SQLERRMC=null, DRIVER=4.16.53   As a solution, a user can increase the timeout parameter by adding the following property in the DB Agent startup file, or as a system argument if DB Agent is started through a command prompt or terminal.    -Ddbagent.custommetric.query.timeout.seconds=<time_in_second>    Example: -Ddbagent.custommetric.query. timeout.seconds=120     ... View more

To set up a Java Agent to automatically give unique names to nodes for the application, add the following element to the /conf/controller-info.xml file.   <auto-naming> true </auto-naming>     Example using a 4.2.14.0 Agent:   Add the following element to the /AppServerAgent-4.2.14.0/ver4.2.14.0/conf/controller-info.xml file: <auto-naming>true</auto-naming> Restart the JVM. Node names will be listed as null in the Controller UI until the server is started. Naming convention is  application_server@host . ... View more

Problem:   When a non-admin user runs automatic leak detections (ALD), object instance tracking(OIT), or Custom memory structures, they may see the following error:   The current user 'ABC' does not have permission to do this. (action: CONFIG_AGENT_PROPERTIES entity: APPLICATION_COMPONENT_NODE 235) (agentManager.updateAgentConfiguration)   Solution:   An administrator must edit the Agent permission and role properties. The name of the permission can be extracted from the error message.   Example:     ... View more

When running WebSphere with Security Enabled, the user must provide permissions to the Java Agent, to ensure a seamless  interaction between the two.   Add the following snippet to the security policy file:   grant codeBase "file:\* AGENT_DEPLOYMENT_DIRECTORY \*/-"   {      permission java.security.AllPermission; };   The security policy file is located in the AppDynamics Agent logs under JVM arguments:     -Djava.security.policy=...../security.policy   Or Unix users can use the ps command to find the command line parameters for the JVM.   If the JVM argument is not provided, the application may be using a default Java policy file ( java.policy ). Add the previously mentioned snippet to this file.    Examples where applying permissions is not sufficient:   1. Agent logs show: java.security.AccessControlException: access denied ("java.io.FilePermission" "/xx/xx/xx/y.xml" "read")   grant codeBase "file:\* AGENT_DEPLOYMENT_DIRECTORY \*/-"  {    permission java.security.AllPermission;    permission java.io.FilePermission "*","read,write,execute";  };   2. Agent logs show:  java.security.AccessControlException: access denied (java.lang.RuntimePermission getClassLoader)   grant codeBase "file:\* AGENT_DEPLOYMENT_DIRECTORY \*/-"  {  permission java.security.AllPermission;  permission java.lang.RuntimePermission "getClassLoader"; };     3. Agent logs show: java.security.AccessControlException: access denied ("javax.management.MBeanServerPermission" "findMBeanServer")   grant codeBase "file:\* AGENT_DEPLOYMENT_DIRECTORY \*/-"  {  permission java.security.AllPermission;  permission javax.management.MBeanServerPermission "findMBeanServer"; };  Note: Replace  \*AGENT_DEPLOYMENT_DIRECTORY\* with the Agent home directory path. Do not miss the forward slash (/-) at the end.    Linux example:  grant codeBase "file:/opt/appdynamics/appserveragent/-" Windows example:  grant codeBase "file:c:/appdynamics/appserveragent/-"                    Additional solutions:    Add the following property as a JVM argument only on development instances. Remove this property as soon as security debugging is completed.  -Djava.security.debug="access,failure"   Additionally, create a node level property, which can coincide with the above security policy file changes.   Node property example: property name: enable-interceptors-for-security type: boolean value: true   Note:  Changes in the security policy file require a JVM restart.    ... View more

To configure Apache Solr version 6.5.x with AppDynamics Agent (preferably version 4.2.x or higher), use the following steps:   Navigate to /<solr-home>/bin/solr.in.sh on the Controller machine. Add the following snippet to the solr.in.sh file in order to add the Java Agent. SOLR_OPTS="$SOLR_OPTS -javaagent:<app_agent_install>/ver4.2.10.0/javaagent.jar" Example: SOLR_OPTS="$SOLR_OPTS -Dappdynamics.agent.applicationName=Solr -Dappdynamics.agent.tierName=SolrTier -Dappdynamics.agent.nodeName-javaagent:/Users/XXX/Documents/Agent/AppServerAgent-4.2.10.0/ver4.2.10.0/javaagent.jar" Restart Solr. ... View more