Creating an extended integration for Puppet assets

Let Oomnitza be your single source of truth!

Choose from two Puppet asset integrations in Oomnitza to gain complete visibility of your assets as data from Puppet is automatically transformed into consumable information and actionable insights.

Puppet Node Asset Load: Uses the Puppet Node endpoint to return all nodes matching the given query. 

Puppet API Docs: Nodes endpoint

Puppet DMI Fact Asset Load: Uses the Puppet Facts endpoint to query DMI (Desktop Management Interface) facts using the 'certname' returned in the Node endpoint. 

Puppet API Docs: Facts endpoint

Connect Oomnitza and Puppet 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 asset and user information
• Configurable reports to share information about assets and users with your colleagues and management
• Configurable asset workflows that you can easily create for getting information about facts

Navigation

Creating the asset integration

Creating custom mappings

Creating asset workflows

Before you start

Before you can create the asset integration with Oomnitza, you will need the following:

Your Puppet API key

Puppet Token-based authentication

Your Puppet fully-qualified domain name, or FQDN

For example, if your URL is https://example.server.region.companyname.network:1234/path/to/resource, ensure that you:

• Ignore the leading https://.
• Enter only the domain and subdomain. 
• Disregard the paths or port numbers after the domain.

This means you only need to include example.server.region.companyname.network

Note
Integrations do not support self-signed certificates. Ensure that your domain has a valid certificate issued by a recognized certificate authority, otherwise you will encounter errors when running the integration.

Integration errors

Your Puppet Port

Your Puppet Port, such as 8081.

Tip
Add the FQDN and Port numbers as global variables. It’ll save you time when you create workflows. See Adding global settings. Add two new global settings called Puppet.Puppet Cloud Domain and Puppet.Puppet Port as keys and enter your actual FQDN and port as values.

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 Puppet fields to Oomnitza fields and create custom mappings to get the information that you need to manage your desktop assets.

Complete the following actions:

1. Click SMART MAPPING. The Connector Sync Time field is automatically mapped to Oomnitza.
2. Complete the following actions:
   1. On the Certname field, click the down arrow and map it to the Serial Number field.
   2. Select Serial Number as the sync key.
3. To map other Puppet fields to Oomnitza, complete these actions:
   1. Click the down arrow on the field.
   2. Select Add new Oomnitza assets field.
   3. Change the label name to a shorter user-friendly name.
   4. Click CREATE.
4. Click UPDATE.   

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

Puppet Node Asset Load to Oomnitza field mappings

The following Puppet fields can be mapped to Oomnitza: 

Cached Catalog Status
Catalog Environment
Catalog Timestamp
Certname
Connector Sync Time
Deactivated
Expired
Facts Environment
Facts Timestamp
Is Latest Report Corrective Change
Is Latest Report Noop
Is Latest Report Noop Pending
Latest Report Hash
Latest Report Job Id
Latest Report Status
Report Environment
Report Timestamp

Puppet DMI Fact Asset Load to Oomnitza field mappings

The following Puppet fields can be mapped to Oomnitza: 

Bios Release Date
Bios Vendor
Bios Version
Board Asset Tag
Board Manufacturer
Certname
Chassis Asset Tag
Chassis Type
Connect: Api FQDN
Connect: Api Port
Connect: Credentials
Connector Sync Time
Environment
Fact Name
Manufacturer
Product Name
Product Uuid
Serial Number
list_response_item

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

Use presets to create asset workflows

To reduce costs by automating repetitive and  complex tasks, take advantage of the built-in presets that Oomnitza provides.

To choose a preset, complete these steps:  

1. Click Configuration > Workflows 
2. Click Add (+) and select Assets from the list.
3. Drag and drop the API block onto the Sandbox.
4. Click Edit on the API block and enter Puppet in the search field. 
5. Select a preset:
   • Puppet Get Fact
   • Puppet Get Specific Facts
6. Click >, configure the API Block, and save your changes.
7. To trigger the workflow, edit the Begin Block.
8. Connect the Blocks. 
9. Save, validate, and activate your workflow.

Reference articles for workflows

• Mapping positive and negative responses
• Troubleshooting workflows 
• Using the API block