Creating an extended integration for GCP disks

Integrate Google Cloud with Oomnitza to gain visibility of information about persistent disks across multiple zones within a single project. Information about each disk such as the disk name, project, capacity, status, and zone is synced with Oomnitza.

This integration offers the flexibility to specify multiple GCP zones, ensuring a comprehensive aggregation of persistent disks across different zones.

Create workflows to automate complex tasks and business processes. Surface key information in operational dashboards and create scheduled reports to share knowledge with your colleagues.

Navigation

Create the asset integration

Custom mappings

Before you start

You will need to have the following information to hand when creating the integration in Oomnitza:

1. Your Google Cloud instance Project ID

The Project ID is case sensitive, so please make sure you have the correct spelling with upper and lower case characters or else the integration will fail with a not authorized message.

2. Your Google Cloud instance Zones

Specify multiple zones in each integration to enable comprehensive aggregation of data across different zones. Google Cloud zones are distinct locations within a region, designed to be insulated from failures in other zones, enhancing reliability and uptime. For example, the 'europe-west1' region includes zones like 'europe-west1-b', 'europe-west1-c', and 'europe-west1-d'. To identify which zones are available in your region, you can use the Google Cloud Console, the Google API, or the gcloud command line. For detailed guidance, refer to the Google Cloud Documentation View available regions and zones.

3. Your Google credentials

You will be prompted to enter your Google Cloud Client ID, Secret, and scopes before you run the integration. For information on credentials see, Google (OAuth 2.0) credentials.

Ensure that you use the following scopes when working with this integration:

• https://www.googleapis.com/auth/compute.readonly
• https://www.googleapis.com/auth/compute 
• https://www.googleapis.com/auth/cloud-platform 

For further information, refer to Google Cloud Documentation: List Disks

Creating the asset integration

1. In Oomnitza, click Configuration> Integrations> Overview.
2. Click Block view
3. Scroll down to the Extended section for asset integrations.
4. Click NEW INTEGRATION.
5. Select the integration in the sidebar.
6. Click ADD.

Integration details overview

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

Installation type

Select Cloud if you want to store credentials in the Oomnitza cloud.

Select Local if you want to store credentials locally. Local extended integrations do not support AWS and OAuth authentication. If you want to sync Oomnitza with vendor applications that require AWS or OAUTH authentication, select Cloud.

Integration preferences

By default, the option Create & Update option is selected. Select this option  when you want to edit records and add new records. If you want to edit records and not add new records, select Update Only. If you only want to add new records, select Create Only.

Integration details

To review or update the integrations details, click Edit .

1. Update the integration name if necessary. 
2. Select an installation type.
3. For integration preferences, select an option.
4. Enter the name of the integration user.

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

Schedule

By default, 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. Click the Edit .
2. Configure your schedule.
3. Click Update.

Mappings

To map the fields to Oomnitza, click Edit .

You can define rules for your integration by selecting Edit integration on the mapping page. For example, you may only want to run the integration if a certain contact or region exists. See Filtering integration results.  
You can add new fields to your integration by selecting Add new field   on the mapping page. All you need to do is specify the property name. See Creating custom API fields. 

Creating custom mappings

Map the Google Cloud disk asset fields to Oomnitza fields and create custom mappings to get the asset information that you need.

Complete these 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. Create a custom mapping for the ID. The ID is a unique identifier for the disk resource; defined by the server. Complete the following steps:
   1. Click the down arrow on the ID field.
   2. Select Add new Oomnitza field.
   3. Change the name of the field to Google Disk Asset ID.
   4. Select the Unique checkbox.
   5. Click CREATE. 
3. Create a custom mapping for the Zone. This will help you identify the zone associated with each asset. Complete the following steps:
   1. Click the down arrow on the Zone field.
   2. Select Add new Oomnitza field.
   3. Change the name of the field to GCP Zone.
   4. Click CREATE. 
4. Map and assign a sync key to a unique field, such as the Google Disk Asset ID.
5. Click UPDATE. 

Tracking information for asset loads 

When the integration is run, you can track the name of the credentials that were used and the source of the data. To do this, you map the following fields to Oomnitza:   

• Connect: Credentials
• Connect: Project
• Connect: Zone

Standard Google Cloud disk asset to Oomnitza User Load mappings

Connector Sync Time
Creation Timestamp
Description
ID
Name
Project
Size in GB
Status
Zone

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