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.
In this article... Why are no queries found in the 'DB Queries' tab under the BT Dashboard? In what order are queries in the ‘Transaction Snapshot Viewer’ fetched? Transaction Snapshot Viewer query order with Oracle databases Transaction Snapshot ...
What you need to configure Oracle Wallet for database monitoring collectors This article provides detailed instructions for configuring Oracle Wallet for database monitoring collectors. To learn more about Oracle collectors, connection details,...
Table of Contents Overview Prerequisite How do I delete a Collector? Overview The Database Collector is the process that runs within a Database Agent to collect performance metrics about your database instances and database servers. To enable the...
Errors In some cases, database corruption can result in java errors, deadlocks, sporadic Controller shutdowns, and Controller inaccessibility. Below is a list of errors that may indicate database corruption. If you encounter one of them or other iss...
Question Is AppDynamics able to monitor MemSQL DB? Answer Yes. MemSQL is wire-compatible with MySQL. MemSQL uses the MySQL jdbc libraries for connectivity. AppDynamics database agent can monitor the MemSQL DB if configured like this: 1. Ins...
The database agent can add between 0% to 2% additional overhead on CPU usage. In addition, a database's idle time may be reported as overhead; for example, if a database is idle for 99% of the time, it may look like the database has an overhead of c...
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 ...
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: SQLCOD...
How does a user utilize iNet Merlia driver based (Version 8.08) JDBC database calls? This database driver is not supported out of the box by AppDynamics, but users can configure the following Agent node properties in order to utilize this tool. ...
Problem: The user is unable to view queries and query wait states information in the Controller UI, even though the information has been captured and sent to the Controller by the Database Agent. Database logs show the following error messages: E...
Beginning with AppDynamics version 4.3.x, a user can enable and disable Collectors that they have created. Newly created Collectors are enabled by default. Users who want to discontinue monitoring a database without deleting the Collector prof...
In order to view the SQL statements in transaction snapshots related to Postgres database, apply the following node properties. See: How to Add a Registered Node Property Property: jdbc-connectionsValue: org.postgresql.jdbc.PgConnectionProperty...
Problem: Scenario 1: The Agent stops collecting or sending metrics to the Controller intermittently, but the Agent is shown as "running." All, or nearly all collectors are temporarily disabled via the UI. Agent logs include error messages sim...
A user unable to fetch wait-state information for the database may see the following error in the Controller UI: In the Controller's server.log file, the following error message indicates an incorrectly set configuration property: |SEVERE...
Users utilizing version 4.3.x Database Agents may experience an issue where the database Collector does not start, and no longer reports metrics to the Controller. The Database Agent logs will show one of the following errors for the problematic...
What do I need to know to set up a Database Agent with High Availability? In this article Starting principles when using High Availability (HA)Agent location and naming for HACrucial considerations for configurationAdditional Resources Starting p...
If an AppDynamics Agent fails to instrument JDBC driver for Vertica database, Vertica backend calls will not be visible. To diagnose this issue, use the following API calls to verify if Agent is able to apply the interceptors. com.vertica.jdb...
For users whose MySQL database collector will not start, first check the configuration data including username, password, host, and port. Look in the Agent logs for an error similar to the following: "Error collecting data for database 'xxx DB...
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. Restrict...
Symptoms The EUM Processor does not start and the following error message is listed in the eum-processor.log file. java.lang.NullPointerException at com.appdynamics.eum.processor.utils.EUMProcessorHelper.controllerSupportNewEventServiceKey(EUMProc...
Now, these users will only need to sign in to AppDynamics once. As they navigate from one to another of their authorized AppDynamics products and services, they will not be asked for their password again.
NOTE | This change does not affect current Controller local, SAML, and LDAP users, who can continue to sign in as they always have, without disrupting their access.
Though this feature is currently only available for users added since v21.11, the ability to convert an existing (pre-v21.11) user account to the new SSO-enabled AppDynamics managed user identity is planned for later in 2022. Be on the lookout for an announcement describing this conversion in the future.
AppDynamics IDP users can use the following steps to view and navigate to their AppDynamics products and services:
|
The password field appears once you enter the username and click next. It may either appear on the same screen, or once you are redirected to your “global” sign-in page.
You need to enter your username twice when first signing in due to our use of a global identity provider.
TIPS | Use the “Remember me” functions to further streamline all your future logins.
Alternatively, sign in to your personal profile page first. It will show you everything you have access to and provide direct access links.
We are working on a migration to AppD IDP user capability that will upgrade your existing Controller account to AppD IDP. It is on the roadmap for later this year.
You can expect successful authentications when an AppD IDP account is used for a service account AppD IDP authentication on a Controller. The service account can be authenticated without the SSO flow.
That said, we recommend that customers move to our OAUTH-based API clients for this process , wherever possible, to improve security. See the documentation for this feature here.
AppD IDP stands for “AppDynamics Identity Provider”. Until now, each Controller has served as its own identity provider. From this point forward, we are moving that function to the AppD IDP, a global AppDynamics Identity Provider.
If you have chosen SAML or LDAP as your authentication provider in the Controller tenant authentication provider settings tab, then you are not using the new AppD IDP for user identity management, but instead are using your own provider. If your Controller tenant has “AppDynamics” selected in the Controller tenant authentication provider tab, then users created since v21.11 are using the AppD IDP for user identity management.
If your account was created between now and v21.11, and your email address is your username, then you are an AppDynamics Identity Provider user.
You can confirm this by logging into your personal profile at https://accounts.appdynamics.com/personal-profile. If the Assigned Controller Tenants sections lists the Controllers you use, you are an AppDynamics Identity Provider user.
Legacy local AppDynamics user accounts are those created before v.21.11 that do not use email as their username.
NOTE | As with Controller based SAML and LDAP users, current pre-v21.11 legacy local users can continue to sign in as they always have, without a disruption to their access.
Yes! This is like any other AppDIDP-managed user except that when they sign in, they will be redirected to the customer IDP. Just add the user using their email address to the Controller account.
The user must be added from the Controller users page, using their email address. If a user’s email exists in the AppD IDP, that account will be used for SSO features.
NOTE | Users cannot be given access to a Controller tenant from the Accounts Management Portal at this time.
You may find the following AppDynamics Documentation resources useful:
Also related to this topic are the following Knowledge Base articles:
Bill.Howard
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form