> For the complete documentation index, see [llms.txt](https://docs.runway.team/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.runway.team/integrations/observability-and-analytics/new-relic.md).

# New Relic

<div align="left"><figure><img src="/files/d0mQMAJ3w3EgeHBmckke" alt=""><figcaption></figcaption></figure></div>

## Set up

### Navigate to the Integration settings view

1. Select an app in the top left corner from the Switcher
2. Navigate to **App Settings** by clicking the gear icon (⚙️) at the top of the Timeline sidebar
3. Click on **Integrations** in the sidebar

### **Connect New Relic**

1. Find the **New Relic** integration module under the **Observability & analytics** section
2. Click the **Connect** button.
3. If you've previously connected a New Relic integration for stability monitoring, you can use the same provider to connect New Relic for the observability & analytics capability. Alternatively, you can create a new installation by following the steps below.
4. Click **New installation** and enter an API key. You can create a New Relic API key by going to **Profile > API Keys.** :link:[New Relic API key documentation](https://docs.newrelic.com/docs/apis/intro-apis/new-relic-api-keys/).

{% hint style="info" %}
New Relic API keys are scoped at the user level. The user that generates the API key must have the following roles:

* **Mobile Applications**
* **Mobile Crashes**

For more information about New Relic user permissions, visit their [docs](https://docs.newrelic.com/docs/apis/intro-apis/new-relic-api-keys/).
{% endhint %}

4. Click **Save** to finish adding the integration provider.

### Configure New Relic

1. Select the application that's associated with your **Production environment.**
2. Select key events from your New Relic application to monitor in Runway.
   1. For custom events, the value you enter in the Event field should be the event type and event name with a period delimiter in between. For example, `Action.ClickButton`.
   2. For each event, you can optionally use the Attribute field to specify an event attribute (e.g. `amount`) to track attribute value-related metrics such as averages, medians, and percentiles. Alternatively, you can also use the Attribute field to filter events using basic query string syntax: for example, if you have a `page_load` event and want to measure unsuccessful loads on a "checkout" screen, you might enter `name=checkout&success=false` for the Attribute value.

{% hint style="info" %}
By default, Runway will create a handful of [health metrics](/using-runway/app-settings/health-metrics-settings.md) using the events you select as part of the integration setup to surface in the [**Rollout**](/using-runway/rollout.md) view of each release. You can further customize and configure these health metrics, including setting acceptable thresholds, connect them to [rollout automations](/automations/types-of-automations.md#halt-unstable-phased-releases) and more!&#x20;

For a complete list of all available metrics , visit the [Metric Types documentation](/using-runway/app-settings/health-metrics-settings.md#metric-types).
{% endhint %}