Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
Default JMX Metrics Example Some MBeans exposed by various supported application servers are preconfigued as JMX Metrics that can be viewed in the JMX Metrics Browser. In this screen capture of the JMX Metrics Browser, under Web Container Runtime,...
Question Our application uses JTurbo JDBC driver to connect to a MS SQL Database. We can not see the JDBC calls to the MS SQL Server database backend. How can we fix this? Answer Refer to this article Using Node Properties to Detect JDBC Backends ...
This article represents the latest collected set of wisdom from AppDynamics field engineers. For information on how to configure the Java Agent with TIBCO, see Configure the Java Agent for TIBCO BusinessWorks Required Agent version BusinessWorks...
For JBoss EAP AppDynamics supports the underlying JVM and framework versions. Our product documentation has specific installation instructions for JBoss (open-source versions) but those instructions do not necessarily work for JBoss EAP. JBoss EAP ...
Confirming Backend Discovery and Instrumentation This article describes the backend discovery life cycle. Understanding these details can help you debug instrumentation issues of backends that are not automatically discovered. The phases referred to ...
AppDynamics automatically discovers various entities that make up your web applications, such as app servers, databases, and remote services. Other activity in your application, such as errors, exceptions, async activity, and business transactions ar...
Contents: Who would use this workflow?How to know which POJO to use?ImplementationLimitations Who would use this workflow? Note: This workflow has largely been replaced by the Live Mode feature. If you don't see expected activity in your applica...
After installing AppDynamics Database Agent, if you see error messages similar to the following code the issue may be with OS monitoring for your Database collector. 15:33:48,718 ERROR [Agent-Scheduler-1] AServerCollector:199 - Error collecting hardw...
Users who are troubleshooting scenarios where the AppDynamics *Standalone Machine Agent is not reporting metrics as expected will find causes and solutions here. The following solutions apply to versions 4.4 and higher. Contents: Installation issu...
Question I am using the Object Instance Tracking feature. When I try to Drill Down on a specific class, I get the following message when I go to the Allocation Tracking tab: "Allocation Tracking is not enabled for System / core Java classes." How...
Updated on 6/11/2018 Problem: App Agent log is empty, or nothing is reported to the Controller. Common Solutions: If your agent is behind a network firewall or load balancer, open ports to enable communication between the agent and the Control...
Content revised 8/1/18 You may want to configure Error Detection to ignore known exceptions. For example, you may see a recurring exception thrown from a framework you are using. If the exception is well-known and insignificant, you might want to el...
Sometimes errors may appear in an appserver log, but not in AppDynamics. Or you may run your own specific test suites and see that known errors are not being detected by AppDynamics. Here are some things to check. 1. Confirm Logging Framework is Su...
This article covers some reasons that a configured MBean metric might not show up in the Metric Browser. Confirm a Persistent Metric is Configured Not all MBeans are configured as persistent metrics in AppDynamics. First confirm that the informatio...
AppDynamics provides out-of-the-box configuration of JMX/PMI metrics based on the MBeans exposed by many commonly used app servers. The MBean Browser is accessed on the Node dashboard from the JMX tab. The browser is used to look at MBean metric v...
Updated on 9/5/18 Question My application uses a MariaDB client. It uses c3pO JDBC drivers with JNDI-bindable DataSources, including DataSources that implement Connection and Statement Pooling, as described by the jdbc3 spec and jdbc2 std extension. ...
Question My application uses a Greenplum database. The calls to the database are JDBC, but we are not discovering the database out of the box. How can I fix this? Answer Refer to Using Node Properties to Detect JDBC Backends for more details on usi...
Symptom JDBC calls to a Vertica database are not being seen by AppDynamics. What can be done? Solution Use the following node propeties and values: jdbc-prepared-statements = com.vertica.jdbc.SPreparedStatement,com.vertica.jdbc.VerticaPreparedSt...
Question I am using a TeraData database and it's not showing up as a Database Server in my application. How can I fix this? Answer Refer to this article Using Node Properties to Detect JDBC Backends and use the following JDBC node properties and va...
Detect JDBC Databases Sometimes you can use one or more of the JDBC Agent node properties to get visibility for JDBC servers that are not discovered automatically by AppDynamics App Agents. If there's a JDBC driver for the database we can often...
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form