Back

Apps crash. You want to know why. With the New Relic Mobile Crash connector, you can find out all the reasons your apps crashed, and how you can solve and prevent those crashes quickly and easily. This article describes how to configure the New Relic Mobile Crash connector in your Universal Data Hub account.

This article covers the following topics:

Table of Contents Placeholder

How It Works

In the event of a system crash, incoming data from live events is captured. Crash tracking connectors in the UDH can then utilize cloud delivery methods to forward crash data to vendors and customize the display of relevant data in live events.

Requirements

  • New Relic Account
  • API Key

Recommended SDK modules:

Supported Actions

Action Name Trigger on Audiences Trigger on Events
Send Android Crash Event


Configure Settings

Go to the Connector Marketplace and add a new New Relic Mobile Crash connector. Read the Connector Overview article for general instructions on how to add a connector.

To configure your vendor, follow these steps:

  1. In the Configure tab, provide a title for the connector instance.

  2. Enter the API key that you received from New Relic for your account.

  3. Provide additional notes about your implementation.

Action Settings: Parameters and Options

Click Next or go to the Actions tab. It's where you'll set up actions and trigger them.

This section describes how to set up parameters and options for each action.

Action: Send Android Crash Event

The connector automatically maps event attributes to the requisite fields before being sent over to New Relic.

Parameters

  1. Crash Event Attributes:  These parameters allow for you to override the default mappings.

Options: Crash Event Attributes

Option Description Example
App Name User-readable app name My App
App Build App build ID 1
App RDNS Bundle ID com.tealium.example
App UUID Install ID a4cc5192-cde5-4788-bb0a-fc7c06ac07eb
App Version Version 1.0.1
Connection Type Internet connection WIFI
Crash Build ID Build ID c0319246-ff40-4fdc-877f-7341ad48f52c
Crash Cause Human readable cause Index out of bounds
Crash Name App-generated name java.lang.RuntimeException
Crash Process ID Low-level process ID 0
Crash Threads Array of stringified JSON ["{\"crashed\":true, \"state\":\"RUNNABLE\", \"threadNumber\":1, \"threadId\":\"main\", \"priority\":5,\"stack\": [{\"className\": \"com.tealium.example.fragment.ControlFragment\", \"methodName\":\"onClick\", \"lineNumber\":89}]}"]
Crash UUID Unique crash identifier c0319246-ff40-4fdc-877f-7341ad48f52c
Device Device name motorola
Device CPU Type Architecture armv7l
Device Free System Storage Space available in bytes 48189440
Device Free External Storage Space available in bytes 2208235520
Device Memory Usage RAM usage percentage 62
Device Model Technical model number XT1028
Device Orientation 0-3 according to the docs 1 (90 degree rotation)
Device OS Version Major OS version 5.1
Device OS Build OS Build version 2
Device Resolution Screen resolution 1024x768 or normal
Device Runtime Runtime version 2.1.0
Platform Platform name Android
Timestamp Epoch ms since epoch 1497563845000