Big Panda Triggering Output and Integration

Enter a descriptive name for the output or integration.

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

This parameter is required. 

Review the following example: 

name: error-anomaly-bigpanda

This parameter only appears when you create an individual output.

This parameter refers to the organization-level integration created in the Integrations page. If you enter this name, then the rest of the fields will be automatically populated.

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 field. In this situation, the name should be used to refer to the specific instance of the destination in the workflows.

This parameter is optional. 

Review the following example: 

integration_name: ed-alert-bigpanda

Enter bigpanda.

This parameter is required. 

Review the following example: 

type: bigpanda

Enter the BigPanda endpoint URL.

This parameter is required. 

Review the following example: 

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

Enter the BigPanda token.

This parameter is required. 

Review the following example: 

token: panda-token

Enter the BigPanda application key.

This parameter is required. 

Review the following example: 

app_key: panda-app-key

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.

This parameter is optional. 

Review the following example: 

custom_fields: 
  "test-field": "test"