Big Panda Triggering Output and Integration

Overview

This output type sends notifications and alerts to a specified BigPanda endpoint.

Review Sample Configuration

The following sample configuration displays an output without the name of the organization-level integration:

    - name: bigpanda-default
      type: bigpanda
      endpoint: "https://api.bigpanda.io/data/v2/alerts"
      token: panda-token
      app_key: panda-app-key
      notify_content:
        custom_fields:
          "test-field": "test"

Review Parameters

Review the following parameters that you can configure in the Edge Delta App:

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.

Review the following example: 

name: error-anomaly-bigpanda

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.

Review the following example: 

integration_name: ed-alert-bigpanda

type

Required

Enter bigpanda.

Review the following example: 

type: bigpanda

endpoint

Required

Enter the BigPanda endpoint URL.

Review the following example: 

endpoint: "https://api.bigpanda.io/data/v2/alerts"

token

Required

Enter the BigPanda token.

Review the following example: 

token: panda-token

app_key

Required

Enter the BigPanda application key.

Review the following example: 

app_key: panda-app-key

notify_content: 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 create custom headers and fields.

To learn more, see Review Notify Content Parameters.

Review the following example: 

custom_fields: 
  "test-field": "test"