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

HTTP errors: Analyze network failures

The HTTP errors page helps you understand why network failures are occuring and share actionable data with your team.

To access the HTTP errors page, go to one.newrelic.com > All capabilities > Mobile > (select an app) > HTTP Errors.

Who might use the HTTP errors page?

Team member

View the data on the HTTP errors page to...


See a list of errors and failures so you can coordinate mobile app teams with backend teams and share the data they need to fix issues.

QA engineer

Make sure that a new version of your app does not cause a spike in errors compared to a previous version.

DevOps engineer

See a list of domains and URLs associated with HTTP errors and network failures so you can focus on the ones that are causing errors and filter out status codes that are too noisy for your alerts.

Mobile developer

Find out if there are frontend or backend problems affecting your mobile app (even without an error alert going off) so that you can address them in a new version.

Support engineer

View the errors and session attributes (geography, connection type, device, app version) associated with an error so that you can help customers with their issues.

Discover the HTTP errors page

From the HTTP errors page, investigate HTTP request and network failures:

  • Use any standard page functions to look for trends in Errors and failures charts.
  • Target specific types of errors and failures by grouping, sorting, and filtering the data.
  • Find anomalies in your request errors with HTTP error profiles.
  • Select an error or failure to view details for it.

You can also define NRQL alerts that are focused on error types for your critical services or query your app data.

Group, sort, and filter errors and failures

If you want to do this...

Do this...

Change how the page groups and sorts errors and network failures

Make selections from the Group by and Sort by dropdowns. By default, the Network errors page is grouped by request domain and sorted by errors and failures.

Filter for specific errors and network failures

Select an error or failure from the Errors and failures list and/or select multiple filters from the Filter bar.

See which filters you applied or remove filters

The filters you select display in the filter bar. To clear filters, select the X next to the filter you want to clear.

Change the time window

Select a new time period from the Time picker dropdown.

View information for one specific app version

Select the version that you want to see charts and lists for in the Versions dropdown.

HTTP error profiles

Error profiles provide visual details about significant differences in the frequency of different values for HTTP error events. For each attribute, the error profile includes:

  • A heatmap showing how the error's attribute is distributed for values that deviate the most
  • A label comparing the error attribute's distribution to that of other errors

This helps you take more of the guesswork out of resolving your mobile application's HTTP errors. You can more easily determine if you safely ignore the error, or if you should attempt to resolve the error with a new deployment, code change, customer communication or other actions.

Drill down into a single error

To view details about an error or failure, select the request URL from the top 20 errors list. From the error summary page, you can view the version information, request attributes, and response body and get breakdown of error types for the request URL.

Query and share error data

To explore the data behind any of the charts or lists on the HTTP errors page:

  1. Select for any chart.
  2. Select View query.

From the query builder, you can add the error data to a dashboard and share it via a permalink.

To dig deeper into the error data, query your data for the following events and attributes:

Get trace details

Mobile monitoring will capture the response details from HTTP requests that return a 400 or 500 level status code. In addition, error messages generated from Android apps will include a stack trace.

To view details about an error trace on the Errors page, select its request URL link. From here you can:

  • View the response body.
  • Share the error details with others by email.

The errors chart also appears on the selected mobile app's Summary page.

Troubleshoot unknown errors or URL errors

The mobile agents maintain a list of exception types. In some cases, custom exceptions thrown by applications fall outside of this list. When this happens, Unknown may appear in the mobile Errors page.

If you find Unknown in your list of errors and need assistance in researching which exception types are being missed, get support at support.newrelic.com.

Copyright © 2024 New Relic Inc.

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