This will open the query builder.įrom the query builder, you can add the error data to a dashboard and share it via a. Select View query and then View in Insights.To explore the data behind any of the charts or lists on the HTTP errors/requests page: View and share error data with query builder From the Error summary page, you can view the version information, request attributes, and Response body, as well as get a breakdown of error types for the request URL. To view details about an error or failure, select the Request URL link to be directed to the Error summary page.
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. This helps you take more of the guesswork out of resolving your mobile application's HTTP errors. A table comparing the error attribute's distribution to that of other errors.A pie chart showing how the error's attribute is distributed for values that deviate the most.For each attribute, the error profile includes: Select the version that you want to see charts and lists for in the Versions dropdown.Įrror profiles provide visual details about significant differences in the frequency of different values for HTTP error events. View information for one specific app version Select a new time period from the Time picker dropdown. To clear filters, select the X next to the filter you want to clear. The filters you select display next to the filter dropdown. See which filters you applied or remove filters Select an error or failure from the Errors and failures list and/or select multiple filters from the Filter dropdown. By default, the Network errors page is grouped by request domain and sorted by errors and failures.įilter for specific errors and network failures Make selections from the Group by and Sort by dropdowns. Group, sort, and filter errors and failuresĬhange how the page groups and sorts errors and network failures
You can also define NRQL alerts that are focused on error types for your critical services or query your app data.
There are two ways to get to the HTTP errors page: 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. 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.įind 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. Make sure that a new version of your app does not cause a spike in errors compared to a previous version. 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. View the data on the HTTP errors page to.