Skip to main content

​
About New Relic Integration

The New Relic Integration lets Sawmills use New Relic credentials for metrics usage features. When you save the New Relic configuration, Sawmills validates the credentials and checks predefined permissions before storing them.

​
Step-by-Step: Configure New Relic Integration

​
1. Access Integrations

Open the user menu at the top right and select Integrations.

​
2. Open New Relic Configuration

In the Integrations section, click on Add New Relic Account.

​
3. Enter Credentials

Provide:
  • New Relic User API Key
  • New Relic Account ID
  • New Relic Account Region

​
Set up New Relic Dedicated User

For production, use a dedicated New Relic user account (acting as a service account, not a personal user key).

​
1. Create a user in New Relic

Create a dedicated user for Sawmills integration usage. A Basic user type is usually sufficient since it provides access to the API and querying capabilities without incurring billable costs like a Core or Full Platform user.
Optional: Restrict to Read-Only AccessIf you want to strictly enforce the principle of least privilege, you can choose to restrict this user to read-only access. In New Relic, you do this by creating a Group for the user, and then creating an Access Grant that links the new group to your target Account with the built-in Read Only role.

​
2. Create keys for the user

  • Create a User API Key in New Relic for this dedicated user.
  • Find your Account ID.
  • Use those credentials in the Sawmills New Relic integration along with your account’s region.

​
3. Save and Validate

Click Save. Before persisting, Sawmills runs validation and shows:
  • User key, account and region status: Working or Invalid
  • Required permissions status
  • Per-permission status for predefined checks
Save is blocked if credentials are invalid or required permissions are missing.

​
Backend Validation Flow

Validation is enforced in the backend service:
  • POST /v1/notification-integrations/newrelic/validate: validates credentials and returns per-permission status.
  • POST /v1/notification-integrations: blocks save when credentials are invalid or required permissions are missing.
  • PATCH /v1/notification-integrations/{id}: re-validates merged New Relic config before update is persisted.

​
Required Permissions

  • alerts
  • entitySearch