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.
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...
This dashboard delves deep into the performance of individual nodes present in the system. To use this dashboard layout, import the attached Ops-Dashboard.xml file and follow the instructions to rebind similar metrics in another application. L...
This Ops Management dashboard exposes the overall application performance by correlating end user experience with the application backend performance. This allows for deep visibility into all aspects of your application from a single dashboard. ...
This sample dashboard is targeted primarily for Development teams, enabling them to track the performance status of their code broken down by Business Transactions. To use this dashboard layout, import the attached Dev-Dashboard.xml file and ...
This QA dashboard delves deep into the overall system performance from a business transaction perspective. It correlates performance aspects of each business transaction with its respective hardware usage along with health metrics and error load pres...
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form