Cross-account alert

New Relic's cross-account alert option enables you to set up alert conditions that monitor data from a different account than the one where the alert is configured. This feature allows for greater flexibility in monitoring and managing dependencies across multiple accounts within New Relic.

In many organizations, different teams or departments may use separate New Relic accounts for their applications and infrastructure. Even if you are not directly responsible for an entity or data in another account, it may still be critical to your operations. For example, an application team might need to set up alerts for the hosts that run their application but are managed under a different account.

This offers several benefits to:

• Manage alerts across multiple accounts that you have access to, enabling a consolidated view of all relevant incidents and issues.
• Limit write and edit access to sensitive accounts, minimizing the need for multiple users to have permissions on accounts they do not directly manage.
• Organize alert configurations by reducing unnecessary alerts on accounts that serve as data sources for others.
• Delegate alert threshold management and governance to the appropriate teams, easing the burden on account owners.
• Ensure timely alerts for critical dependencies, even if they reside in different New Relic accounts.

Get started

Before you start using cross-account alerts:

• You must first enable the data sharing between accounts. This is currently being done only on a per-account basis in New Relic UI.
• Organization managers will have the ability to turn the data-sharing toggle on.
• Alternatively, you can create a custom role with the Cross-account conditions: Data-sharing access control permission and assign it to the users to whom you want to grant this capability. For more information, refer to Create custom roles.

Once you've ensured your user has the proper role and permission, you can allow other accounts to query data from the selected account by following the below steps:

There is also an API that enables users with the appropriate roles and permissions to opt multiple accounts in or out simultaneously. For more information, refer to Add API examples for cross-accogit unt alert elections.

As long as you have at least read-only access to the data account, you can create alert conditions and query data from any account within your organization.

Create a cross-account alert condition

You can create cross-account alerts in the following ways:

• API: Enter the account number you'd like your condition to target in the dataAccountId field in the condition builder API. For more information, refer to NRQL condition.

  -OR-

• UI: In the query mode of the condition builder UI, you'll see a drop-down as part of the first step. This menu lists the accounts that you can access for querying in your new alert. For more information, refer to Create alert condition using query mode.

Restrict data sharing for cross account alerts

When an account stops sharing data (the Let other accounts query data from this account option is disabled), then:

• The account does not appear in the drop-down, when choosing where to query for your new alert conditions.
• Any previously created alert conditions targeting that account's data will be deleted, and evaluation will stop. All history pertaining to that condition will be deleted.

Data visibility

Currently, when using this feature, any user with at least read access to the account that owns the alert condition can view cross-account alert condition information. This access is granted regardless of whether the user has read access to the originating account. Users can see:

• Condition names and details, including condition signals, facet names, etc.
• Issues and incidents pertaining to the cross account condition, including signals, facet names in the incident titles, etc.
• Workflows to set up notifications on cross account alert conditions.