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

# New Relic

### About New Relic

New Relic is an observability platform used by engineering teams to monitor applications, infrastructure, and logs. Connecting New Relic to Harmony gives IT teams visibility into who has access to New Relic, what roles they hold, which license tier each user consumes, and when users actually sign in.

### What the New Relic integration enables

| Capability             | Description                                                                       |
| ---------------------- | --------------------------------------------------------------------------------- |
| User Discovery         | Surface all New Relic users in Harmony's software inventory                       |
| License Tracking       | See each user's tier — Basic, Core, or Full platform — to understand billable use |
| Role Visibility        | View the roles granted to each user through their New Relic groups                |
| Login Activity         | Track user sign-ins to identify active and inactive users                         |
| Multi-Instance Support | Connect multiple New Relic organizations                                          |

### Prerequisites

* **New Relic Admin Access**: A Core or Full platform user with the **Authentication Domain Manager** role (required to read users) — an **Organization manager** covers all needed permissions
* **User API Key**: A User key (`NRAK-...`) created by that user
* **Harmony Account**: Active Harmony workspace

### Connect New Relic to Harmony

#### Step 1: Create a User API key

1. Sign in to [one.newrelic.com](https://one.newrelic.com)
2. Go to **Administration** > **API keys**
3. Click **Create a key**, choose key type **User**, and name it (e.g. `Harmony Integration`)
4. Copy the generated key (it starts with `NRAK-`)

{% hint style="info" %}
The key inherits the permissions of the user who creates it. Create it as a user with the Authentication Domain Manager role (or an Organization manager) so Harmony can read users, groups, and roles.
{% endhint %}

#### Step 2: Identify your data center region

Check the address you use to open New Relic:

* `one.newrelic.com` — **United States (US)**
* `one.eu.newrelic.com` — **Europe (EU)**
* `one.jp.newrelic.com` — **Japan (JP)**

#### Step 3: Navigate to Integrations

1. Log in to your Harmony dashboard
2. Go to **Settings** > **Integrations**
3. Find **New Relic** under **SaaS Applications** and click **Connect**

#### Step 4: Enter Credentials

1. Enter your **User API key**
2. Select your **Data center region**
3. Click **Connect**

{% hint style="info" %}
To connect additional New Relic organizations, repeat this process with a key from each organization.
{% endhint %}

### What Harmony Syncs

**From New Relic:**

* Users (name, email, last active time)
* User tier per user (Basic, Core, or Full platform)
* Groups and the roles granted through them
* Login events from the New Relic audit log (up to 13 months of history)

{% hint style="warning" %}
If the API key's user lacks permission to read role grants, users still sync — their roles are simply reported as not collected rather than guessed.
{% endhint %}

### Use Cases

<details>

<summary>License Optimization</summary>

Spot Full platform or Core users who rarely sign in and downgrade them to reduce New Relic spend

</details>

<details>

<summary>Access Review</summary>

Review each user's New Relic roles — in New Relic's own terms — as part of periodic access certification

</details>

<details>

<summary>Offboarding Verification</summary>

Confirm departed employees no longer appear as active New Relic users

</details>

<details>

<summary>Shadow Access Detection</summary>

Compare New Relic's user list against your identity provider to find accounts created outside standard provisioning

</details>


---

# 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.harmony.io/integrations/saas-applications/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.