Skip to main content

Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow, DB-CDC, Spark ETL, or Replication data flow that sends data to an Opsgenie location.
opsgenie_api.png

Opsgenie

Create an Opsgenie Destination​

  1. Click the + icon on the Nexset that will be sent to the Opsgenie destination, and select the Send to Destination option from the menu.

  2. Select the Opsgenie connector from the list of available destination connectors. Then, select the credential that will be used to connect to your Opsgenie account, and click Next; or, create a new Opsgenie credential for use in this flow.

  3. In Nexla, Opsgenie destinations can be created using pre-built endpoint templates, which expedite destination setup for common Opsgenie endpoints. Each template is designed specifically for the corresponding Opsgenie endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    Opsgenie destinations can also be configured manually, allowing you to send data to Opsgenie endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Opsgenie endpoints. Each template is designed specifically for the corresponding Opsgenie endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

    Create Alerts

    This endpoint template sends each Nexset record as an alert to your Opsgenie account. Use this template when you need to create alerts in Opsgenie from your data, such as monitoring alerts, incident notifications, or system alerts.

    • This endpoint automatically creates alerts from your data. No additional configuration is required beyond selecting this endpoint template. The request body should contain the alert data in JSON format matching the Opsgenie Alert API structure.

    This endpoint sends data as JSON in the request body to create alerts in your Opsgenie account. Each record from your Nexset will be sent as a separate API request to create a new alert in Opsgenie. The request body should contain the alert data in the format required by the Opsgenie Alert API, including alert message, priority, tags, and other alert properties.

    For detailed information about alert creation, request body formats, available alert properties, and alert management, see the Opsgenie Alert API documentation.

    Create Incidents

    This endpoint template sends each Nexset record as an incident to your Opsgenie account. Use this template when you need to create incidents in Opsgenie from your data, such as service incidents, outage notifications, or maintenance events.

    • This endpoint automatically creates incidents from your data. No additional configuration is required beyond selecting this endpoint template. The request body should contain the incident data in JSON format matching the Opsgenie Incident API structure.

    This endpoint sends data as JSON in the request body to create incidents in your Opsgenie account. Each record from your Nexset will be sent as a separate API request to create a new incident in Opsgenie. The request body should contain the incident data in the format required by the Opsgenie Incident API, including incident message, priority, impact, and other incident properties.

    For detailed information about incident creation, request body formats, available incident properties, and incident management, see the Opsgenie Incident API documentation.

Configure Manually​

Opsgenie destinations can be manually configured to send data to any valid Opsgenie API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Opsgenie API after each call to a new Nexla webhook data source.

API Method​

  1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Opsgenie API from the Method pulldown menu. Opsgenie API typically uses POST method for creating resources.

Data Format​

  1. Select the format in which the Nexset data will be sent to the Opsgenie API from the Content Format pulldown menu. Opsgenie API expects JSON format for all requests.

API Endpoint URL​

  1. Enter the URL of the Opsgenie API endpoint to which data will be sent in the URL field. This should be the complete URL including your API base URL (from your credential), the API path (e.g., /v2/alerts, /v1/incidents/create), and any required query parameters (e.g., https://api.opsgenie.com/v2/alerts). Include any required query parameters in the URL.

Ensure the API endpoint URL is correct and accessible with your current credentials. The Opsgenie API endpoint URL should point to the endpoint where you want to create resources. The endpoint URL should include your API base URL and the resource type path. You can test the endpoint using the Test button after configuring the URL.

Request Body​

  1. Configure the request body that will be sent to the Opsgenie API. The request body should contain the resource data formatted as JSON, with field names matching the Opsgenie API's expected structure. The request body format is typically {message.json} to send the entire Nexset data as JSON, or you can construct a custom JSON structure with specific field mappings.

The request body must be valid JSON and must match the Opsgenie API's expected format for the specific endpoint you're using. Opsgenie API uses specific structures for different endpoints (alerts, incidents, etc.). For detailed information about request body formats, available endpoints, and resource structures, see the Opsgenie API documentation.

Save the Destination​

  1. Once all of the relevant steps in the above sections have been completed, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the destination configuration for later use.