Integration Diagnostics

In case an issue or problem occurs within the integration lifecycle, BigPanda allows you to troubleshoot errors and issues in real-time.

In order for BigPanda to receive alerts from your monitoring tools, each integration must be correctly configured. With certain configuration issues, the payload will fail and the alert information will never appear in BigPanda, instead triggering an error. These failed alerts will not appear in BigPanda.

BigPanda will automatically mark integrations with failed payloads on the Integrations tab. Review these errors to identify and troubleshoot integration issues so that no alerts are missed.

Any integration that has a failed payload within the previous 24 hours will have the number of errors highlighted in red on the Integration ribbon in the left pane. Integrations with failed payloads in the previous 7 days will have the number of errors marked in grey on the integration ribbon in the left pane.

🚧

Errors are only shown in the UI for 7 days. We recommend checking regularly to ensure that no alerts are falling through the cracks, especially during the first few weeks with any new integration.

The Troubleshooting log provides additional information about the error to help you find the configuration issue in the source tool. You can search the Troubleshooting log to find specific information about an event or payload.

To troubleshoot integrated source systems:

  1. Open the Integrations tab. The Integrations list appears, displaying all of the integrations with error indicators on the Integration tiles. Errors are indicated for both active and pending integrations.
  1. Select the Integration you wish to troubleshoot.

📘

The number of errors appears in the right pane. Errors are deleted after 7 days. You can view the Last Event label to learn when the last successful event was received.

  1. Select Troubleshooting. The Troubleshooting log opens presenting a list of events in the left pane.
  2. To filter the Troubleshooting log;
    • Add a specific event or payload in the search text box.
      Or,
    • Set the filter parameters as follows:

Parameter

Description

Description

  • Any description
  • Select from any existing payload descriptions

Date

  • Last 7 days
  • Last 24 hours
  • Custom Dates Range
  1. To view the error, select the event. The payload appears in the right pane.
  2. To copy the payload to your clipboard, select Copy.
  1. Use the information provided about each event to fix the settings in the source system and resolve the errors. The following error messages are available:

Error type

Description

Explanation

invalid_payload

Request body must contain at least one alert

The request body is empty. Check the configuration of the monitoring system to ensure it does not send an empty payload.

invalid_payload

‘primary_property’ must exist and be one of the following: host, service, application, device

A primary property is missing. This is a mandatory field that defines how an incident title appears in BigPanda. Make sure each event is sent with one of the following fields: host, service, application, or device.

invalid_payload

‘primary_property' X does not reference any property

The primary property is mentioned in the payload, but it is not related to a specific entity. The host, service, application, or device must be designated.

invalid_payload

‘secondary_property' X does not reference any property

A secondary property is mentioned in the payload, but it is not related to a specific entity. The check or sensor fields must be designated.

invalid_payload

'timestamp' must be a time in Unix format (UTC timezone)

Fix the timestamp format to match the UTC timezone definition.

invalid_payload

‘status' must exist and be one of the following: ok, critical, warning, unknown, acknowledged

An improper status field was sent in the payload. Make sure that only one of the following options for status is used: ok, critical, warning, unknown, and acknowledged.


Recommended Reading