Alerts
The Alerts API allows you to easily integrate a monitoring system with BigPanda. Monitoring systems generally send out events when problems are detected and when problems have been resolved (fixed).
The API receives event payloads from a monitoring system. Incoming events sent via the REST API are processed according to the BigPanda alert correlation logic. Depending on the results of the correlation, the system then creates a new incident or updates an existing incident based on Alert Correlation Logic rules.
If the tool you are integrating with does not support HTTP headers, you can use the access_token URL parameter for authentication. For example: <https://api.bigpanda.io/data/v2/alerts?access_token=><YOUR TOKEN>
Sending multiple alerts
BigPanda uses the timestamp to determine the latest status of an incident. If it is not included, BigPanda uses the time when the alert is received. To ensure that BigPanda accurately reflects the current status, when sending multiple alerts, you must include the timestamp for each alert or sort the alerts array by when the events occurred, in ascending order.
Sending duplicate events
When an event sent via the Alerts API is an exact duplicate of a previous event, BigPanda returns an HTTP response code of 204 No Content.
Resolving alerts
To maintain only the most relevant information in the incident feed, we recommend configuring monitoring systems to send resolving events to BigPanda when an alert is no longer active.
Generic Alerts
Authentication
All BigPanda APIs require Bearer Token Authorization in the call headers.
This API uses the Org Token type of Authorization token.
BigPanda recommends adding Authentication headers only in the secure tool you use to make API calls.