Integrations

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.

View Integrations

1. Click All Clients and select a client.

2. Go to Setup > Integrations and Apps.

   Note

   The Integrations and Apps user interface is not available at the service provider user level.
   
   The AVAILABLE INTEGRATIONS AND APPS page is displayed.
   
   • This page is visible to the users who have not installed any integrations, yet.

   

Install an Integration

To install an integration from:

AVAILABLE APPS

1. From the AVAILABLE APPS page, click +Add and select an app from the list. You can also search for the apps category wise and select from the results.

   

   
   
2. Click Add on the app card and follow the instructions on the screen.

INSTALLED APPS

1. From the INSTALLED APPS page, select an app from the list.

   

   
   
2. Click + ACCOUNT on the app card and follow the instructions on the screen.

Notes

• The + ACCOUNT on the card indicates that multiple integrations can be created.
• If the + ACCOUNT is not present on the card, it indicates that multiple integrations cannot be created.
  For example, the Linux Patch Feed and Windows Patch Feed apps as seen in the Installed Apps 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:

• Account - Name of the account.
• Added On - Date and time details of the added account.
• Added By - Information about the user who added the account.
• Status - Status of the account. Available only for some accounts.
• Enabled - Indicates whether the integration is enabled or disabled. Available only for some accounts.
  

The following actions can be performed from an app:
Actions

• Edit - Allows you to edit the integration.

• Uninstall - Allows you to uninstall the integration. Mention the reason for uninstalling the integration and click Uninstall.

• Rescan - Allows you to rescan the resource.
  The Rescan option is present only for the integrations that have discovery profiles available such as public cloud integrations.

  

  Note

  Uninstalling the integration cannot be reversed. Once uninstalled, the metrics, resources, alerts, and incidents related to that particular integration are impacted.

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:

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

   • Version - Displays the version details of the integration.

   • 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.

   

   • The following options are available in the three dots:
     • Edit: To edit an integration, click this button.
     • Copy Id: To copy an integration id, click this button.
     • Uninstall: To uninstall an integration, click this button.

Edit an integration

1. Click Edit from the three dots or click the name of the integration. 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.

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.

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 this button.
• Remove: To remove a configuration, click this button.
• Discover: To discover a configuration, click this button.

Edit a configuration

1. Click Edit from the three dot menu of a configuration.

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

   Notes:

   • You may also uninstall multiple configurations at the same time. Select configurations from the list in the Edit page and click UNINSTALL at the top right.
   • You may also add a new configuration from the Edit 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 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 under the Discovery status column.

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.

Example: Concatenate and Substring under Functions attribute of placeholders help to define the entity types. If you want to create an incident:

• using Concatenate, add two strings in the same string. For example, Subject and IncidentID.
• using Substring, add a delimiter to the main string. For example, add end to the existing string.

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 the event log information.