Let Oomnitza be your single source of truth!
You'll get visibility of your assets and users as data from New Relic is automatically transformed into consumable information and actionable insights.
Connect Oomnitza and New Relic in minutes
You'll get visibility of your New Relic users by creating configurable workflows to automate tasks such as:
-
- Workflows for getting device details
- Workflows for deleting devices
- Workflows for getting a user's details
- Workflows for getting a user's role and deactivating users
Content
Before you start
Before you create the workflows, you must add your New Relic API credentials to Oomnitza.
It is recommended that you create the extended integration for New Relic users and the extended integration for New Relic assets. You can use the information retrieved in these integrations to trigger workflows that can delete devices, get user details, and much more.
Create asset workflows
To create an asset workflow, you must select credentials and enter the New Relic API domain.
To choose a preset, complete these steps:
- Click Configuration > Workflows
- Click Add (+) and select Assets from the list.
- Drag and drop the API block onto the Sandbox.
- Click Edit on the API block and enter New Relic in the search field.
- Select a preset:
- To choose a preset, click the forward arrow (>).
- Configure the API Block following the preset instructions below, and save your changes.
- Edit the Begin Block and add rules to trigger the workflow. For example, if you set the Actions to New you can trigger a workflow every time a new asset is created. Refer to Using the Begin block.
- Connect the Blocks.
- Save, validate, and activate your workflow.
Using the Delete Device preset
The Delete Device preset enables you to delete a device, using a New Relic Device ID. When you select this preset you need to supply your New Relic API Domain, for example api.newrelic
or api.eu.newrelic
. You can configure the message payload by selecting Advanced Mode.
- In the API block window, click the Advanced Mode button located in the upper right of the window.
- Select the Information tab. You will notice that the New Relic Device ID is referenced in the property
{{new_relic_device_id}}
.You can map the Device ID to this field by creating an asset integration and following the mapping steps in Creating custom mappings, otherwise you can enter the Device ID instead. - Select the Response tab. Map the Response field
{{response}}
to a custom Oomnitza field. You can create a custom field by following the steps in Creating custom fields.
Using the Get Device Details preset
The Get Device Details preset enables you to fetch a device's details, using a New Relic Device ID. When you select this preset you need to supply your New Relic API Domain, for example api.newrelic
or api.eu.newrelic
. You can configure the message payload by selecting Advanced Mode.
- In the API block window, click the Advanced Mode button located in the upper right of the window.
- Select the Information tab. You will notice that the New Relic Device ID is referenced in the property
{{new_relic_device_id}}
. You can map the Device ID to this field by creating an asset integration and following the mapping steps in Creating custom mappings, otherwise you can enter the Device ID instead. - Select the Response tab. Map the Response field
{{response}}
to a custom Oomnitza field. You can create a custom field by following the steps in Creating custom fields.
Create user workflows
To create user workflows, you must select credentials and enter the New Relic API domain.
To choose a preset, complete these steps:
- Click Configuration > Workflows.
- Click Add (+) and select Users from the Objects list.
- Drag and drop the API block onto the Sandbox.
- Click Edit on the API block and enter New Relic in the search field.
- Select a preset:
- To choose a preset, click the forward arrow (>).
- Configure the API Block following the preset instructions below, and save your changes.
- Edit the Begin Block and add rules to trigger the workflow. For example, if you set the Actions to Schedule and add a rule so that the Email Equals <EmployeeEmail> you can trigger a workflow to fetch a user matching a certain name on a specific date. Refer to Using the Begin block.
- Connect the Blocks.
- Save, validate, and activate your workflow.
Using the Get User Details preset
The Get User Details preset enables you to retrieve a single user by their New Relic User ID. When you select this preset you need to supply your New Relic API Domain, for example api.newrelic
or api.eu.newrelic
. You can configure the message payload by selecting Advanced Mode.
- In the API block window, click the Advanced Mode button located in the upper right of the window.
- Select the Information tab. You will notice that the New Relic User ID is referenced in the property
{{new_relic_user_id}}
. You can map the User ID to this field by creating a user integration and following the mapping steps in Creating custom mappings, otherwise you can enter the User ID instead. - Select the Response tab. Map the Response field
{{response}}
to a custom Oomnitza field. You can create a custom field by following the steps in Creating custom fields.
Using the Delete User preset
The Delete User preset enables you to delete a user by their New Relic User ID. When you select this preset you need to supply your:
New Relic API Domain: For example api.newrelic
or api.eu.newrelic
.
New Relic Partner ID: To obtain your Partner ID, go to your partner admin console and retrieve the partner ID number that is listed in your URL: https://partner-admin-console.newrelic.com/accounts/$ACCOUNT_ID/admin_console/partnerships/$PARTNER_ID
New Relic Account ID: To obtain your Account ID, go to your partner admin console and retrieve the account ID that is listed in your URL: https://partner-admin-console.newrelic.com/accounts/$ACCOUNT_ID/admin_console/partnerships/$PARTNER_ID
For further information, refer to the New Relic Documentation: Find your Partner ID.
You can configure the message payload by selecting Advanced Mode.
- In the API block window, click the Advanced Mode button located in the upper right of the window.
- Select the Information tab. You will notice that the New Relic User ID is referenced in the property
{{new_relic_user_id}}
.You can map the User ID to this field by creating a user integration and following the mapping steps in Creating custom mappings, otherwise you can enter the User ID instead. - Select the Response tab. Map the Response field
{{response}}
to a custom Oomnitza field. You can create a custom field by following the steps in Creating custom fields.
Reference articles for workflows
Create SaaS user workflows
The SaaS user role workflow allows you to read a SaaS user’s role from New Relic.
Prerequisites
Before you create a SaaS user workflow, you should have already run your extended user integration and selected User plus SaaS User to populate the software entry in the Software > SaaS menu.
To create a Saas User workflow using the New Relic User Role preset, complete the following steps:
- Click Configuration > Workflows
- Click Add (+) and select Software SaaS Users from the list.
- Enter the name and a description of the workflow.
- Edit the Begin block by adding the rules that will trigger the workflow. For further information see SaaS User Roles.
- Click the Blocks tab, and drag and drop the SaaS User Role retrieval block onto the canvas.
- Click the Edit icon.
- Enter New Relic in the search field and choose the New Relic User Role preset.
- Click the right arrow >.
- Select your credentials.
- Select your New Relic API Domain. For example
api.newrelic
orapi.eu.newrelic
. - Select the Deactivate User checkbox to deactivate the SaaS user in SaaS > New Relic > Users if they are not found in your New Relic instance.
- Click SAVE
- Connect the blocks.
- Save, validate, and activate your workflow.
To view active New Relic users in the SaaS Users UI, complete the following steps:
- Click Software from the menu.
- Select the Saas tab, and select your software entry for New Relic.
- Click Users in the side pane.
- The Role column will be populated with the user details to confirm that this user has been found in your New Relic SaaS.
Comments
0 comments
Please sign in to leave a comment.