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
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 userHarmony Account: Active Harmony workspace
Connect New Relic to Harmony
Step 1: Create a User API key
Sign in to one.newrelic.com
Go to Administration > API keys
Click Create a key, choose key type User, and name it (e.g.
Harmony Integration)Copy the generated key (it starts with
NRAK-)
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
Log in to your Harmony dashboard
Go to Settings > Integrations
Find New Relic under SaaS Applications and click Connect
Step 4: Enter Credentials
Enter your User API key
Select your Data center region
Click Connect
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)
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.
Use Cases
Last updated
Was this helpful?
