Skip to main content
All CollectionsIntegrations
Data Push Destinations - BigPanda (Beta)
Data Push Destinations - BigPanda (Beta)
Written by Josh Peters
Updated over a week ago

The UXI data push for BigPanda is a beta feature and enables you to see your issue data or incident data in BigPanda. You can sign up to test this beta feature by contacting support. The integration with BigPanda makes use of the BigPanda Open Integration Manager.

Benefits of sending UXI incident data to BigPanda – Incident data is available only for dashboards that use Incident Detection. Using the incident data provides fewer notifications, as you are only notified when incidents are created and resolved. However, incidents evolve over time, and you do not get the underlying details of issues within the incident. Each incident has a unique incident identifier you can use to track when the incident is opened and resolved. All the fields are described in the incident schema.

Benefits of sending UXI issue data to BigPanda – Issue data provides more notifications as you are notified of every issue and state transition (created, updated, resolved). However, issue data provides the most detail to see which specific sensors are experiencing the problems. Each issue has a unique issue uid you can use to track when the issue is created and resolved. All the fields are described in the issue schema.

Example using the UXI Data Push for issues with BigPanda

Login to BigPanda and select Integrations -> New Integration

Under All Integrations, select Open Integrations Manager.

Follow the steps to create an app key

Select Alerts REST API

Select Generate App Key, Copy the resulting Auth Token and App Key

In your UXI dashboard, go to Settings -> Integrations

Under Data Push Destinations, select Add Destination

In the Add Data Push Destination menu, select the following options:

· Data Type Issues

· Destination Type: BigPanda

· Name: Provide a meaningful name

· Url: enter the BigPanda URL

· App Key: Enter the BigPanda app key created earlier

· Access Token: Enter the BigPanda access token created earlier

In BigPanda, Toggle to the tab for Integration Manager.

Below are the settings we are using in our test environment.

1. Tag Mapping:
Create multiple events using the "elements" tag. The format of the messages sent to BigPanda is as follows where the <issue or incident> corresponds to the issue schema or incident schema:

"elements" :
<issue or incident>,
<issue or incident>

For BigPanda to parse this into multiple issues, use the option to create multiple alerts using the “elements” part of the payload. In subsequent steps, use @alert to refer to the elements of each issue payload.

Each issue has a unique uid that UXI uses to track the issue lifecycle.

2. Status Mapping

Use the event_type field of each issue to set the severity to warning when the issue is CREATED and OK when the issue is RESOLVED.

3. Use each issue timestamp

4. Event Deduplication

You can optionally set this to use the issue identifier

5. Event Filtering

Issues transition to various states during their lifecycles, especially when using incident detection. For integration purposes, it's better to ignore these transitions and only consider cases where the issue is created and resolved. You can ignore the other cases with the following:

@alert.event_type = UPDATED OR @alert.event_type = INCIDENT_ADDED OR @alert.event_type = INCIDENT_REMOVED

When completed, you should see new issues represented in BigPanda as severity warnings, and when the issue is resolved, the severity is set to OK.

Did this answer your question?