> 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
Discover users, track roles and license tiers, and monitor login activity across your New Relic organization
### 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. New Relic requires Pro or Enterprise edition to customize groups and roles — organizations on other editions have only the standard roles |
| Login Activity | Track user sign-ins to identify active and inactive users — one login event per user per day |
| 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 — this is the role that carries the permissions for adding and managing users, so it is what lets Harmony read users, groups, and roles. Members of New Relic's default **Admin** group have it
* **Account access for login data**: Harmony reads login events per New Relic account, and a User key only reaches the accounts its owner can access. Make sure the key's owner has access to your organization's parent/reporting account
* **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 New Relic as the user described in [Prerequisites](#prerequisites)
2. Open the **API keys** page for your data center — [one.newrelic.com/api-keys](https://one.newrelic.com/api-keys) (US), [one.eu.newrelic.com/api-keys](https://one.eu.newrelic.com/api-keys) (EU), or [one.jp.newrelic.com/api-keys](https://one.jp.newrelic.com/api-keys) (JP). The same page is reachable from the user menu by clicking **API keys**
3. Click **Create a key** in the top-right corner of the **API keys** page
4. Enter a key name (e.g. `Harmony Integration`), select **User** for the **Key type**, and click **Save**
5. Copy the generated key (it starts with `NRAK-`)
{% hint style="warning" %}
**Copy the key immediately.** New Relic shows the full key only while you are creating it — afterwards only the first 8 characters are displayed in the API keys UI, and recovering the full value requires a NerdGraph query. If you lose it, create a new key.
{% endhint %}
{% 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 (for example, a member of the default Admin group) 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 %}
### Disconnect New Relic from Harmony
1. Log in to your Harmony dashboard
2. Go to **Settings** > **Integrations**
3. Find **New Relic** under **SaaS Applications** and click the integration card
4. Click **Disconnect**
5. Confirm the disconnection when prompted
Once disconnected, Harmony stops syncing data from New Relic. Previously synced data remains available in Harmony. To revoke access on the New Relic side as well, delete the User key from the **API keys** page.
### 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 — one event per user per day
{% hint style="info" %}
**Refresh cadence:** Harmony refreshes login activity every hour and the user inventory every 6 hours. The first sync backfills about 90 days of login activity, and later syncs pick up where the previous one finished.
{% endhint %}
{% hint style="info" %}
**Login events are collapsed to one per user per day.** Harmony records that a user signed in on a given day rather than every individual sign-in, which is what drives the active/inactive picture and seat-reclamation signals.
{% endhint %}
{% 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 %}
### Permissions Explained
Harmony uses the User key read-only — it only queries New Relic and never modifies users, groups, roles, or accounts.
| What Harmony reads | What the key's owner needs |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Users, groups, and roles | The **Authentication domain manager** role, and a **Core** or **Full platform** user type |
| Login events (audit log) | No special role — every user type can query data for the accounts they have access to, so the owner must have access to the account the login events are written to |
| Organization and account list | No special role — used to identify your organization and the accounts Harmony should query |
### Use Cases
License Optimization
Spot Full platform or Core users who rarely sign in and downgrade them to reduce New Relic spend
Access Review
Review each user's New Relic roles — in New Relic's own terms — as part of periodic access certification
Offboarding Verification
Confirm departed employees no longer appear as active New Relic users
Shadow Access Detection
Compare New Relic's user list against your identity provider to find accounts created outside standard provisioning
### Troubleshooting
The connection fails or no users are synced
**Possible causes:**
* The key's owner does not hold the **Authentication domain manager** role, or is a Basic user rather than a Core or Full platform user
* The wrong **Data center region** was selected — the key only works against the region its organization lives in
* Only the truncated key was copied (New Relic shows the full key once, at creation time)
**Solutions:**
1. Confirm the key's owner has the Authentication domain manager role and a Core or Full platform user type
2. Reconnect using the region that matches the address you use to open New Relic
3. Create a fresh User key and copy it immediately, then reconnect
Roles are reported as not collected
**Possible causes:**
* The key's owner cannot read role grants, so Harmony records roles as not collected rather than guessing them
* Your New Relic organization is not on Pro or Enterprise edition, so custom groups and roles are not available and users only carry the standard roles
**Solutions:**
1. Re-create the key as a user with the Authentication domain manager role and reconnect
2. Users still sync in full — only the role field is affected
Login activity is missing or incomplete
**Possible causes:**
* New Relic writes user, permission, and login events only to the **parent/reporting account** of your organization — child accounts contain none
* The key's owner does not have access to every account in the organization, so accounts they cannot read are skipped
**Solutions:**
1. Make sure the key's owner has access to your organization's parent/reporting account
2. Grant the key's owner access to any additional accounts whose login activity you expect to see, then wait for the next hourly refresh
### Data & Privacy
Key privacy principles
For information about how Harmony handles your data, see our [Privacy Policy](https://harmony.io/privacy).
* Harmony accesses New Relic data in read-only mode and does not modify any data in your New Relic organization
* Access can be revoked at any time by disconnecting the integration in Harmony or deleting the User key in New Relic
---
# 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=&goal=
```
`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.