Edge Delta Remedy Output

Trigger data to Remedy.

Overview

This output type sends notifications and alerts to a specified Remedy URL.

Example

  - name: remedy-default
      type: remedy
      endpoint: "localhost"
      token: remedy-token
      notify_content:
        custom_fields:
          "test-field": "test"
      custom_headers:
        X-header1: "test-header"

Parameters

name

Required

Enter a descriptive name for the output or integration.

For outputs, this name will be used to map this destination to a workflow.

name: remedy-default

integration_name

Optional

This parameter refers to the organization-level integration created in the Integrations page.

If you need to add multiple instances of the same integration into the config, then you can add a custom name to each instance via the name parameter. In this situation, the name should be used to refer to the specific instance of the destination in the workflows.

integration_name: ed-alert-remedy

type: remedy

Required

Enter remedy.

type: remedy

endpoint

Required

Enter the Remedy API endpoint.

endpoint: "localhost"

username

Optional

Enter the username for Remedy basic authentication.

You must enter a token or a username/password.

password

Optional

Enter the password for Remedy basic authentication.

You must enter a token or a username/password.

token

Optional

Enter the Remedy token.

You must enter a token or a username/password.

token: remedy-token

custom_headers and custom_fields

Optional

This parameter is used to customize the notification content.

If you do not want to use default fields in a notification, then you can create custom headers and fields.

      notify_content:
        custom_fields:
          "test-field": "test"
      custom_headers:
        X-header1: "test-header"