Discussion Feed

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

Scenario:   A legacy Machine Agent and Java Application Agent are installed on a machine. Despite correct installation and configuration, one or both of the Agents do not report. The first step in troubleshooting this issue is to validate the Unique Host ID, which is a problem more common with Machine Agents.   Machine Agents use the Java API to get the Unique Host ID. Sometimes the same JVM can return different values for the same machine each time the Machine Agent is restarted. One possible cause is the  Unique Host ID of the App Agent and the Machine Agent are not in sync. In this case, the Machine Agent does not know which application to register.     Validate:   Search for the application or the Unique Host ID on both the Application and Machine Agents, and make sure that the values are the same. Examples:  To confirm the issue, go to the Agent settings page located at either of the following URLs:   http://<host:Port>/controller/#/location=SETTINGS_AGENTS http:// <host:Port> /#/location=SETTINGS_MACHINE_AGENTS  Also, verify that the Machine Agent is associated with the application.      Solution:   If there is any discrepancy between the two Agents, resolve the issue by providing the  same Unique Host ID value for the App Agent and the Machine Agent using the following steps.   Note: If it is not feasible to stop the App agent, it is possible to sync the Unique Host ID value of the Machine Agent with the App Agent, and then apply the property to the App Agent on the next restart.   Stop both Agents. Start the App Agent with the following property: -Dappdynamics.agent.uniqueHostId=<your-host-id> system property Confirm that there are no new errors or issues with the App Agent. Start the Machine Agent with the same property: - Dappdynamics.agent.uniqueHostId=<your-host-id> system property Another option is to add a <unique-host-id>your-host-id</unique-host-id> element within the <machine_agent_install>/conf/controller-info.xml file. ... View more

Custom metrics allows the user to specify a SQL query to run on a monitored DB every minute, and collect the results of the query.   This document specifies restrictions and limitations, as well as some examples and debugging techniques.    Restrictions and Limitations:   The query must always return a positive integer number. The query should not return more than one column. The user can define up to 20 custom metrics per monitored DB. This limit is configurable through admin.jsp with the following property; however, it should be increased graciously. For Security reasons, we only allow SELECT queries.     How to debug?     If the Agent encounters an error while running the query, the Agent will send an error event to the Controller. View these error events by clicking on Database -> Events in the Controller UI. For more details on an error, view the database Agent logs located at <db_install_dir>/logs . The errors are self-descriptive and can be searched using the keywords " CustomMetricsCollector," "ERROR," or "WARN." Examples: [<MyTestMysql>-Scheduler-3] 29 May 2017 11:04:59,702 ERROR CustomMetricsCollector - Error collecting data for database 'MyTestMysql' java.sql.SQLException: Invalid custom metric: test4 , actual data type is non-numeric and expected data type is numeric (Custom Metric : test4) 09 Jun 2017 13:40:08,889 ERROR [<Database>-Scheduler-1] CustomMetricsCollector:130 - Error collecting data for database 'Database' java.sql.SQLException: DB2 SQL Error: SQLCODE=-952, SQLSTATE=57014, SQLERRMC=null, DRIVER=4.16.53 (Custom Metric : TestMetric)     Query Examples with MySQL:   1.select COUNT(1) "total" from dual; - Worked output: 1 2. select 9+ ' ' +':00' num from dual; - Worked . output: 9  3. select name from user where id=3 - Not working as expected Output: root   4.  select id as node_id from application_component_node where id NOT in (select distinct(node_id) from metricdata_hour where ts_min > ((select max(ts_min) from metricdata_hour)) - 60*2) - Worked/Not Worked based on output Output: Fails if returns multiple records       Related Links: Database monitoring metrics Configuring custom metrics         ... View more