Creating an extended integration for PagerDuty users

Let Oomnitza be your single source of truth!

You'll get complete visibility of SaaS account activity in PagerDuty as data is automatically transformed into consumable information and actionable insights.

Connect Oomnitza and PagerDuty in minutes

Get the information and insights that you need to reduce costs and the time that you spend on administration tasks such as:

• Configurable dashboards and list views of key user information
• Configurable workflows that you can create:
• For reducing costs by deactivating the accounts of users that aren’t listed by PagerDuty
• For deleting the SaaS accounts of inactive users, or employees who have left the company, or employees whose role doesn’t entitle them to access the SaaS platform
• Configurable reports to share information about users with your colleagues and management

Navigation

Before you start

Updating the credentials

Creating the user integration

Creating custom mappings

Deactivate SaaS users in Oomnitza

Delete PagerDuty users 

Before you start

Best practice
For the integration with Oomnitza, create a dedicated user account.

Before you can configure any of the available integrations with PagerDuty, you need to follow the steps in Updating the credentials. PagerDuty requires an API key for authorization.

When entering the API key, you must ensure that you put the word Token token= before the key you generated when Updating the credentials in Oomnitza. Only account administrators have the ability to generate account API tokens. To find our more about the PagerDuty API refer to the PagerDuty API documentation links below.

PagerDuty API documentation

Generating API keys

Authentication 

Tip
Keep a copy of the API key. You need it when you add your credentials to the Oomnitza vault.

Updating the credentials

To authorize connections between Oomnitza and PagerDuty, complete these steps:

1. Log into Oomnitza.
2. Click Settings > Credentials, and then click Add new credential (+).
3. Add the information details.
4. Click the AUTHORIZATION tab.
5. As authorization type select API Key.
6. Enter Authorization as the name of the token. 
7. Enter Token token= followed by a space and the API Key. For example, Token token=y_NbAkKc66ryYTWUXYEu.
8. Ensure that Add to Header is selected.
9. Click CREATE. 

Next step

You use the credentials that you added to create and customize your PagerDuty integration with Oomnitza.

Creating the user integration

1. From the menu, click Settings.
2. On the Integrations page, scroll down to the Extended section for User Integrations.
3. Click NEW INTEGRATION.
4. In the New User Integration sidebar, click PagerDuty.
5. To integrate Oomnitza with the PagerDuty User Load, click APPLY and then click NEXT twice.

Connect page

Best practice
To ensure that only live user records are streamed from PagerDuty to Oomnitza, choose Update only as your integration preference. When you run the integration, you can check the error logs to see which user records weren't uploaded and why they weren't uploaded. You can then decide whether to upload the user records that were skipped by changing your integration preference to create and upload. See How to access error logs.

1. Enter a descriptive name for the integration such as PagerDuty Users. That'll be the name of the user integration tile that is shown on the Integrations page.
2. From the User Selection list, select User only.
3. From the installation type list, select Cloud.
4. From the Credentials list, select the credentials from the Oomnitza vault.
5. From the Integration Preferences list, select Update only.   
6. Enter the name of the user of the integration.
7. Click Next.

Next step

Map PagerDuty fields to Oomnitza fields and create a sync key.

Creating custom mappings

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

Try it out!
Click the down arrow in the field that you want to map to Oomnitza.  Select Add new Oomnitza users field. Replace the name with a user-friendly label, and click CREATE.

Standard PagerDuty to Oomnitza mappings

The following PagerDuty fields can be mapped to Oomnitza: 

• Id. The user id which is used to uniquely identify a user in PagerDuty.
• Name. The user's full name
• Email. The email of the user. It can be mapped to the email or username field in Oomnitza.
• Role
• Type
• Invitation sent?
• Connector Sync Time. The current date and time stamp when the connector was run.

Want to map more fields to Oomnitza?
Contact Support, or see Mapping extended connectors.

When you've completed mapping PagerDuty fields to Oomnitza fields, click NEXT.   

Schedule

By default, PagerDuty user data is streamed to Oomnitza once every day.

You can configure the schedule to meet your needs such as changing the interval or changing the time so that the data is streamed when your system isn't busy.

1. Configure your schedule.
2. Click FINISH.

Result

A new tile is created for the integration on the Integrations page. 

What to do next

If you want to see what information is collected now, click the tile on the Integrations page and click RUN.

Figure: Mock-up for illustration purposes

If you want to change the integration settings, you can click a navigation link on the page, such as 4 Mappings, and edit the settings. 

Deactivate SaaS users in Oomnitza

You can add the SaaS User role retrieval block to a workflow to read the user’s role in PagerDuty and deactivate SaaS users in Oomnitza.

Add the SaaS User role retrieval for PagerDuty

1. From the menu, select Software.
2. From the Workflows list, select SaaS Users.
3. To add a new workflow, click +.
4. Enter the name of the workflow and a description, and then click Add new.
5. Drag and drop the SaaS User Role retrieval block in the sandbox.
6. Click Edit, and enter PagerDuty as the search criteria.
7. Click the right arrow next to the PagerDuty User Role API.
8. Select the credentials that you created for PagerDuty.
9. Ensure the Deactivate User checkbox is selected.
10. Click Save.

Next

You edit the Begin block, add a schedule, and the rules that trigger the workflow. You also must link the blocks together and validate, launch, and save the workflow.

Understanding workflows

Result

When the workflow is run, the SaaS user is deactivated in Oomnitza if the user isn’t found in your PagerDuty instance.

Delete PagerDuty users 

You can add the API block to a workflow to delete users in PagerDuty.

Add the API block for PagerDuty

1. From the menu, select Software.
2. From the Workflows list, select SaaS Users.
3. To add a new workflow, click +.
4. Enter the name of the workflow and a description, and then click Add new.
5. Drag and drop the API block in the sandbox.
6. Click Edit, and enter PagerDuty as the search criteria.
7. Click the right arrow next to PagerDuty Delete User.
8. Select the credentials that you created for PagerDuty.
9. Click SAVE.

Next

You edit the Begin block, add a schedule, and the rules that trigger the workflow. You also must link the blocks together and validate, launch, and save the workflow.

Understanding workflows

Result

When the workflow is run, the user is deleted in PagerDuty.

Unleash the power of Oomnitza

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

• Configure dashboards for your assets
• Configure custom reports
• Configure workflows for automating complex and repetitive tasks

See Getting started