The New Relic integration enables security and compliance teams to verify that infrastructure monitoring and alerting controls are properly configured. It connects Drata to New Relic so your team can validate monitoring alerts for infrastructure metrics and provide evidence that systems are actively monitored.
Key Capabilities
Infrastructure monitoring verification: Validate alerts for key infrastructure metrics
Alert configuration monitoring: Confirm alert conditions exist in New Relic
Automated evidence collection: Provide proof that infrastructure monitoring controls are configured
This integration is used to automate tests such as infrastructure monitoring verification and database monitoring validation, helping prove compliance with infrastructure monitoring and operational security policies.
Prerequisites & Data Access
Administrator access to your New Relic account
Ability to generate a New Relic API Key (User key type)
Your New Relic Account ID
AWS integrated with New Relic for infrastructure monitoring tests
Required Drata Role with Write access: Admin, Workspace Managers, DevOps Engineer
Access Reviewers (Access Reviewers can only Read the connection page they can’t make changes)
Important requirement:
Drata currently supports New Relic’s US data center region only.
EU region accounts typically use URLs beginning with:
rpm.eu.newrelic.com
Permissions & Data Table
Permission/Scope | Why It’s Needed |
New Relic API Key (User type) | Allows Drata to authenticate and retrieve alert and monitoring data |
Alerts view permission | Allows Drata to verify monitoring alerts and policies |
AWS integration in New Relic | Enables infrastructure monitoring tests to validate AWS metrics |
Step-by-Step Setup
Step 1: Verify AWS Integration in New Relic
All New Relic monitoring tests require an AWS ↔ New Relic integration.
Log in to your New Relic account.
Verify that Amazon Web Services is installed under your New Relic integrations.
If the integration is not configured, follow New Relic’s guide to connect AWS.
Expected outcome: New Relic can retrieve AWS infrastructure metrics required for Drata monitoring tests.
Step 2: (Optional) Create a Custom Role
Drata only requires the ability to view Alerts. Creating a service account with limited permissions is recommended.
Navigate to https://one.newrelic.com.
Hover over your username and select Administration.
Create a custom role following New Relic’s role management guide.
Configure the role with View permissions for Alerts.
Assign the role to the user that will generate the API key.
Expected outcome: A user account exists with limited permissions to access alert data.
Step 3: Create a New Relic API Key
Navigate to https://one.newrelic.com.
Hover over your username and select API Keys.
Click Create a key.
Configure the following:
Account: Select the account used for the connection
Key type:
UserKey name: Drata recommends
Drata API Key
Click Create a key.
After the key is created:
Click the “…” menu
Select Copy Key
Important:
Copy the API Key, not the Key ID.
Expected outcome: You have a New Relic API key for the integration.
Step 4: Find Your Account ID
Log in to New Relic.
Navigate to your account settings.
Locate and copy your Account ID.
Expected outcome: You have the Account ID required for the connection.
Step 5: Connect New Relic in Drata
Log in to Drata → go to the Connections page.
Navigate to your Available Connections.
Search for and start the New Relic connection process.
Enter the following when prompted:
Account ID
API Key
Region: US
Expected outcome:
New Relic is successfully connected and monitoring configuration data begins syncing to Drata.
Important Notes
Drata currently supports New Relic’s US data center region only.
If your New Relic URL begins with
rpm.eu.newrelic.com, your account is in the EU region, which is not currently supported.For infrastructure monitoring tests to pass:
Monitoring alerts must exist in New Relic
Alerts must contain the expected infrastructure metrics
Active notifications must be configured for the alert policies
AWS infrastructure must be connected to New Relic for monitoring tests to validate AWS metrics.
Important Note: At this time, Drata only supports New Relic's US data center region. If you are uncertain of your region, an EU region URL will begin with "rpm.eu.newrelic.com/."
It is recommended to create a service account user to limit the access that Drata has to your New Relic instance. The steps below detail how to do that. Full permission capabilities can be found here: https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-user-management/user-capabilities/#alerts
Monitoring Test | New Relic Metric Name |
Database CPU Monitored | RDS:
DocDB:
|
Database Free Storage Space Monitored | RDS Free Storage Space:
RDS Free Local Storage:
DocDB Free Local Storage:
|
Database Read I/O Monitored | RDS Read IOPS and SelectThroughput:
DocDB ReadIOPS and SelectThroughput:
|
Messaging Queue Message Age Monitored | provider.approximateAgeOfOldestMessage aws.sqs.ApproximateAgeOfOldestMessage |
Infrastructure Instance CPU Monitored | Instance CPUUtilization:
Cluster CPUUtilization:
|