PDFs

On this page:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
15 rates
You set up and configure Mobile RUM in two areas:

  • Your AppDynamics Controller
  • Your iOS and/or Android application

To prepare Mobile RUM you need to make changes in both these areas in a particular order.

You need to do the following:

  1. Check your prerequisites

  2. Review Controller capacity

  3. Evaluate your mobile application

  4. Complete the Getting Started Wizard

  5. Instrument and verify your app

  6. Configure network request naming and thresholds

Check Your Prerequisites

Before you can use AppDynamics to monitor your mobile application, you need to make sure you have the following prerequisites:

  • An AppDynamics account, with access to an AppDynamics Controller
  • A Mobile RUM License. See Mobile RUM Licenses.
  • Access to your mobile application source code

Review Your Controller Capacity

If you use an on-premises Controller and plan to monitor mobile applications, assess your Controller's capacity to accommodate the increase in the number of metrics that Mobile RUM will generate. The number of individual metric data points generated depends on the level of activity of your mobile applications. As a rough guide, the use of Mobile RUM can increase the number of metric data points by as much as 15 to 25K per instrumented application, if your applications are heavily accessed by mobile users. The actual number depends on how many network requests your applications receive.

The number of separate RUM metric names saved in the Controller database can be larger than the kinds of individual data points saved. For example, a metric name for a metric for iOS 5 might still be in the database even if all your users have migrated away from iOS 5. So, the metric name would no longer have an impact on resource utilization, but it would count against the default limit in the Controller for metric names per application. The default limit for names is 200,000 for Browser RUM and 100,000 for Mobile RUM.

For more information about Controller sizing, see Hardware Requirements per Performance Profile

Evaluate Your Mobile Application

By default, Mobile RUM can monitor your application in two ways: network requests and crash reporting.

If you want to collect information on network requests, your application must make HTTP calls using specific classes:

  • An iOS application must use NSURLConnection or NSURLSession to generate network requests.
  • An Android application must itself (i.e., not via an external framework) use HttpURLConnectionHttpsURLConnection, HttpClient, OkHttp, or ch.boye.httpclientandroidlib  to generate network requests.
  • Using the SDK, custom HTTP libraries can also be monitored and used by the agent itself. See Customize Your Instrumentation with the iOS SDK and Customize Your Instrumentation With the Android SDK for more information.

Even if your application does not generate network requests, or if you do not want to monitor that activity, you can use AppDynamics purely to monitor crashes. You can also extend the Mobile Agents using the SDK to collect other data, like how your application is functioning internally.  

Complete the Getting Started Wizard

Use the Getting Started Wizard to create a mobile app group, get an EUM App Key, and guide you through the instrumentation process. Once you have successfully completed the steps in the wizard, Mobile RUM will automatically be enabled for the created mobile app group.

Your Controller must have a Mobile RUM license before you can enable the Mobile RUM functionality.

Disable Mobile RUM

To later disable/enable Mobile RUM:

  1. Open your mobile application. 
  2. From the left-hand navigation bar, click Configuration.
  3. Click Container Configuration >.
  4. Toggle the Mobile Monitoring switch to OFF/ON.

Get Your Application Key

To find your App Key after you've completed the Getting Started Wizard:

  1. Open your mobile application.
  2. From the left-hand navigation bar, click Configuration.
  3. From the Configuration page, you can view the EUM App Key in the Container Configuration section as shown below.

Instrument and Verify Your App

The method you follow to instrument your app depends on your platform:

Configure Network Request Naming and Thresholds

You can customize how you want the Controller to name your application's requests and what performance thresholds you want to be in effect. See Configure Mobile Network Request Naming and Thresholds.

External Access

Mobile RUM is made up of several components, any or all of which can either be located on the Internet or hosted inside your own data center/network. On-premises access points are configured at installation or through the UI. But if your installation requires access to any of these components on the Internet, the following is a list of the locations where the various components can be accessed. You need to make sure the appropriate URLs are accessible from your network.

  • The Mobile Agent sends its data from the browser to the EUM Server. On the Internet, the mobile app sends its beacons to mobile.eum-appdynamics.com:443.
  • The EUM Server sends analytics data to the Events Service. On the Internet, the EUM Server sends its data to analytics.api.appdynamics.com:443.
  • The Controller fetches data from the EUM Server. On the Internet, the Controller fetches data from api.eum-appdynamics.com:443.
  • The Controller queries the Events Service. On the Internet, the Controller queries analytics.api.appdynamics.com:443.