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.
The ISP (Internet Service Provider) or Carrier information can be captured as part of requests but ISP (Carrier) monitoring in EUM in on-premise installations is turned off by default. The ISP feature is behind a feature flag that you will need to e...
Issue What should I do if my EUM Server is unable to start because of below error? Error Starting EUM Processor Server | com.google.inject.CreationException: Unable to create injector, see the following errors:Error in custom provider, com.sin...
If you are using one of our SAAS EUM Clouds in North America, Europe, and APAC region, below are the instrumentation customizations required to set the collector and config endpoint. North AmericaEuropeAPAC North America Android Instrumentation.sta...
Similar to the steps outlined in the Set the Security Protocol document for the Controller, you can also set the security protocol or update the existing security protocol used by the EUM Server. The document link above refers to changing these sett...
Assuming you are already successfully auto-injecting the EUM JavaScript Agent, the following steps can be used to turn on SPA2 monitoring. 1. From the User Experience tab, double-click on the EUM application you'd like to enable SPA2 monitoring f...
How do I change Page and Ajax limits for an EUM application in an on-premises Controller? These limits can be altered, but keep in mind that more registered pages and Ajax will result in more metrics. This is a performance overhead for both EUM ...
To instrument your application for EUM, you will need to configure your JavaScript Agent and insert it into the page that is returned to the end user. This process is known as injection. It is important to complete the injection process completely...
If your Mobile Agent version is 4.5, 4.4 & 4.3, you need to use the loggingLevel method to enable and set the different logging levels in your instrumentation code. For instance: // appKey should be assigned your EUM app key ADEumAgentConfigur...
Logging in to the EUM database manually 1. From $EUM_HOME/mysql/bin folder run the below command: ./mysql -u root -p eum_db --protocol=TCP --protocol=TCP -P [EUM-MySQL-Port] 2. When you execute this command, it will ask you for your EUM user passw...
To enable EUM Client side debug logs dynamically, you can use the Glassfish admin console or use the asamin utility. 1. Access the Glassfish admin console following the steps outlined here: AccesstheGlassfishAdminConsole 2. Once logged in, navig...
If you do not see AJAX requests being reported, below are a few things you should check: The AJAX page name limit is getting hitThe max AJAX limit is getting hitThe page is navigating to another page before the Adrum Beacon postedThe AJAX causes a...
Problem: EUM browser data is not correlating to the backend application, even when the correlation cookie is coming as a part of the response from the application server. Analysis: We see that the cookie information is present in the response and ...
If the End User Monitoring (EUM) data/license does not appear in the Controller UI and the logs of the Controller (server.log) contains the message below, this is normally caused by an EUM license key mismatch between the property_eum-license-key va...
To work around this issue, follow the steps outlined below. Essentially, you will be changing the EUM key within the events-service-api-store.properties file temporarily so that EUM can fail authorization again. Once the EUM Server fails, you will c...
Question: Why can’t I enable EUM? Answer: There are a few reasons why you may not be able to enable EUM: 1. “Configure EUM” permissions If you don’t have the “Configure EUM” permission, you won’t be able to configure Browser and Mobile RUM. Yo...
The data and the discrepancy is due to the fact that data sources for the Mobile App Crashes Metric (EUM) and the Crash Events Count (Analytics) are different. The data for the Mobile App Crashes Metric is from EUM metrics stored in the Controller D...
Question How often does the data purge activity occur for EUM resource snapshots when the retention policy configuration is set? Answer For the on-premise EUM Processor, the expiration check happens once every hour. The data purge that occurs ...
Question Is it possible to set up multiple Synthetic Private Agents on the same server? Answer As per the current model, if you install multiple Synthetic Private Agents tagged under same ID on same machine, it won't work properly since we nee...
Question Why do I need to run the eum-schema update after importing the MySQL eum_db dump from the Controller MySQL to the EUM MySQL database? Answer Starting 4.4, EUM has its own MySQL database in production mode deployment. If we are upgrad...
I’m upgrading EUM from a version lower than 4.4. Why does the upgrade fail during “schema update”? Problem EUM upgrade from a version lower than 4.4 fails in the "schema update" step with the below error: Unexpected error running Liquibase: Error ...
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