Account Creation for New Relic

Makes a new New Relic account in the organization you are working in, to its naming convention, with its groups and their roles, a budget plan in Ingest Budgets and a row in Chargeback. It happens in two stages. Anyone granted this module asks for an account, which stages a request. An admin reviews the request and submits it for creation, and only that makes anything in New Relic.

Requesting an account

Fill in the parts of the name; the account name is shown as it builds, with the groups that will be made with it listed beneath. Give the monthly ingest expected, in MB, GB or TB, the cost center, and the account owner's first name, last name and email address. Create account stages the request. It appears under Requests as Pending.

A name already asked for in another request is refused. The owner is recorded with the request and becomes the budget owner in Chargeback. No New Relic user is made for them, and they are not added to any group.

Requests

Every request is kept, with its status: Pending, Created, Failed or Rejected. The list shows all of them, and the dropdown narrows it to one status. While a request is pending, the person who made it and any admin can Change it. Once it is created, failed or rejected it can no longer be changed.

Review, for admins

Review reads New Relic and shows exactly what creating would make, without making anything:

• the account, and the data center it is made in;
• each group, the authentication domain it is made in, and the roles it is given on the new account;
• the budget plan, named after the account and set to the monthly ingest asked for, holding the account;
• the chargeback row, with the first part of the name as the subaccount group, the owner as budget owner, and the cost center.

Anything that stands in the way is listed first and creating is not offered until it is dealt with: New Relic already having an account of that name, a role or domain that no longer exists, or a name that no longer fits the conventions.

Create in New Relic asks once more and then runs. Reject needs a reason, which the person who asked sees against their request.

A rejected request stays in the list as Rejected. An admin can Resubmit it, which makes it pending again with the reason it was rejected still shown, so it can be changed, reviewed and created like any other. It is refused if another request has asked for the same name in the meantime.

An account made in New Relic cannot be removed from here. It can only be cancelled in New Relic's own administration.

When it runs

The steps run in order: the account, then each group and its roles, then the budget plan, then the chargeback row. Each is recorded as it finishes, and the request shows them ticked off. One account is created at a time, and it carries on if you leave the page.

If a step fails the request is marked Failed and says which step and why. Review and retry carries on from the first step that is not done: an account already made is not made again, and a group already made is only given its roles. If the account itself was made, the budget plan and chargeback row are still written even when a group failed, so the account is not left unbudgeted.

The chargeback row is added with GBL left blank, since a request does not carry one. Complete it in Chargeback. If a budget plan with the account's name already exists, the account is put in that plan and no new one is made.