Integrations

Introduction

OpsRamp provides a common platform to integrate different tools and applications used by an organization and provides a single interface to view and monitor all the events arising out of the IT infrastructure.

The main objective of integration is to ingest and integrate third-party events. During the integration process, you can define the integration events that you want to monitor. Integration Events are configured for Monitoring and Collaboration integration types. Using the Outbound configuration, you can define the integration events.

OpsRamp categorizes the tools and applications that are used to generate and monitor the events of a resource in an IT infrastructure.

Following table displays the available Integration categories at Service Provider, Partner, and Client levels.

View Integrations

1. From All Clients, select a client.

2. Go to Setup > Account.

3. Select the Integrations and Apps tab.

   Note

   SP level users can install integrations by selecting All Partners > All Clients.
   
   

4. The Available Integrations and Apps page is displayed.
   

   Note: This page is visible to the users who have not installed any integrations, yet.

   

Install an Integration

To install an integration from the Available Integrations and Apps page:

1. Search for the application category wise and select from the results.

   

   
   
2. Click ADD on the application card and follow the instructions on the screen.

To install an integration from the Installed Integration page:

1. From the Installed Integrations page, search for the application you want to install, and select the application.
   
   Note: If the application is not available, click +ADD. The Available Integrations and Apps page is displayed. Follow the instructions mentioned in points 1 and 2 above, to install the integration.

   

   
   
2. Click +ADD on the application card and follow the instructions on the screen.

Notes

• The +ADD on the card indicates that multiple integrations can be created.
• If the +ADD is not present on the card, it indicates that multiple integrations cannot be created.
  For example, the Linux Patch Feed and Windows Patch Feed applications as seen in the Installed Applications page illustration.
• The count next to the user icon indicates the number of integrations that have already been installed.

View App Information

To view information about the app, click anywhere on the card. The options slide-out screen is expanded. To collapse the slide-out, click anywhere on the card.
The following information is available:

• Name - Name of the account.
• Version - Version of the App.
• Collector Profile - Name of the collector profile.
• Status - Status of the account. Available only for some accounts.
• Added On - Date and time details of the added account. Information about the user who added the account is also displayed.
• Updated On - Date and time details of the modified account. Information about the user who modified the account is also displayed.
• Enabled - Indicates whether the integration is enabled or disabled. Available only for some accounts.
  

Modify an Installed Integration or Application

1. Click the name of the integration or application. A list of installed integrations is displayed with the following information. These options are displayed based on the type of Integration or Application.

   • Name - Displays the name of the integration or application.

   • Version - Displays the version details of the integration. You can update the version by clicking the Update dropdown and selecting version.

   • Collector Profile - Displays the name of the collector profile.

   • Status - Displays the status of the collector profile. The status is a combination of both the gateway and application. For example, if the gateway status is up and the application status is installed, then the status is Running.

     Note: The following statuses are applicable to SNMP, Linux, and SDK integrations.

   Gateway Status	Application Status
   	Installed	Enabled
   Up	Running	Running
   Down	Stopped	Stopped
   Not Installed/Deployed/Registered	Configured	Configured

   • Added On - Displays the date and time details of the added integration or application. The user icon next to the time indicates the user who added the application.

   • Updated On - Displays the date and time details of the updated integration or application. The user icon next to the time indicates the user who modified the installed application. This information appears whenever an action is performed such as modifying discovery configuration, mapping attributes, or inbound/outbound events.

   

Actions on integration

Following are the actions you can perform on an integration:

• Click the action (three dots) menu against each integration, to view the following options. These options are displayed based on the type of integration or Application:

  • View resources: To view the resources discovered by selected integration instance, click this button.
  • Edit: To modify or edit an integration, click this option.
  • Copy Id: To copy an integration id, click this option.
  • Uninstall: To uninstall an integration, click this option.
    Note: Uninstalling the integration cannot be reversed. Once uninstalled, the metrics, resources, alerts, and incidents related to that particular integration are impacted.
  • Rescan: Click this option to discover the resources. The Rescan option is present only for the integrations that have discovery profiles available such as public cloud integrations.
  • Export and Import: This option allows you to export and import integrations from one client under a partner to another client under the same partner or a different partner.
  • Export OIDs: This option allows you to export OIDs in JSON format.
  • View Logs: View logs for the integration.
  • Assign template: Assign template to monitor integration failures.
  • Monitoring of Integration: Assign a template from the Monitoring of Integration tab, if you want to monitor integration failures.

  

View Resources

1. Click the View resources from the three dots.
2. The Infrastructure Search appears with related resources of integration instance.

Note: See Related Resources for more details.

Edit an Integration

1. Click Edit from the three dots or click on the name of the integration. Based on the type of integration, the page is displayed to modify.
   Example: For integrations like SNMP, the Configurations page is displayed with a list of available configurations specific to the selected integration.
2. Click the three dots available for the configuration and click Edit.
3. In the Edit Configuration window that appears, edit the configuration and click Update.
4. Click Done.

Copy an Integration Id

Click the three dots available for the integration and click Copy Id. The integration id is copied.

Uninstall an Integration

1. Click the three dots available for the integration and click Uninstall.

2. In the Uninstall Integration window that appears, mention the reason for uninstalling and click UNINSTALL. The configuration is uninstalled.

   Note: When you uninstall an integration, the resources associated with all configurations are also deleted.

Rescan

Click the rescan option from the action (three dots) menu. The resources are discovered. The scan requested date and time and the last scanned date and time are also shown.

Export and Import

You can export and then import an integration from one client to another.

To export:

1. Click the action menu (three dots) against the integration and click Export to download the JSON file on to your computer. This file has all the data related to the integration.

You can now import the downloaded JSON file.

To import:

1. Click the import icon available at the upper-right corner of the page.
2. Click Upload File from the popup window.
3. Select the JSON file.
4. Click Open and then click Import. The integration is imported.

Note: You can import an integration into another client under the same partner or select another partner and a client.

Export OIDs

You can export OIDs in JSON format.

To export:

1. Click the action menu (three dots) against the integration and select Export OIDs to download the JSON file on to your computer. This file has the OIDs separated by commas.

View Logs

You can view logs for the integration.

Follow these steps to view the logs:

1. Click on the Actions (three dots) icon for the integration and click on View Logs.
2. The logs information is displayed on the View Logs window.
   • Switch between the Outbound/Inbound logs by clicking on the down arrow available at the top right corner.
   • Use the Filter option to filter the logs based on Created Time and Status.

Assign Template

You can assign templates to the integration for monitoring the integration failures.

See monitoring integration failures for more information.

Modify a Configuration

Configurations are available for each integration. The following actions can be performed on the configurations from the three dots next to each configuration:

• Edit: To edit a configuration, click Edit.
• Remove: To remove a configuration, click Remove.
• Discover: To discover the resources, click Discover.

Edit a Configuration

1. Click Edit from the three dot menu icon against a configuration.

2. From the Edit Configuration window, edit the configuration and click Update.

   Notes:

   • You can change the collector profile. To do this, click Change, select the collector profile from the dropdown, and click Update. The collector profile is updated successfully. This is applicable for all discovery related apps.
   • You may also uninstall multiple configurations at the same time. Select configurations from the list from the Edit Configuration page and click Uninstall at the top right.
   • You may also add a new configuration from the Edit Configuration page by clicking +Add.

Remove a Configuration

1. Click Remove from the three dots of a configuration that you want to remove. A confirmation message appears.

2. Click Delete to remove the configuration. Click Cancel to go back.

   Note: When you remove a configuration, the resources and the related metrics associated with that configuration are also deleted.

Discover a Configuration

• Click the three dots available for the configuration and click Discover. A discovery is initiated and the status is displayed in the Discovery status column.

The number of devices that are discovered are displayed in the Devices column.

• Click the hyperlink to view the discovered devices.

Other Details like Name, Discovery status, Last discovery time, UID and Enabled are displayed.

• Name: Name of the configuration.
• Discovery status: Status of the discovery like Completed, Queued and
  In Progress.
• Last discovery time: The last discovery date and time.
• UID: Configuration UID.
• Enabled: Enable or disable the configuration. When it is Disabled, discovery does not happen.

Note: The above columns vary based on the integration.

Assign Templates

You can assign templates to the devices.

To assign templates:

1. Click the hyperlink in the Devices column to view the discovered devices.
2. Click the resource name.
3. From the slide-out, click the three dots available at the upper-right corner.
4. Click View details. The resource details page is displayed.
5. From the monitors tab, assign the templates.

You can view graphs from the Metrics tab.

The device states are also shown in the resources listing page.

Discovered: The Discovered state is shown if a device is only discovered.

Active: The Active state is shown if a device is managed.

Client and Partner Integrations

Clients and partners can directly install and configure integrations. However, clients and partners have different access:

• Clients can install all the supported integrations.

• Clients can edit integration configurations installed directly by a partner.

  • Every modification creates a separate copy for the client.
    • After modification, the partner configuration does not apply to the client for the modified configuration.

• Partners can install only some of the integrations for clients (for example, monitoring and collaboration).

• Custom Integration is an exception where while assigning integration to every client, providing configuration details for every client is required.

Multiple Client Integration

Partners can install and configure an integration without selecting a client and apply the same configuration to multiple clients selecting one client at a time. As a result, multiple clients can be assigned the installed and configured integration without repeating the same effort.

In the following scenario, a partner has six clients and wants to install a collaboration integration with the same configuration for five clients, but a different configuration for the sixth client.

Solution: A partner performs the following steps:

1. Install and configure the integration without selecting a client.
2. Select the name of one client.
3. Search for the configured integration by name and click to open the integration.
4. Then, from that integration screen, click the Install button. A click Install takes care of both installation and configuration.
5. Repeat steps 2-4 for the other four clients. All five clients get integration installed with the same configuration.
6. Repeat steps 2-4 for the sixth client.
7. Change the configuration. The sixth client receives the same installed integration but with a different configuration.

Authentication Type

OpsRamp uses the following industry-standard authentication types to establish a connection between OpsRamp Platform and the third-party tools:

• OAuth 2.0:

  • OAuth 2.0 is a protocol that allows an application to authenticate against the server as a user.
    • OAuth 2.0 relies on HTTPS for security and provides secured delegate access to a resource based on the user.
    • OAuth 2.0 provides security by allowing a token to be issued by the Identity Provider to these third-party applications, with the approval of the user. The client then uses the token to access the resource on behalf of that user.

• Webhook:

  • Webhook is a token-based REST API.
    • Webhook enables third-party services to send real-time updates to OpsRamp.
    • Updates are triggered by some event or action by the Webhook provider and pushed to OpsRamp using HTTP requests. When OpsRamp receives the request and handles with some custom logic, like sending an email or storing the data in a database.

Connection Direction

After the connection is established using the authentication type, you need to define the direction of the integration between OpsRamp platform and the third-party tool. OpsRamp supports the bi-directional flow of information between the third-party tool and OpsRamp.

OpsRamp supports the following types of integration directions:

Select the Integration Direction depending on the integration category.

Attribute Maps

The attributes or properties of the third-party tool and OpsRamp are not uniform in nature. They differ in their naming structure and format. To have a uniform structure and to process the information exchange, you need to map the attributes of a third-party tool with those of OpsRamp. Depending on the type of integration, OpsRamp supports an extensive list of attributes and properties which can be configured/mapped as per the requirements.

Once the attributes are mapped, OpsRamp processes the information received from the third-party tool and displays them in the portal.

For some webhook-based Integration, default attributes are already configured during installation. You do not need to map attributes manually. For example, Pingdom, Stackdriver, New Relic, OMS,

Integration Events

The main objective of integration is to ingest and integrate third-party events into OpsRamp. During the integration process, you can define the integration events that you want OpsRamp to monitor. Integration Events are configured for Monitoring and Collaboration integration types. Using the Outbound configuration, you can define the Integration Events.

OpsRamp supports creating/adding integration events for ServiceDesk and Resource entities. For each of these entities, you can define the required entity types and for each entity type, you can define an entity type event. For every event, placeholders are defined. You can select these placeholders (attributes) for the API payload.

For integrations that support outbound events, like Custom, Ticketing, and Custom (Ticketing) integrations, use placeholders in the following fields:

• Endpoint URL
• Payload
• Attachment endpoint URL
• Attachment payload

How to use: To add a placeholder in a field, type ‘$’ and select the placeholder. If you want to append a placeholder to an existing string, give a space after the string and type ‘$’.
Remove the unwanted spaces.

Examples:

1. To concatenate two or more strings using the ConcatenateStrings function.
   • Add subject and incidentId in the start and end strings of Concatenate string.
     $utils.concatenateStrings($incident.subject,$incident.uniqueId)
     
     
2. To create an incident with a substring:
   • Add an end delimiter to the main string.
     $utils.substring(<String>,<startDelimiter>,<endDelimiter>)

Note: Based on entity type values, the placeholder tokens change.

Monitoring

All the events getting ingested from the third-party tool into OpsRamp are monitored based on predefined metrics created by OpsRamp. The related metrics are grouped into a monitor and monitors are grouped to create a template. The created template is applied to a selected resource or uses integration to monitor the events arising from the third-party tool.

Audit Logs

OpsRamp captures all the communication events happening between the third-party tool and OpsRamp platform.

Log information provides payloads events and their corresponding status.

You can view audit log information for the following integration categories:

• Events
• Ticketing
• Custom
• OS Patching
• SSO

To view the audit logs:

1. Click the menu (three dots) icon at the upper-right corner of the Installed Integrations screen.
2. Select Audit Logs. The View Logs window displays the Outbound and Inbound log information of all the installed integrations.
   Note: Event, SSO, OS patching have only Inbound logs.
   
   The logs are displayed with Request URL, Event Name, Processed Time, Status, Status Message, Entity Id, Request Payload, Response Payload details.

• Select from the dropdown to view the Outbound and Inbound logs.
• Use the Filter dropdown to filter the logs by Created Time, Status, and/or Entity Id.
  
  

Outbound event configuration

In all Ticketing (collaboration) applications, when Events are configured in Outbound integrations, if the outbound payload contains any integer values, they are sent as string, by default, to the third party. That is, integer values are enclosed in quotes.

To normalize the integer values in the Outbound payloads, a header is added in the Headers section.

Configure the header as follows:

• Select the Key as Normalize_payload_datatype and the Value as true and save it.

The strings (the integer values within double quotes) are automatically sent as integer values.

Example:
The below image shows the newly added header and the value:

• Header: Normalize_payload_datatype
• Value: true

Call-outs #1 and #2 show entity_id and status values as strings. These are sent to the third party without quotes.

Custom integrations

The Custom integration that was previously available with five categories in it is now split as separate integrations for each category. Click the links to navigate to the respective integration:

• Custom
• Custom (Ticketing)
• Custom (Events)
• Custom (SSO)
• Custom (Process Automation)