Consider the following scenarios: You have an on-premises multi-tenant controller and a EUM server (on-prem or SaaS). You have one EUM license with 10 units. You want to split an assigned number of units to a new tenant.  To split EUM units and provision the EUM licenses, ask the Sales team for a EUM license with <x> number of units. They will usually give you two licenses. First license: The previous license with the old EUM account name and access key, but with updated units = 10 - x Second License:   Contains the new EUM account name and access key, but with units = x Be sure to leave the EUM account name or access key of the previous license unchanged. Such changes may cause a change in the EUM app-key in the application associated with the previous EUM account. Once you get both licenses, provision them on your EUM server, as follows. How do I provision licenses on a EUM server? Licenses need to be provisions on SaaS. On-premises customers, skip to the  How do I provision EUM licenses on a multi-tenant Controller UI section below. Got o the EUM server (remotely hosted).  Provision both licenses one by one on the EUM server using the following command: $> cd EUM/eum-processor $> ./bin/provision-license.sh <PATH TO LICENSE> See the instructions for provisioning EUM licenses here. Then, once the license is provisioned on the EUM server, proceed with the following steps: How do I provision EUM licenses for accounts on a multi-tenant Controller UI? Navigate to the Administration page of your on-premise Controller:  http(s)://<hostname>:<port>/controller/admin.jsp Click Accounts. Select the account name that you want to provision EUM for and click Edit. Scroll down to the End User Monitoring (EUM) panel. From the Browser Real User Monitoring section: Copy the EUM license key from your license file into the EUM License Key field. From the License Type drop-down, select a license type (EUM Lite or EUM Pro). Enter your allotted Browser RUM units into the Browser RUM Units Licensed field. Set overages from the Allow Overages drop-down. Complete the steps above for the Mobile Real User Monitoring section. Click Save. Complete the 7 steps above for both (or all) tenant accounts. ... View more

This article outlines how to troubleshoot the Java Agent when Transaction Analytics is not receiving any data. Table of Contents How do I start troubleshooting missing transaction data? How do I test for communication issues between agents? How do I start troubleshooting missing transaction analytics data? If you aren't seeing transaction analytics data under Analytics, start by troubleshooting from the origin of the events, following the steps below: Check if Analytics is enabled for the Business Transactions (BT) of the application: Go to Analytics > Configuration > Transaction Analytics > Configure Analytics for Application. Make sure the Enable Analytics Data Collection for <Application> checkbox is selected and that the BT is present in the list on the left-hand side under Configure Which Transactions Report Analytics Data. Open the Application Agent log to look for the  analytics-dynamics-service-enabled  property, and make sure it's set to true. Then, look for log entries similar to the ones shown below. This ensures the Dynamic Services for Analytics Data Collection have started and that the Java Agent is now sending the analytics-enabled BT events to the Analytics Agent. [AD Thread Pool-Global0] 17 Oct 2018 23:34:46,278 INFO AnalyticsDynamicServiceConfigListener - Analytics Dynamic Service configuration listener received new properties from the Controller, starting refresh operation. [AD Thread Pool-Global0] 17 Oct 2018 23:34:46,278 INFO AnalyticsDynamicServiceConfigListener - ********** Started applying Analytics Dynamic Service properties from Controller ************* [AD Thread Pool-Global0] 17 Oct 2018 23:34:46,279 INFO Analytics - Analytics Dynamic Service config [ENABLED] = true [AD Thread Pool-Global0] 17 Oct 2018 23:34:46,302 INFO WriterMaster - Initialized with writer parameters [65536 (appdynamics.analytics.bufferPool.maxCount), 65536 (appdynamics.analytics.tlsCharBuffer.maxLength), 128 (appdynamics.analytics.unflushedQueue.maxLength), 2 (appdynamics.analytics.numOfSinkWriterTasks), 102400 (appdynamics.analytics.message.maxSizeBytes), 10000] and sink parameters ['http://localhost:9090/v2/sinks/bt' (appdynamics.analytics.agent.url), 30000 (appdynamics.analytics.agent.connection.timeoutMillis), 1200 (appdynamics.analytics.agent.send.attempt.max), 15000 (appdynamics.analytics.agent.send.attempt.pauseMillis), 16 (appdynamics.analytics.agent.send.batch.items.max), 60000 (appdynamics.analytics.throughputCollectionIntervalMillis)] [AD Thread Pool-Global0] 17 Oct 2018 23:34:46,304 INFO WriterMaster - Starting [appdynamics-analytics-writer0] 17 Oct 2018 23:34:46,319 INFO SinkWriterTask - Starting [appdynamics-analytics-writer1] 17 Oct 2018 23:34:46,320 INFO SinkWriterTask - Starting [AD Thread Pool-Global0] 17 Oct 2018 23:34:46,321 INFO WriterMaster - Started [AD Thread Pool-Global0] 17 Oct 2018 23:34:46,324 INFO AnalyticsCollectorFactory - Analytics configured with new delegate: [com.singularity.ee.service.analytics.Analytics] [AD Thread Pool-Global0] 17 Oct 2018 23:34:46,324 INFO Analytics - Started [Analytics] collector [AD Thread Pool-Global0] 17 Oct 2018 23:34:46,324 INFO AnalyticsDynamicServiceConfigListener - --------- Finished applying Analytics Dynamic Service properties from Controller ------------ Check to see if the   analytics-dynamics-service-enabled  property is set to true. If it is true, but the later logs never confirm WriterMaster - Started or Analytics - Started [Analytics] collector, it's possible that the  analytics-dynamics-service.jar file under javaagent/ver4.x.x.xxxxx/external-service/analytics is not present.  In this case, please download a valid Java Agent installer package, which has  analytics-dynamics-service.jar under  javaagent/ver4.x.x.xxxxx/external-service/analytics . Then instrument the application again.  Check if the  analytics-dynamics-service.jar  file is present under the  javaagent/ver4.x.x.xxxxx/external-service/analytic directory . If present, open  javaagent/ver4.x.x.xxxxx/conf/app-agent-config.xml and look for the following:  <agent-service name="DynamicServiceManager" implementation-class-name="com.singularity.ee.agent.appagent.kernel.DynamicServiceManager" enabled="true"> <implementation-class-name> com.singularity.ee.agent.appagent.kernel.DynamicServiceManager </implementation-class-name> <configuration-properties> <property name="external-service-directory" value="external-services"/> </configuration-properties> </agent-service>  If it's not present, please add it.    If the above config is present, open the latest  javaagent /ver4.x.x.xxxxx/logs/dynamic-service*.log and look for  any error in loading Analytics Dynamics Services. Check for an an error similar to the following: [AD Thread Pool-Global0] 18 Oct 2018 13:02:56,585 INFO com.singularity.dynamicservice.DynamicServiceManager - Service class name com.singularity.ee.service.analytics.Analytics [AD Thread Pool-Global0] 18 Oct 2018 13:02:56,590 ERROR com.singularity.dynamicservice.DynamicServiceManager - Error occurred while polling for new services java.security.AccessControlException: access denied ("java.lang.RuntimePermission" "getClassLoader") at java.security.AccessControlContext.checkPermission(AccessControlContext.java:472) ~[?:1.8.0_102] at java.security.AccessController.checkPermission(AccessController.java:884) ~[?:1.8.0_102] at java.lang.SecurityManager.checkPermission(SecurityManager.java:549) ~[?:1.8.0_102] at java.lang.ClassLoader.checkClassLoaderPermission(ClassLoader.java:1528) ~[?:1.8.0_102] at java.lang.ClassLoader.getParent(ClassLoader.java:1374) ~[?:1.8.0_102] at com.singularity.ee.agent.appagent.kernel.classloader.AgentClassLoader.a(AgentClassLoader.java:432) ~[appagent-boot.jar:?] at com.singularity.ee.agent.appagent.kernel.classloader.AgentClassLoader.c(AgentClassLoader.java:415) ~[appagent-boot.jar:?] at com.singularity.ee.agent.appagent.kernel.classloader.d.b(d.java:69) ~[appagent-boot.jar:?] at com.singularity.ee.agent.appagent.kernel.classloader.AgentClassLoader.loadClass(AgentClassLoader.java:305) ~[appagent-boot.jar:?] at java.lang.ClassLoader.loadClass(ClassLoader.java:411) ~[?:1.8.0_102] at com.singularity.ee.util.c.loadClass(c.java:320) ~[appagent.jar:Server Agent #4.5.0.23604 v4.5.0 GA compatible with 4.4.1.0 r88b53d319a45abc58963be9d2d0824499a2c23dd release/4.5.0-release] at com.singularity.ee.agent.appagent.kernel.c.loadClass(c.java:84) ~[appagent.jar:Server Agent #4.5.0.23604 v4.5.0 GA compatible with 4.4.1.0 r88b53d319a45abc58963be9d2d0824499a2c23dd release/4.5.0-release] at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:1.8.0_102] at com.singularity.ee.service.analytics.Analytics.<init>(Analytics.java:70) ~[?:?] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:1.8.0_102] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) ~[?:1.8.0_102] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:1.8.0_102] at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[?:1.8.0_102] at java.lang.Class.newInstance(Class.java:442) ~[?:1.8.0_102] at com.singularity.ee.agent.util.reflect.l.f(l.java:1693) ~[appagent-boot.jar:Server Agent #4.5.0.23604 v4.5.0 GA compatible with 4.4.1.0 r88b53d319a45abc58963be9d2d0824499a2c23dd release/4.5.0-release] at com.singularity.ee.agent.appagent.kernel.DynamicServiceManager.pollDirectoryForNewServices(DynamicServiceManager.java:476) ~[appagent.jar:Server Agent #4.5.0.23604 v4.5.0 GA compatible with 4.4.1.0 r88b53d319a45abc58963be9d2d0824499a2c23dd release/4.5.0-release] at com.singularity.ee.agent.appagent.kernel.DynamicServiceManager.pollForNewServices(DynamicServiceManager.java:329) ~[appagent.jar:Server Agent #4.5.0.23604 v4.5.0 GA compatible with 4.4.1.0 r88b53d319a45abc58963be9d2d0824499a2c23dd release/4.5.0-release] at com.singularity.ee.agent.appagent.kernel.DynamicServiceManager.run(DynamicServiceManager.java:272) ~[appagent.jar:Server Agent #4.5.0.23604 v4.5.0 GA compatible with 4.4.1.0 r88b53d319a45abc58963be9d2d0824499a2c23dd release/4.5.0-release] at com.singularity.ee.util.javaspecific.scheduler.n.run(n.java:122) ~[appagent.jar:Server Agent #4.5.0.23604 v4.5.0 GA compatible with 4.4.1.0 r88b53d319a45abc58963be9d2d0824499a2c23dd release/4.5.0-release] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_102] at com.singularity.ee.util.javaspecific.scheduler.z.e(z.java:335) ~[appagent.jar:Server Agent #4.5.0.23604 v4.5.0 GA compatible with 4.4.1.0 r88b53d319a45abc58963be9d2d0824499a2c23dd release/4.5.0-release] at com.singularity.ee.util.javaspecific.scheduler.a.b(a.java:152) ~[appagent.jar:Server Agent #4.5.0.23604 v4.5.0 GA compatible with 4.4.1.0 r88b53d319a45abc58963be9d2d0824499a2c23dd release/4.5.0-release] at com.singularity.ee.util.javaspecific.scheduler.b.a(b.java:119) ~[appagent.jar:Server Agent #4.5.0.23604 v4.5.0 GA compatible with 4.4.1.0 r88b53d319a45abc58963be9d2d0824499a2c23dd release/4.5.0-release] at com.singularity.ee.util.javaspecific.scheduler.b.b(b.java:206) ~[appagent.jar:Server Agent #4.5.0.23604 v4.5.0 GA compatible with 4.4.1.0 r88b53d319a45abc58963be9d2d0824499a2c23dd release/4.5.0-release] at com.singularity.ee.util.javaspecific.scheduler.b.run(b.java:236) ~[appagent.jar:Server Agent #4.5.0.23604 v4.5.0 GA compatible with 4.4.1.0 r88b53d319a45abc58963be9d2d0824499a2c23dd release/4.5.0-release] at com.singularity.ee.util.javaspecific.scheduler.i.a(i.java:694) ~[appagent.jar:Server Agent #4.5.0.23604 v4.5.0 GA compatible with 4.4.1.0 r88b53d319a45abc58963be9d2d0824499a2c23dd release/4.5.0-release] at com.singularity.ee.util.javaspecific.scheduler.i.run(i.java:726) ~[appagent.jar:Server Agent #4.5.0.23604 v4.5.0 GA compatible with 4.4.1.0 r88b53d319a45abc58963be9d2d0824499a2c23dd release/4.5.0-release] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_102]   If there is such an error, you need to provide the permission in the java.policy file under <JAVA_HOME>/lib/security/java.policy  as follows: grant codeBase "file:/opt/appdynamics/-" { permission java.security.AllPermission; permission java.lang.management.ManagementPermission "monitor"; permission java.io.FilePermission "read"; }; This should fix the Analytics Dynamics Service startup issue and start reporting events to the Analytics Agent, which is responsible for forwarding these events further to the Events Service. In the Java agent log, are we seeing the following WARN message? It tells us that your Analytics data is being dropped because you have reached the limit. [pool-63794-thread-3] 21 Jul 2019 19:56:07,004 ERROR AnalyticsCollectorFactory - Bounds exceeded creating analytics collector. Disabling Analytics Collection.  The Analytics collector is attached to each thread that is spawned so that it can detect and publish the analytics information. When the number of threads goes beyond 2200, it shuts off the Analytics component from the Agent. To get past this error, please add the following to the <agent-services> section of the  app-agent-config.xml  file for the Agent: <agent-service name="Analytics" enabled="true" minimum-java-version="1.5"> <configuration-properties> <property name="analytics-collectors-limit" value="5000,WARN_IF_BOUND_EXCEEDED"/> </configuration-properties> </agent-service> After adding this, restart the app agent once. This will let the collection grow without bound, but will log every time something is added beyond the bound. No data will be dropped. How do I test for communication issues between agents? Once the above issues are fixed, you can expect events to be forwarded to the Analytics Agent. However, if you still don't see data in Analytics, you should look for communication issues between the Analytics Agent and the Java Agent.  Check if the Java Agent is configured to send the events to the correct Analytics Agent endpoint.  By default, the Java Agent sends events to the Analytics Agent running at http://localhost:9090 . If this is not the case, you have to explicitly set the JVM parameter to talk to the remote Analytics Agent. This is discussed in detail in the Installing Agent-Side Components document. If for some reason (e.g., maintenance or communication configuration issues) the Java Agent is not able to talk to Analytics Agent for a very long period of time, the Java Agent will queue the events on its end, ready for the Analytics Agent communication to be back up. However, the communication is not available before the buffer's memory is exceeded, you will see a WARNING in the Java Agent log that says "Internal buffers appear to be full."  After multiple failed attempts, the Java Agent will disable the Analytics Service within itself and stop sending data to the Analytics Agent. To resume sending data, go to Analytics > Configuration > Transaction Analytics > Configure Analytics for Application and disable and re-enable the Enable Analytics Data Collection for <Application> checkbox. If this does not work, try a JVM restart to resume the service.  ... View more

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 explicitly enable.  Set this following property in eum.properties under EUM_HOME/eum-processor/bin directory. beaconReader.geoResolveCarrier=true Next, restart the EUM server. Unix: cd <EUM_HOME>/eum-processor ./bin/eum.sh stop ./bin/eum.sh start & Windows: Use the Windows service for EUM to restart. ... View more

Purpose For demo purposes when the customer wants to install everything (i.e. Enterprise Console, Controller, Events service and EUM ) on the same node, the steps below can be used to install the Events Service on the same node as Enterprise Console (EC). Steps to install 1. Install Enterprise Console following the instructions outlined here. 2. Start the Enterprise Console. ./bin/platform-admin.sh start-platform-admin Starting Enterprise Console Database .. ***** Enterprise Console Database started ***** Starting Enterprise Console application Waiting for the Enterprise Console application to start......... ***** Enterprise Console application started on port 9191 *****   3. Log in to the Enterprise Console. ./bin/platform-admin.sh login --user-name admin --password secret Login successful. 4. Create a platform. ./bin/platform-admin.sh create-platform --name sample_platform --installation-dir /home/ubuntu/appdynamics/sample_platform Created platform: sample_platform 1. The installation path should be writable for all hosts added to this platform. 2. The path should be an empty folder, or will be created if it doesn't exist. 3. Use a path which does not have any existing AppDynamics components installed under it. If you will be issuing many commands in a row for the same platform, you can avoid repeatedly specifying the --platform-name flag by setting the environment variable APPD_CURRENT_PLATFORM to the name of a platform. If you specify the --platform-name flag to any command, this will override the value of the environment variable. 5. Add a host, but use default platformadmin host for this. Adding credentials isn't required! ./bin/platform-admin.sh add-hosts --hosts platformadminAdding new hosts to a platform and making configuration updates. ( 1/ 12) Check new hostnames: SUCCESS ( 2/ 12) Validate SFTP configuration: Establish connection to the remote host ( 2/ 12) Validate SFTP configuration: Verify connection ( 2/ 12) Validate SFTP configuration: Examine sshd config file ( 2/ 12) Validate SFTP configuration: Verify subsystem is configured ( 2/ 12) Validate SFTP configuration: SUCCESS ( 3/ 12) Add hosts to Enterprise Console: SUCCESS ( 4/ 12) Initialize Orcha Cluster and save Cluster configuration: SUCCESS ( 5/ 12) Add hosts to Orcha Cluster: SUCCESS ( 6/ 12) Unpack JRE artifact: Unarchive binary in staging ( 6/ 12) Unpack JRE artifact: SUCCESS ( 7/ 12) Unpack orcha-modules artifact: Unarchive binary in staging ( 7/ 12) Unpack orcha-modules artifact: SUCCESS ( 8/ 12) Configure orcha logging: Set orcha modules root log location ( 8/ 12) Configure orcha logging: SUCCESS ( 9/ 12) Bootstrap hosts: Copy JRE to the remote host ( 9/ 12) Bootstrap hosts: Copying orcha modules to the remote host ( 9/ 12) Bootstrap hosts: Set permissions ( 9/ 12) Bootstrap hosts: Getting status of orcha modules on the remote host ( 9/ 12) Bootstrap hosts: Verifying the presence of remote Orcha ( 9/ 12) Bootstrap hosts: SUCCESS ( 10/ 12) Delete jre staging directory: Delete JRE staging area ( 10/ 12) Delete jre staging directory: SUCCESS ( 11/ 12) Delete orcha modules staging directory: Delete Orcha staging area ( 11/ 12) Delete orcha modules staging directory: SUCCESS ( 12/ 12) pa_publish_add_host_stage: SUCCESS Enterprise Console host expansion completed. Job duration: 14 seconds 6. Install the Events Service on the platformadmin host. ./bin/platform-admin.sh submit-job --service events-service --job install --args serviceActionHost=platformadmin profile=Dev ( 1/ 26) Clean up orphaned Events Service: SUCCESS ( 2/ 26) Register Events Service Lifecycle Listener before installing: SUCCESS ( 3/ 26) Validate and set parameters while installing ES: SUCCESS ( 4/ 26) Setup cluster configuration: SUCCESS ( 5/ 26) Initialize Events service cluster: SUCCESS ( 14/ 26) Set JRE Versions: SUCCESS ( 15/ 26) Check Events Service hostnames: SUCCESS ( 16/ 26) Verify hosts: Check total free memory ( 16/ 26) Verify hosts: Check total number of processors ( 16/ 26) Verify hosts: Verify if the required directories exists ( 16/ 26) Verify hosts: Get permissions of given directories ( 16/ 26) Verify hosts: Check if the given directories are writable ( 16/ 26) Verify hosts: Get stats of install/data directories ( 16/ 26) Verify hosts: Check if the destination installation directory has sufficient space ( 16/ 26) Verify hosts: Check if the destination data directory has sufficient space ( 16/ 26) Verify hosts: Stop the Events Service api store node ( 16/ 26) Verify hosts: Check if ports are available ( 16/ 26) Verify hosts: Fail if ports unavailable ( 16/ 26) Verify hosts: SUCCESS ( 17/ 26) Save Events Service Cluster Configuration: SUCCESS ( 18/ 26) Add new nodes to Events Service cluster: SUCCESS ( 19/ 26) Install Events Service: Getting status of Events Service artifact ( 19/ 26) Install Events Service: Verifying the presence of Events Service artifacts ( 19/ 26) Install Events Service: Copying Events Service binaries to target host ( 19/ 26) Install Events Service: Extracting Events Service binaries on remote host ( 19/ 26) Install Events Service: Moving extracted folder into Events Service processor ( 19/ 26) Install Events Service: Adding executable permissions to the Events Service startup script for NIX system ( 19/ 26) Install Events Service: Removing temporary directories ( 19/ 26) Install Events Service: Creating Events Service unarchived template directory ( 19/ 26) Install Events Service: Unarchive Events Service properties template ( 19/ 26) Install Events Service: Updating Events Service configuration ( 19/ 26) Install Events Service: Removing Events Service unarchived template directory ( 19/ 26) Install Events Service: Removing Events Service template in nodes ( 19/ 26) Install Events Service: Create JRE 8 link on windows ( 19/ 26) Install Events Service: Install service if on windows ( 19/ 26) Install Events Service: Starting the Events Service api store node ( 19/ 26) Install Events Service: SUCCESS ( 20/ 26) Load Events Service cluster configuration: SUCCESS ( 21/ 26) Load all ES cluster hosts into execution context.: SUCCESS ( 22/ 26) es_cluster_health_stage: SUCCESS ( 23/ 26) Clean up obsolete Events Service: SUCCESS ( 24/ 26) Register Events Service Recurring Cluster Health Job: SUCCESS ( 25/ 26) Register Events Service Recurring Node Health Job: SUCCESS ( 26/ 26) es_publish_install_stage: SUCCESS Job completed successfully. Job duration: 1 minutes 15 seconds Verify 1. Check the Events Service node. ./bin/platform-admin.sh list-nodes --service events-service Available nodes in the events-service service: api-store member on host platformadmin in state: "running" with roles: master 2. Verify the Events Service health. ./bin/platform-admin.sh show-events-service-health ( 1/ 3) Load Events Service cluster configuration: SUCCESS ( 2/ 3) Load all ES cluster hosts into execution context.: SUCCESS ( 3/ 3) es_cluster_health_stage: SUCCESS Health status: HEALTHY Job duration: 6 seconds ... View more

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 America Europe APAC North America Android Instrumentation.start(AgentConfiguration.builder() .withAppKey("<EUM_APP_KEY>") .withCollectorURL("https://mobile.eum-appdynamics.com:443") // The URL of the EUM Server(on-prem) .build()); iOS [Objective C] ADEumAgentConfiguration *adeumAgentConfig = [[ADEumAgentConfiguration alloc] initWithAppKey:<#EUM_APP_KEY#>]; // Set the Collector URL and Screenshot Service URL to the EUM Server URL. adeumAgentConfig.collectorURL = "https://mobile.eum-appdynamics.com:443"; adeumAgentConfig.screenshotURL = adeumAgentConfig.collectorURL; [ADEumInstrumentation initWithConfiguration:adeumAgentConfig]; [Swift] let configuration = ADEumAgentConfiguration(appKey: <#EUM_APP_KEY#>) // Set the Collector URL and Screenshot Service URL to the EUM Server URL. configuration.collectorURL = "https://mobile.eum-appdynamics.com:443" configuration.screenshotUrl = configuration.collectorURL ADEumInstrumentation.initWith(configuration) Note: The default endpoint for iOS and the Android agent is still https://mobile.eum-appdynamics.com:443, so even if this is not explicitly set, the agent will send data to the North America EUM Cloud. Europe Android  Instrumentation.start(AgentConfiguration.builder() .withAppKey("<EUM_APP_KEY>") .withCollectorURL("https://fra-col.eum-appdynamics.com:443") // The URL of the EUM Server(on-prem) .build()); iOS [Objective C] ADEumAgentConfiguration *adeumAgentConfig = [[ADEumAgentConfiguration alloc] initWithAppKey:<#EUM_APP_KEY#>]; // Set the Collector URL and Screenshot Service URL to the EUM Server URL. adeumAgentConfig.collectorURL = "https://fra-col.eum-appdynamics.com:443"; adeumAgentConfig.screenshotURL = adeumAgentConfig.collectorURL; [ADEumInstrumentation initWithConfiguration:adeumAgentConfig]; [Swift] let configuration = ADEumAgentConfiguration(appKey: <#EUM_APP_KEY#>) // Set the Collector URL and Screenshot Service URL to the EUM Server URL. configuration.collectorURL = "https://fra-col.eum-appdynamics.com:443" configuration.screenshotUrl = configuration.collectorURL ADEumInstrumentation.initWith(configuration) APAC Android Instrumentation.start(AgentConfiguration.builder() .withAppKey("<EUM_APP_KEY>") .withCollectorURL("https://syd-col.eum-appdynamics.com:443") // The URL of the EUM Server(on-prem) .build()); iOS [Objective C] ADEumAgentConfiguration *adeumAgentConfig = [[ADEumAgentConfiguration alloc] initWithAppKey:<#EUM_APP_KEY#>]; // Set the Collector URL and Screenshot Service URL to the EUM Server URL. adeumAgentConfig.collectorURL = "https://syd-col.eum-appdynamics.com:443"; adeumAgentConfig.screenshotURL = adeumAgentConfig.collectorURL; [ADEumInstrumentation initWithConfiguration:adeumAgentConfig]; [Swift]  let configuration = ADEumAgentConfiguration(appKey: <#EUM_APP_KEY#>) // Set the Collector URL and Screenshot Service URL to the EUM Server URL. configuration.collectorURL = "https://syd-col.eum-appdynamics.com:443" configuration.screenshotUrl = configuration.collectorURL ADEumInstrumentation.initWith(configuration) ... View more

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 and the Controller (backend and UI). Therefore, you may need to back it up with better hardware resources if you see performance degradation. To change the limits, follow the steps below: Log in to http://controller_host:8090/private/ControllerFlagsServlet using the credentials below: username: root@system password: same as your admin.jsp password Look for  appdynamics.controller.eum. cloud.ajax.limit and  appdynamics.controller.eum. cloud.page.limit and change the values, then save. Note: this is an on-prem-only feature, not available on SaaS." ... View more

If you do not see AJAX requests being reported, below are a few things you should check: The AJAX page name limit is getting hit The max AJAX limit is getting hit The page is navigating to another page before the Adrum Beacon posted The AJAX causes a redirect to another page The AJAX is done through the FETCH API   1. The AJAX page name limit is getting hit. Each EUM application can register up to 500 AJAX page names by default. If the AJAX requests are overflowing, this will limit all of the new AJAX requests that are not already registered with a page and they will get dropped on the EUM side.   This can be seen in the eum-processor.log if the logging is set to DEBUG in EUM/eum-procesor/bin/logback.xml .   2. The max AJAX limit is getting hit. By default, the JavaScript Agent limits the AJAX requests sent for base or virtual pages to 50. Although base or virtual pages normally do not send large amounts of AJAX requests, in some cases, a page may send redundant AJAX requests, especially those containing error reports.   For example, a series of redundant AJAX requests containing a dead loop of errors and exceptions with no new information could overload the EUM Server. To prevent an overload of AJAX requests, you can configure the JavaScript Agent to limit the number of AJAX requests sent for the base and virtual pages.   The code example below limits the number of AJAX request per base or virtual page to 7.   <head>    <script type='text/javascript' charset='UTF-8'>       window["adrum-start-time"] = new Date().getTime();       window['adrum-config'] = {          xhr: {             maxPerPageView: 7          }       };       ...      </script>    <script src='//cdn.appdynamics.com/adrum/adrum-latest.js' type='text/javascript' charset='UTF-8'/>    ... </head>   3. The page is navigating to another page before the Adrum beacon is posted. There can be situations when the base page or user triggered an AJAX call but, before the beacon reports it back to the EUM collector, the page redirects or the user navigates to another page and the last beacon gets aborted.   Little can be done since the browser will abort any pending requests in such cases, but you can turn off the buffer. By default, the beacon buffers 20 requests before going out or 5 seconds (whichever occurs first).       (function(config) {     config.channel = {         bufferMode: false     }         return config; })(window[‘adrum-config’] || (window[‘adrum-config’] = {}));   4.  The AJAX causes a redirect to another page. Similar to case 3, if the AJAX causes a redirect to another page, the beacon for the AJAX will not be prepared and it will be aborted.   5. The Async request is done through the FETCH API The Fetch API provides an interface for fetching resources (including across the network). It will seem familiar to anyone who has used XMLHttpRequest, but the new API provides a more powerful and flexible feature set.   This is currently not supported by the AppDynamic JavaScript Agent and is still a work in progress.  ... View more