> 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/stability-monitoring/new-relic.md).

# New Relic

## 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 **Stability monitoring** section.
2. Click the **Connect** button.
3. 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](#set-up).
{% 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 the application that's associated with your **Beta** **environment**. This field is optional, but recommended if your app has a [beta testing integration](/integrations/beta-testing.md) connected.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.runway.team/integrations/stability-monitoring/new-relic.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.