Here in Support, we get a lot of tickets about account structure and account moves. How you choose to structure your New Relic account has implications for years to come.
Let’s break down the top things to consider before setting up your New Relic account.
Data cannot be moved from one account to another.
New Relic doesn’t have the feature of moving historical data from one account to another. When you change the license key on an application to report to a different account, historical data will remain in the old account, which means if you want to query that historical data, you need to go to the old account to do so.
Be intentional when it comes to setting up applications in an account, so all the data in your applications are in one place.
Users that have access to a parent account have access to all sub-accounts, too.
Set up your parent account with thoughtful consideration. Who should have keys to the main house with unfettered access? I’m guessing only those who really need it.
For example, a contractor working on one project probably shouldn’t have access to the parent account because then that user has access to all sub-accounts.
Consider, too, how you are using a parent account to gather data. Are you using a parent account like a sub-account? For a specific project with a variety of users who may come and go in an organization? Why not spin up a sub-account for that project and keep the parent account more tightened up?
Again, don’t forget: data cannot be moved from one account to another account. So, if you decide you want to spin up a new parent account for your sub-accounts down the road, it’s going to be a complicated process, and all data will stay where started.
Sub-accounts inherit their parent’s subscription, including data retention.
All subscriptions on the parent account trickle down to the sub-accounts below it. This includes data retention, so if a parent account has 30 days of Insights data retention, the sub-accounts will too.
This is an important factor when it comes to usage: the sub-accounts and its parent share usage and reporting rolls up to the parent account, which can be viewed on the Unified Usage page. Account-wide usage can then be queried from the parent account. If you were to spin up a new parent account, the historical usage data would stay with the old parent account.
Another aspect to consider is when a sub-account becomes its own standalone account, its subscription is reverted to Lite, which has a 24-hour retention period. If a subscription isn’t immediately applied to it, historical data can be lost.
Sub-accounts inherit their parent’s SSO/SAML configuration.
In New Relic’s account structure, the parent account’s SSO configuration trickles down to all sub-accounts, which means if you enable SSO on the parent account, users on that account and all sub-accounts must be listed on the Identity Provider (IDP) side.
It is possible to have SSO enabled separately on sub-accounts by using a custom entity ID, but if you choose to go that route, we do not recommend setting up SSO on the parent account.
How you choose to set up your New Relic account structure has crucial implications thanks to account inheritance and the inability to move data between accounts. Please don’t hesitate to open a Support ticket if you have specific concerns or questions about setting up your account structure. We want you to be set up for success the moment you open a New Relic account!