• EnglishEspañol日本語한국어Português
  • Log inStart now

Mobile monitoring best practices guide

By eliminating crashes and increasing speed across the stack, you can build better performance into every mobile app release. Here are some best practices to take full advantage of mobile monitoring with New Relic.

1. Start collecting data

Start collecting data in production.

You'll see immediate value by adding our mobile monitoring SDK to your app for its next release to the app store. We recommend installing the iOS or Android agent to your production release even if you're simply testing New Relic's capabilities. This will ensure you'll get an adequate amount of data to really understand all of our mobile monitoring capabilities and your end users' experience.

How to do it

2. Explore your data

Immediately be able to explore your data.

As soon as New Relic starts reporting data, take the time to explore the wealth of information about your mobile apps. To get started, go to one.newrelic.com and select Mobile.

How to do it

3. Take preventive steps

Use alert notifications to help uncover the causes behind crashes and errors.

Once you are running our mobile monitoring capabilities in production and have explored some of the key features, you can use New Relic to uncover critical issues with your mobile application. In particular, focus on crashes and errors.

  1. Use metric-based as a starting point to gain high-level visibility into problems.
  2. Then, as new services or functionalities are added, use New Relic's more targeted, event-based (NRQL) alerts to make sure that the most critical issues are handled swiftly.

Use these alerts to determine whether a crash is impacting a large number of users. If it is, the relevant people (for example, both the mobile app team's on-call member and the owner of the related backend service) will be alerted.

Make sure that your team knows how to respond to changes in crash rate (crashes per sessions) and the percentage of users impacted by crashes of your mobile app.

How to do it

4. Dig deeper into crashes

Take your crash reporting to the next level.

Now it's time to tackle some of those harder-to-reproduce crashes by:

  1. Applying additional instrumentation to your application.
  2. Leveraging crash event trails, NRQL queries, and dashboards to visualize your data.

How to do it

5. Focus on KPIs

Bring your key performance indicators to life.

Create custom interactions and events to hone in on the most important signals, including user activity for the business-critical aspects of your app. Using these powerful APIs, you can add custom instrumentation to just about anything. The following are some example use cases.

How to do it

Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.