Micro Focus Operations Manager i acts as a single pane of glass, allowing you to be in control of your IT environment. It enables you to automate continuous discovery and IT event monitoring so you can sense the state of IT resources and how it impacts your business. OpsRamp integration supports to accept events from OMi as alerts.

OpsRamp configuration

Configuration involves the following:

  1. Installing the integration.
  2. Configuring the integration.

Step 1: Install the integration

To install:

  1. Select a client from the All Clients list.
  2. Go to Setup > Integrations > Integrations.
  3. From Available Integrations, select Monitoring > Micro Focus Operations Manager i.
  4. Click Install.

Step 2: Configure the integration

To configure the integration:

  1. From the API tab, provide the following:
    • Authentication: Copy Tenant Id, Token and Webhook URL for configuration. These settings are used for creating a HTTP Request template.
    • Map Attributes: Provide the mapping information for the third-party.
  2. From the Monitoring of Integration tab, click Assign Templates.
  3. From the Audit Logs, set up audit log criteria and time frame.

Configuring the map attributes

To configure the mapping attributes:

  1. Select the required OpsRamp property from the drop-down.
  2. Click Add Mapping Attributes to map attributes for the specific OpsRamp alert property.
  3. Click + to define the mappings.
  4. From Create Alert Mappings on Status, define the mappings, parsing conditions, and default values, and Save.

The following tables shows the attribute mappings and a sample payload. The sample payload with OMi event details that appears in OpsRamp after the integration. Depending on the mapping of properties, data is displayed in OpsRamp.

Payload Descriptions
OMi payloadOMi AttributesOpsRamp Attributes
	"event": {
		"subject": "Memory utilization is high",
		"description": "Memory utilization is high",
		"createdTime": "2018-01-10 07:58:42",
		"receivedTime": "2018-01-10 07:58:42",
		"id": "13492360-f5dc-71e7-0c4e-ac1a6f660000",
		"ciInfo": {
			"ciId": "ed363fe71d376d23febcd5ee2938b51a",
			"ciName": "omi",
			"ciDNS": ""
		"category": "OS",
		"subCategory": "",
		"application": "a",
		"object": "o",
		"severity": "critical",
		"state": "open",
		"priority": "medium",
		"policyName": "opcmsg_test(1.0)"
event.idExternal Alert ID
event.severityAlert state
OMi Property ValueOpsRamp Property Value
event.subjectAlert subject
event.descriptionAlert description
event.createdTimeAlert time
event.category - $event.subCategoryAlert metric
event.ciInfo.ciNameAlert resource name

OMi configuration

The Connected Servers Manager is used to configure the target servers. These server receive forwarded events and subsequent event changes.

Configuration involves:

  1. Configuring the OpsRamp server.
  2. Configuring external event processing.
  3. Configuring event forwarding rules.

Step 1: Configure OpsRamp server

In this step, OpsRamp is configured as a target connected server in OMi Connected Servers Manager. OMi events and subsequent event changes are posted to OpsRamp.

To configure OpsRamp as a connected server:

  1. Log in to OMi.
  2. Go to Administration > Setup and Maintenance.
  3. From the Connected Servers pane, click the New Script icon to create new script and provide the following:
    • In General section:
      1. Display Name: Provide a name for the script. The script would be identified with this name. Example: OpsRamp Push Event Adapter.
      2. Description: Provide a summary describing the script. Example: Push OMi events to OpsRamp using groovy script.
      3. Click Next.
    • In the Script section: Provide the script and click Next.
      • Note: Use the Tenant ID and Token values from the OpsRamp comfiguration.
      • For example: /integrations/alertsWebhook/client_27/alerts?vtoken=wZjQ9V3CmGYXzmukLzPpQ6xzJVHEju5P
    • In the Advanced section: Provide the time-out as 60000 ms and click Finish.
OMi Script

OMi Script

Step 2: Configure external event processing

To configure the external event processing:

  1. Go to Administration > Setup and Maintenance.
  2. On the Connected Servers pane, click the New Script icon and then click External Event Processing.
    External Event Processing

    External Event Processing

  3. In the General section, provide the following:
    • Display Name: Provide a name for OpsRamp connected server.
    • Name: Provide a unique internal name. You can change the internal name if you want to change the automatically generated name.
    • Description: Provide a description of the connection.
    • Select Activate External Event Processing Server after creation and click Next.
      External Event Processing

      External Event Processing

  4. In Server Properties section, configure the following:
    • Fully Qualified DNS Name: Provide OpsRamp DNS name
    • CI Type: Select Management System from the drop-down.
    • Customize the way events and change notifications are delivered to OpsRamp server using Advanced Delivery Options, and then click Next.
      External Event Processing Server Properties

      External Event Processing Server Properties

  5. In Integration Type section, configure the below details:
    • Select Call Script Adapter, select the previously configured Script name from the drop-down.
    • Provide the time limit for execution of the script and click Next. Note: Default time limit is 60 seconds.
      External Event Processing Integration Type

      External Event Processing Integration Type

  6. In Outgoing Connection section, configure the following:
    • Provide port number as 443. The events are forwarded to OpsRamp server.
    • Select Use Secure HTTP, click Retrieve from Server to fetch OpsRamp certificate and click Next. Username and password are optional.
      External Event Processing Outgoing Connection

      External Event Processing Outgoing Connection

  7. In Event Drilldown section, configure the following:
    • Select Use Secure HTTP for secure communication and click Next.
  8. In Incoming Connection section, the username is auto-generated. Leave this section blank and click Finish.
External Event Processing Incoming Connection

External Event Processing Incoming Connection

Step 3: Configure event forwarding rules

Configure an event forwarding rule to determine which events are forwarded to OpsRamp connected server. Events matching with the rules are pushed to OpsRamp connected server along with the subsequent changes in the events. You can configure which events to forward based upon a filter, and to which connected server the events should be forwarded. You can configure filters in the Event Forwarding manager.

To configure event forwarding rules:

  1. Go to Administration > Event Processing.
  2. From Automation, click Event Forwarding and click the New Script icon to create a new event forwarding rule.
  3. In the General section, configure the following:
    • Name for the rule.
    • Rule description.
  4. In Condition section, configure the following:
    1. Click browse icon and select the filter. The filter determines which events to forward. For example, a filter can contain severity related attributes to forward only Critical or Major events.
    2. To create a new filter, configure the the following:
      1. Click the New Script icon and click New Simple Filter.
      2. Provide name for filter. Example: OpsRamp Push Events Forward Rule.
      3. Provide description of the filter.
      4. Configure General, Dates and Additional Event Properties as per your requirement.
      5. Click All events in Correlation section, and then click OK.
        The rule now appears in the Event Filter drop-down in Conditions section.
        Event Forwarding Rule Condition

        Event Forwarding Rule Condition

  5. In Target Servers section, configure the below details:
    1. Select the previously configured OpsRamp connected server from the drop-down.
    2. Click the Add multiple servers icon to view the target server details.
    3. Select Notify and Update in Forwarding Type drop-down and then click OK.
      Event Forwarding Rule

      Event Forwarding Rule