Discussion Feed

Question   How does the EUM licensing model work when using a multi-tenant Controller?   Answer   EUM for a multi-tenant Controlleris slightly different than the license for a single Controller. The EUM account mentioned in the license file can only be used for one of the multi-tenant accounts. If there is a need to split the EUM usage across multiple Controller accounts, then separate licenses with different EUM account names will be provided and the total units will be divided amongst those licenses.   The customer must provide all of these licenses to the EUM server, but only enter the production license in the Controller home directory.   Note: The license.lic file applies to the entire Controller, not for any given account when in multi-tenant mode. This means, for example, a user with 100 Java units in the license.lic file can not exceed 100 Java APM units across all accounts,  and any accounts created in the Admin section of the Controller UI would pull values from that license file. ... View more

Some users may see unnecessary AJAX calls being made from a browser page, which prevents the flow of EUM data.   This issue is due to the default limit of reporting 50 AJAX calls per page, and after reaching said limit, any additional calls such as Adrum beacon POST requests are dropped.   More information: Limit the Number of AJAX Requests   To resolve this issue, there are two options.   Option 1:  Limit the XHR (Ajax) monitoring to only specified calls.  See Limit XHR (Ajax) Monitoring to Specified Calls   Option 2: Increase the limit from the default of 50 to a higher value. See Limit the Number of Ajax Requests ... View more

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(EUMProcessorHelper.java:360)  at com.appdynamics.eum.processor.utils.EUMProcessorHelper.initializeAccountCredentialStore(EUMProcessorHelper.java:326)  at com.appdynamics.eum.processor.EUMProcessorServerApplication.run(EUMProcessorServerApplication.java:161)  at com.appdynamics.eum.processor.EUMProcessorServerApplication.run(EUMProcessorServerApplication.java:100)  at io.dropwizard.cli.EnvironmentCommand.run(EnvironmentCommand.java:40)  at io.dropwizard.cli.ConfiguredCommand.run(ConfiguredCommand.java:77)  at io.dropwizard.cli.Cli.run(Cli.java:70)  at io.dropwizard.Application.run(Application.java:80)  at com.appdynamics.eumcloud.EUMProcessorServer.main(EUMProcessorServer.java:40)   Diagnosis Take the output of the accounts and  account_credential  tables within the  eum_db schema of the Controller database.   Example: ./controller.sh login-db use eum_db; select * from accounts; select * from account_credential;   Note: The account name within the accounts table must match that of the account_credential table. The number of records must be the same.   Solution If the accounts table is purged before provisioning the license, there can be a mismatch in the number of records within the two tables.   To resolve this issue, delete the mismatching  account_name row from the account_credential table. Then restart the EUM Processor.   Example:  delete from account_credential where account_name = 'mismatched_account_name'; ... View more

Question Can an application use an alternate URL to access the EUM Collector?   This is relevant to:  EUM customers who wish to separate the EUM Collector to multiple competing brands. EUM customers with both internal and external applications that need different URLs to access the EUM Collector. Answer Yes, using the custom configuration section in the EUM Server configuration.    In the Controller, navigate to the EUM configuration page. Click on the "Configure and download a JavaScript Agent". Expand the "Advanced" section. In the  custom configuration  text fields, change the values of  config.beaconUrlHttp  and  config.beaconUrlHttps   to the new URL. Click "Save Config and Generate HTML Snippet". Copy the HTML snippet or download the JavaScript file.  Add the generated snippet to all HTML pages that should be monitored by the JavaScript Agent. ... View more

Question Why am I not able to assign priority using a numeric property  to the custom naming rules inside EUM Server configuration in version 4.3? Answer This is expected behavior. As of version  4.3, users can drag and drop to change the priority of custom naming rules.   Rules are evaluated from top to bottom.     Note: Prior to version 4.3,  a numeric property decided the order or evaluation.   Related Links: Configure Page Identification and Naming ... View more

Question: Why are the Agent IDs used for Cross Domain Session Correlation different for each enabled application?   Answer: This is not the expected behavior, as the Agent IDs should be the same for each application using Cross Domain Session Correlation. This issue can occur when the adrum-xd.html file is hosted on different domains for each application. For Cross Domain Session Correlation to work, all pages on the multiple domains have to access the same copy of adrum-xd.html that is hosted on a single domain.       Question: Is there any way to confirm whether the JavaScript Agent is sending a cross-domain-capable beacon?   Answer:  To check whether the JavaScript Agent is sending a cross-domain-capable beacon, look at the beacon “ai” field, which standards for “agent ID.” If agent ID starts with “XD_”, cross domain works on the JavaScript agent.       Question: How often is the file adrum-xd.html (which is used to enable Cross Domain Session Correlation) loaded?   Answer: The adrum-xd.html file is loaded into a hidden iframe once every 2 weeks.        Question: Is it possible to see  Cross Domain Sessions across multiple AppDynamics applications?   Answer: No, it's not possible. In our Cross Domain Session Correlation, we only support sessions that are across domains but within the same AppDynamics application.       More info on Cross Domain Session Correlation: Configure the JavaScript Agent.     ... View more

Question Why are there unknown values for Mobile Carriers and Connection Types in Mobile RUM dashboard?   Answer The AppDynamics Android Agent references ConnectivityManager and TelephonyManager for information on the device's connection and carrier, respectively. Sometimes these frameworks fail to return information, for a variety of reasons, which are beyond the control of AppDynamics.   Example: Some devices from specific vendors disallow access to the Connectivity Manager for security reasons, and appear in device logs as "Access to ConnectivityManager is denied". There are Android devices and versions where the Connectivity Manager is not available or does not work in certain hardware configurations. There are several documented cases of this, the specific Android error is "missing IConnectivityManager", and appears in device logs as "Error determining connection type." Frequently, devices without SIM cards, like tablets, will fail to return carrier info from Telephony Manager. In the dev logs, they appear as "Error determining carrier name". Note: A value of  "offline" in the dashboard means that connectivity was limited at the time the request was sent     Related Links: More on Mobile RUM Mobile RUM metrics Video - Start monitoring with the Android Agent ... View more