Use Case

Learn more about the use case.

  • Collect Violations from NewRelic to create new Events in OBM.

Requirements

Learn more about the integration and network requirements.

Integration Requirements


NewRelic Requirements

Operations Connector Requirements

Access Details

  • Instance URL

  • Instance URL

Authentication
  • API Key
  • N/A

Permissions

  • N/A
  • N/A

Environment

Network Requirements


Network Requirements
Communication
  • ZigiOps → NewRelic (80/443)
  • ZigiOps → Operations Connector (30005)

Setup

Learn more about how to set up and enable the integration template.

  1. Select the Integrated Systems and click the Save button to continue.

  2. Enable the integration from the slider button, located in the middle section of the screen.


Action Details

Learn more about the actions, available in this integration template.

Each operation consists of 2 tabs - Source and Field Map. The Source tab contains the trigger, the trigger conditions, and the expressions configuration and the Field Map tab contains the mapping configuration.

Open Violations

This operation polls the data from NewRelic. It is designed to collect Open violations from NewRelic and create a new event in OpsBridge. The Violation is collected from the NewRelic instance, then it is internally processed through the field mapping configuration, and finally, a request is sent to OpsBridge to create a new event.

Source

From this tab, you could customize the polling interval, trigger conditions, and expressions or use the defaults. 

Field Map

From this tab you could customize the field, value, and conditional mappings, which suit your requirements.

Closed Violations

This operation polls the data from NewRelic. It is designed to collect Close violations from NewRelic and create a new event in OpsBridge. The violations are collected from the NewRelic instance, then it is internally processed through the field mapping configuration, and finally, a request is sent to OpsBridge to create a new event.

Source

From this tab, you could customize the polling interval, trigger conditions, and expressions or use the defaults. 

Field Map

From this tab you could customize the field, value, and conditional mappings, which suit your requirements.

Recommendations

This section provides information about the recommended considerations, which should be taken into account, before starting the integration.

Correlation

It is recommended to keep the default correlation configuration unless you're familiar with the integration and the specifics of the integrated systems. You could contact our support team for assistance, prior to further changes to the correlation configuration.

Mapping

The predefined templates comply with the specifics of the integrated systems. It is recommended to confirm if your integrated systems have any required fields, which must be reported, so you could map them accordingly. Please note that if a required field is not mapped, the operation might fail. In this case, you could review the troubleshooting page for more information about the operation's execution history.