Creating an extended integration for New Relic users (REST API)

Integrate New Relic with Oomnitza to gain visibility of users and SaaS user information.

Sync key information such as personal details and user’s role with Oomnitza. To monitor SaaS usage, use the integration point to retrieve SaaS roles, or last activity, or both. You can also use the integration point to create a data-hygiene workflow to deactivate the SaaS records in Oomnitza that were removed from the SaaS application. Then, you can delete the records in Oomnitza.

Create workflows that use Oomnitza integration points such as deleting user accounts and getting a user’s details to automate complex tasks and business processes. Surface key information in operational dashboards and create scheduled reports to share knowledge with your colleagues

This integration leverages the REST API. For further information, see New Relic Docs: REST API v2. To use GraphQL to query data, refer to the New Relic users (NerdGraph API). 

Before you start

To stream New Relic user data into Oomnitza, you need to have added your New Relic API credentials to Oomnitza.

You also need to have your API domain to hand to create the user integration in Oomnitza. Your API domain will vary depending on where your account was created, for example api.newrelic for US accounts, or api.eu.newrelic for EU accounts.

Creating a user integration

1. In Oomnitza, click Configuration > Integrations > Overview.
2. Click Block view .
3. On the Integrations page, scroll down to the Extended section for user integrations.
4. Click NEW INTEGRATION.
5. In the sidebar, search for the integration.
6. Click ADD.

Integration details overview

More information is provided about the following fields to help you complete the integration:

• User only. Add user records.
• User plus SaaS user. Add user and SaaS user records. 

The benefit of adding SaaS user records is that you can run a workflow to validate the status and activity of SaaS users and retrieve information such as the role of the SaaS user. The information that can be retrieved depends on whether SaaS user workflows are available for the integration. 

Installation types

• Cloud. Store credentials in the Oomnitza cloud.
• Local. Store credentials locally. If you want to sync Oomnitza with vendor applications that require AWS or OAUTH authentication, select cloud as the type of installation. Local installations don't support AWS and OAuth authentication. 

Integration preferences

• Create & Update. Add and update records.
• Create only. Add records.
• Update only. Update records.

Editing the integration details

1. Click Edit .
2. Make your changes.

Editing the credential details

If you selected Cloud as the installation type, choose one of the following options:

• Select the credentials that were created for the integration.
• Edit the credentials that were created for the integration.
• Create new credentials

Scheduling the integration

By default, data is synced once every day. Change the interval or the time so that the data is streamed when your system isn't busy.

1. Click Edit .
2. Make and save your changes.

Mapping fields to Oomnitza

To map the fields to Oomnitza, click Edit .

  Selecting Edit integration to add rules for syncing data. Filtering integration results.  
 

You can add new fields to your integration by selecting Add new field   on the mapping page. 
Creating custom API fields. 

Creating custom mappings

Map the New Relic fields to Oomnitza fields and create custom mappings to get the user information that you need.

To take advantage of workflows, ensure you map the following New Relic fields to Oomnitza:

Complete the following actions:

1. Click Smart Mapping to automatically detect appropriate mapping fields. Values from the integration can also be dragged to the appropriate field on the Oomnitza side, or selected from the integration field dropdown.
2. You must create a custom mapping for the New Relic Id field. To do this, complete these steps:
   1. Click the down arrow on the Id field.
   2. Select Add new Oomnitza users field.
   3. Change the name of the new field to New Relic User Id. 
   4. Select the Unique checkbox.
   5. Click CREATE. 
3. Ensure that the Email is mapped to the
   1. Username field on the Oomnitza side (required for integration).
   2. Email field on the Oomnitza side (required for integration).
4. Select the Role field on the Oomnitza mapping side.
5. Choose a suitable role from the list (a defined role is necessary for the integration)
6. Assign a sync key to a unique field, such as the Email.
7. Click UPDATE.

Standard New Relic to Oomnitza mappings

The following New Relic fields can be mapped to Oomnitza: 

Connector Synch Time
Email
Id
First Name
Last Name
Role

Ensure that you select one of the fields as the Sync Key such as the email address of the user. 

Launching the integration

Your integration is in Draft mode until the required mandatory fields are added. When added, click Launch to activate your integration. 

If you selected Cloud as the installation type when creating the integration, see Running an extended integration

If you selected Local as the installation type when creating the integration, see Running an extended integration locally.

Viewing data ingested by Oomnitza

Viewing ingested asset data

For asset integrations, click Hardware. If the asset integration also ingests software data, click Software.

Viewing ingested user data

For user integrations, click People. If you chose the option to ingest User and SaaS user data, click Software > SaaS, click the SaaS app, and then click the Users tab. 

Related Links

• Running an extended integration
• Troubleshooting integrations
• Mapping extended integrations

Unleash the power of Oomnitza

To get valuable actionable insights that help you manage your assets, learn how to:

• Configure dashboards for your assets and users
• Create asset and user workflows to automate tasks
• Configure custom reports about your assets and users

Next steps

Creating workflows for New Relic assets and users