What are the steps to deactivating the integration when the SAP ABAP Agent is causing system dumps? If the ABAP Agent is causing the system dump, deactivate the integration ( /DVD/APPD_CUST ) and troubleshoot the issue using the following steps:   Deactivate the integration Check the HTTP SDK status Deactivate the integration WARNING | Please do not change any other settings. Only deactivate the integration using the following steps if the ABAP Agent itself is causing system dumps: Execute the /DVD/APPD_CUST transaction to open the AppDynamics settings screen. On the AppDynamics settings screen, you will click the Display <-> Change button to go into edit mode Click the Display <-> Change button in the top-left of the menu bar to go into edit mode. You will notice the UI changes. Click the Deactivate integration button, which will deactivate the integration immediately. On the AppDynamics settings screen in Edit mode, you will be able to click the Deactivate integration button to immediately deactivate the integration Back to Top Check the HTTP SDK status Finally, check the HTTP SDK status (transaction /DVD/APPD_STATUS ), analyze the logs, and take the proper remedial action. Execute the /DVD/APPD_STATUS transaction to open the AppDynamics SDK status screen. On the “AppDynamics HTTP SDK status check” screen, you will be able to review connection status, restart, and stop the service From here, you can: • Check to see whether the HTTP SDK is reached  • Check to see whether the process is running • Start/Restart the process • Stop the process   From the AppDynamics HTPP SDK proxy log files screen, save the logs to a local file and review them. If you are unable to triage the issue and need help from AppDynamics Support, you will likely need to provide the logs and send them to AppDynamics support for analysis as a first step. Click the Save button on the “AppDynamics HTTP SDK log files” screen to download selected logs. Click the Save button on the “AppDynamics HTTP SDK log files” screen to download selected logs Back to Top ... View more

What do I need to know about configuring a Java Agent to monitor a Spring Boot application? When configuring a Java Agent to monitor a Spring Boot application, you need to configure the Java Agent parameter before the Spring Boot application JAR file.  Example:  java -javaagent:<agent-install-dir>/ver4.x.x/javaagent.jar -jar application.jar ... View more

Issue  On some of your JVM environments, Garbage Collection (GC) metrics are not reporting out of the box. Observations The agent collects and reports the GC metrics based on the related MBeans exposed by the underlying JVM. If the JVM does not return the related Mbeans, then GC metrics will not be reported by the agent. In this case, the agent logs will report the messages below:  [Thread-0] 06 Feb 2018 07:06:23,529 WARN MemoryMetricGenerator - Current JVM GC MX Beans - GPGC New, GPGC Old, not registered with JMX Service.Please add the appropriate minor collection bean name to JMX Service property key name : jmx-gc-minorCollectionBean [Thread-0] 06 Feb 2018 07:06:23,529 WARN MemoryMetricGenerator - Current JVM GC MX Beans - GPGC New, GPGC Old, not registered with JMX Service.Please add the appropriate major collection bean name to JMX Service property key name : jmx-gc-minorCollectionBean Solution 1 You will need to analyze the GC mechanisms used by the JVM by verifying with JConsole or any other JMX tool. Refer to the attached screenshots for an example.  Identify the GC mechanism and configure it in the " app-agent-config.xml " file under "JMXService" configurations. Example: <agent-service name="JMXService" enabled="true"> <configuration-properties> <property name="jmx-gc-minorCollectionBean" value="PS MarkSweep"/> <property name="jmx-gc-majorCollectionBean" value="PS MarkSweep"/> <property name="jmx-server-metrics-update-interval-in-seconds" value="60"/> </configuration-properties> Restart the JVM for the changes to take effect. Solution 2 You can create custom JMX metrics as follows, although you may need to use the JMX browser to confirm the exact names. Minor Collection Major Collection ... View more

Issue Business transactions are being marked as errors, but the error details are not showing on transaction snapshots. Observation This could be due to the error registration limit on the agent side. In the agent logs, you may see this message: INFO ErrorRegistry - ErrorRegistry ADD registration limit has been reached, dropping error object Resolution If you see this error, you will need to register the node property below and set the value to >500. Node Property : max-error-add-registration-limit Type : Int Value : 500 (default) ... View more

How can Linux or Windows users pass startup parameters to their Machine Agents? This article contains instructions for passing startup parameters, such as proxy details, to Machine Agents in Linux, or in Windows. Table of Contents Passing startup parameters to a Machine Agent in Linux Passing startup parameters to a Machine Agent in Windows Passing startup parameters to a Machine Agent in Linux Linux users who wish to pass startup parameters such as proxy details to their Machine Agent have two options: during Machine Agent startup, or in the run time file.   Passing during Machine Agent startup Stop the Machine Agent. Depending on how you are starting Machine Agent, these JVM parameters can be added in startup command. For instance: When starting the Machine Agent from bin folder, JVM arguments will be passed as: ./machine-agent -Dappdynamics.http.proxyHost=XXX -Dappdynamics.http.proxyPort=80​ When starting machineagent with  machineagent.jar file, JVM arguments will be passed as: java -jar machineagent.jar -Dappdynamics.http.proxyHost=XXX -Dappdynamics.http.proxyPort=80​ Back to Table of Contents Passing in the run-time file Stop the Machine Agent. Navigate to the <Machine Agent -Dir>\bin directory. Do a  VI of file machine-agent . In the VI editor, search for this line: JAVA_OPTS="$JAVA_OPTS -Xmx256m"​ You should see that the -Xmx JVM  argument is passed. After you pass the proxy settings, it will look like this:  JAVA_OPTS="$JAVA_OPTS -Xmx256m -Dappdynamics.http.proxyHost=XXX -Dappdynamics.http.proxyPort=80" Save the file. Restart Machine-Agent . Back to Table of Contents Passing startup parameters to a Machine Agent in Windows Windows users who wish to pass startup parameters (such as proxy details) to their Machine Agent should follow these steps: Stop the Machine Agent service. Navigate to the  <Machine Agent -Dir>\bin directory. Create a new empty file called MachineAgentService.vmoptions . Navigate to the  <MachineAgent Home>/InstallService.vbs file and add the following lines of code before vmOptionsFile.WriteLine: vmOptionsFile.WriteLine("-Dappdynamics.http.proxyHost=XXX") vmOptionsFile.WriteLine("-Dappdynamics.http.proxyPort=80")​ For example: Set vmOptionsFile = fsObject.OpenTextFile(scriptDir & "\bin\MachineAgentService.vmoptions", OVERWRITE, True) vmOptionsFile.WriteLine("-Dappdynamics.http.proxyHost=internet_proxy2.via.novonet") vmOptionsFile.WriteLine("-Dappdynamics.http.proxyPort=80")​ NOTE: Do not create "MiniDump on crash". If the option is not supported by the JRE, the executable will ignore it. vmOptionsFile.WriteLine("-XX:-CreateMinidumpOnCrash")​ Save the changes. Restart the service.  Back to Table of Contents   ... View more

Agent stopped reporting the metrics and no load observed on controller UI. Log message : INFO ConfigurationChannel - Setting disable-agent to true Possible reasons : 1. Disable the javaagent on "Agent Configure " screen by selecting "Off" button. 2. Configure the "Action Suppression" to disable the node.PFA, the screenshot for the same. ______________________________________________________ Was this helpful? Give it kudos [click on the thumbs up icon at the end of the article, bottom left corner] to let others know too! Do you have a question or need clarification? [Post Your Comment] Below.  ... View more

Hp Exstream uses oSGI framework, so when you configure the Java Agent you need to configure bootdelegation parameter in HP Exstream configuration files. Startup parameter : -Dorg.osgi.framework.bootdelegation=com.singularity.* Files to modify ...   custom.properties and config.properties ____________________________________________________ Was this helpful? Give it kudos [click on the thumbs up icon at the end of the article, bottom left corner] to let others know too!   Do you have a question or need clarification? [Post Your Comment] Below.  ... View more

Problem Request Segment Data Queue holds the request snapshots captured by agent and sends details to controller every minute. For that minute, agent will hold all the request segment data in a queue and send it at one go. If there are many snapshots collected, the queue may not hold everything. So in that case, it might drop the snapshots and that is what is reflected in the logs below ...     Sample logs  [AD Thread Pool-Global0] 09 Feb 2017 00:05:20,134 Request Segment Data reporter queue length limit of 1000kb reached. [AD Thread Pool-Global0] 09 Feb 2017 00:05:20,135 Request Segment Data reporter queue length limit of 1000 reached. Dropping snapshots. You may consider increasing the value of 'max-snapshot-reporter-queue-size-kb' in app-agent-config.xml   Solution 1) Stop the agent 2) Add the listed line along with other properties in app-agent-config.xml file Example: <property name="max-snapshot-reporter-queue-size-kb" value="2000"/> 3) Start the agent   __________________________________________________________________________________ Was this helpful? Give it kudos [click on the thumbs up icon at the end of the article, bottom left corner] to let others know too!Do you have a question or need clarification? [Post Your Comment] Below.  ... View more

Gradle scripts are useful to build and deploy applications. If we would like to monitor applications, we need to configure the javaagent on Gradle scripts. Steps: 1. Edit build.gradle 2. Need to include javaagent and configuration using "applicationDefaultJvmArgs". 3. To add javaagent..... applicationDefaultJvmArgs = ["-javaagent:/Users/narendranath/Documents/AppServerAgent-4.3.3.2/ver4.3.3.2/javaagent.jar"] 3. To add javaagent configurations dynamically , then ... applicationDefaultJvmArgs = ["-javaagent:/Users/narendranath/Documents/AppServerAgent-4.3.3.2/ver4.3.3.2/javaagent.jar", "-Dappdynamics.agent.applicationName=NewRibbonApp", "-Dappdynamics.agent.tierName=AppTier", "-Dappdynamics.agent.nodeName=AppNode"]  _______________________________________ Was this helpful? Give it kudos [click on the thumbs up icon at the end of the article, bottom left corner] to let others know too! Do you have a question or need clarification? [Post Your Comment] Below.  ... View more

What do I do when the Agent is not able to communicate to the Controller due to connectivity issues? Observations In logs, we see the following messages: [Thread-0] 22 Nov 2017 09:09:43,469 ERROR ConfigurationChannel - Exception: athenetest.saas.appdynamics.com:443 failed to respond org.apache.http.NoHttpResponseException: athenetest.saas.appdynamics.com:443 failed to respond Fix Check the "SSLEnabled" property in the controller-info.xml or any dynamics parameters configured in startup files. Ensure that "SSLEnabled" was set to "true" in the case of "https" and "false" in the case of "http". ... View more

How do I configure Akana gateway using java agent? To learn how to instrument Akana gateway using Java agent, begin by reading http://docs.akana.com/ag/index.html Configure javaagent in "startup.sh" located in "/opt/<Akana foler>/pm84/bin" path Search for "export JAVA_OPTS" Add the below line , before "export JAVA_OPTS" export JAVA_OPTS="$JAVA_OPTS -javaagent:<javaagent path>/javaagent.jar As Akana Gateway is based on OSGi framework, you'll need to apply the bootdelegation configurations in "config.properties" as below org.osgi.framework.bootdelegation=package1,package2,.....,com.singularity This article includes the following files: sample startup.txt (refer it as startup.sh ) config.properties ... View more

How do I resolve a Controller error message for exceeded custom metric limits for DB monitoring? Users unable to add new custom metrics using the database monitoring tool may see the following error displayed in the Controller UI: Error message This issue occurs when the default limit for database monitoring has been reached.  By default, database monitoring supports up to 20 custom metrics per database. When this limit is reached, the tool will not create any new custom metrics and the above error is displayed. To resolve this issue, the user can configure the following property to a higher value.  Within the Controller UI, using root login, access the  admin.jsp page and change the following property value: dbmon.config.max.custommetric​ Click Save Example Configure custom metrics  ... View more

Problem: When a SQL statement is truncated, the full statement is not displayed in a snapshot. By default, a snapshot will only display up to 999 characters from a SQL statement. Solution: Create a node property with the following information, and set it to a higher value than 999 in order to display the complete SQL statement. property: max-length-batch-sql desc: max-length-batch-sql type: Integer value: 2000 ... View more