Skip to main content

Integrate with BigPanda

BigPanda’s agnostic architecture allows you to automatically ingest raw data from monitoring, collaboration, or contextual sources, then connects that data together across our robust IT Knowledge Graph to accelerate and automate your ITOps processes.

Relevant Permissions

Roles with the following permissions can access the BigPanda Integrations tab and Integration configuration:

Role Name 

Description 

Integrations

Manage BigPanda Integrations in the BigPanda Integrations tab.

Alert Enrichment

View and use the Alert Enrichments UI and API.

Permission access levels can be adjusted by selecting either View or Full Access. To learn more about how BigPanda's permissions work, see the Roles Management documentation.

Integrate across BigPanda products

The BigPanda platform includes four products that share a common integrations framework. Each product uses the same connected data in a different way:

  • Event IntelligenceIntegrate with AI Detection and Response - Ingests alerts from monitoring tools, deduplicates and normalizes them into high-quality alerts, and correlates related alerts into actionable incidents. This is where most monitoring, changes, topology, and collaboration integrations are configured.

  • AI Detection and Response (ADR)Integrate with AI Detection and Response - Uses alert, change, and topology integrations to detect emerging issues early and enrich incidents with AI-driven triage context. ADR works with the same monitoring integrations as the core platform and adds integrations with service desk, change management, and external observability tools.

  • AI Incident AssistantIntegrate with AI Incident Assistant and Prevention - Connects to chat, conferencing, ITSM, observability, and on-call tools to automate triage, collaboration, and escalation. Integrations are configured as AI agent tools that the AI Incident Assistant can call during an incident.

  • AI Incident PreventionIntegrate with AI Incident Assistant and Prevention - Uses ITSM, change, and observability data, often synced through the Unified Data Connector, to surface patterns and risks before they become incidents.

Some tools may have multiple integrations to support different data types or products. For example, ServiceNow can be integrated as a bidirectional sync with Event Management, serve as an ITSM tool for Incident Assistant, be added as a contextual connector through the UDC, or through individual connections tying CMDB and maintenance plans to ADR.

As the specific integrations required for your team may vary based on the products and features your team leverages, reach out to your account team for advice on integration best practices for your circumstances.

Share integrated data through UDC

The Unified Data Connector(UDC) enables context sharing across BigPanda products. When possible, sync ITSM, change, and knowledge data through UDC to ensure all teams have access to the same data. 

Data standardization

The complexity of enterprise systems is a challenge even for the smartest automations. The more tools that are coordinating across multiple access points and leveraging varied formats, the more likely small errors can have downstream business impacts. Whenever possible, apply data normalization best practices to reduce the chance of missed data connections.

Whitelist Source IPs

To enable outbound integrations with certain collaboration tools such JIRA and ServiceNow, you may need to whitelist BigPanda IP addresses.

Outbound IPs

BigPanda uses the following IP addresses for outbound integrations. We recommend you whitelist these IP addresses:

US Regions:

  • 54.151.42.136

  • 52.53.42.221

  • 54.236.197.177

  • 18.213.73.104

  • 52.70.92.71

  • 3.129.47.16 (Used for Biggy)

  • 52.202.174.130 *

  • 34.206.214.75 *

  • 100.24.96.213 *

  • 52.88.166.255 *

  • 54.185.33.241 *

EU Outbound IPs

BigPanda uses a set list of IPs for outbound integrations to the EU. Add these IP address to your firewall rules to allow BigPanda to create tickets and share updates with the respective systems.

  • 18.198.221.213

  • 18.198.124.132

  • 3.64.169.118

  • 52.58.7.255

  • 52.58.83.1

  • 3.124.97.0

  • 18.158.124.29

  • 34.248.210.211 *

  • 108.128.243.45 *

  • 34.246.3.55 *

Disaster recovery IP addresses

The IP addresses marked with asterisks (*) are disaster recovery IPs.

Additional IP addresses may be needed

Add these IP addresses to your firewall rules to allow BigPanda to create tickets and share updates with the respective systems.

Custom integrations may use additional outbound IPs not listed here. These IPs are configured as part of the integration setup with your team and BigPanda. Contact your account team for more information.

Inbound IPs

At this time, BigPanda does not have dedicated IP addresses for sending data to BigPanda, but instead leverages an AWS IP block.

The IP addresses for our API endpoints could change at any time to an address within AWS's IP block. You can find an up-to-date list of AWS IPs here.

Relevant Permissions

Roles with the following permissions can access the BigPanda Integrations tab and Integration configuration:

Role Name 

Description 

Integrations

Manage BigPanda Integrations in the BigPanda Integrations tab.

Alert Enrichment

View and use the Alert Enrichments UI and API.

Permission access levels can be adjusted by selecting either View or Full Access. To learn more about how BigPanda's permissions work, see the Roles Management documentation.

Integrate with Event Management and AI Detection and Response

Administrators can install any of the standard integrations in BigPanda.

  1. Navigate to the Integrations tab.

  2. In the left pane, click New Integration.

  3. Select or search for the desired integration.

  4. Follow the instructions to install and configure your integration. Some configuration in the desired tool may be necessary.

Find an Integration

You can filter the list of available integrations by type by selecting the desired type at the top or by entering a search term in the top right. If you don't see the tool you use, consider using the Alerts API, email parser, or contact BigPanda support.

integrations_create_lobby

Integration Selection

Open Integration Manager

Some integrations have additional configuration options available through the Open Integration Manager, allowing you to adjust timestamp, status, tag fields and more. The Open Integration Manager will automatically appear as a secondary tab during Integration configuration.

App Keys

The first step in creating a new integration is to generate the app key. The app key is a unique identifier associated with the application. App keys are required for connecting BigPanda to other systems.

When generating the app key, you also select the name for the integration in the UI. When naming an integration, be sure to use a short (max 200 characters), clear name that will be understood across your organization. Keep in mind, some tools may require multiple integrations to support different configurations or subsystems and your name should make it clear which specific element the integration connects to.

Once you are happy with your integration name, click Generate App Key.

BigPanda will create an App Key and internal System ID for the integration. Both may be necessary later during integration install or configuration, so make note of both.

Integration ID

The Integration ID is automatically created from the integration name. The ID can be used in BPQL searches, and in API calls.

Once the ID is assigned, it cannot be changed.

Time-Based Alert Resolution

With Time-Based Alert Resolution, you can set up automatic resolution for orphaned or outstanding alerts to easily reduce noise and help increase MTTR.

Use the Auto-Resolve drop-down menu to select the time period for when alerts are automatically resolved. Alerts that are not updated within the auto-resolve time frame will automatically be resolved.

Initial Resolution

The default auto-resolve time is 30 days. When first turning on Time-Based Alert Resolution for an integration, all alerts older than 30 days will be automatically resolved.

The Auto-Resolve time can also be edited after the integration has been created. To edit the Auto-Resolve time, navigate to Settings, then Integrations. Find the integration from the list, and click Edit Integration to change the Auto-Resolve time.

Adjust with Caution

When a shorter time frame is selected, the new auto-resolution rule will apply to all existing alerts from that integration. Any outstanding alerts that meet the new time-rule will immediately be slotted for auto-resolution.

Validate and Troubleshoot the Integration

After first setting up an integration, compare the incidents in BigPanda with alerts in the native monitoring system. This will help ensure that data is flowing correctly into BigPanda.

This can be done by searching for incidents from a specific monitoring system over a specified time frame. From that same time frame, search within the native monitoring application. Check to make sure that alerts from all servers are entering BigPanda.

If alerts are missing, the following may be occurring:

  • BigPanda is deduplicating the alerts.

  • The alert was sent with an invalid status.

  • The alert was not configured to be sent. Some source systems allow you to choose what is sent to BigPanda. Confirm that the configuration in the monitoring tool is correctly configured.

  • The integration instance was not connected. If there are multiple instances of an integration, confirm that each one is connected to BigPanda.

See Troubleshoot an Integration for more information about fixing errors and other issues.

App Keys

The first step in creating a new integration is to generate the app key. The app key is a unique identifier associated with the application. App keys are required for connecting BigPanda to other systems.

When generating the app key, you also select the name for the integration in the UI. When naming an integration, be sure to use a short (max 200 characters), clear name that will be understood across your organization. Keep in mind, some tools may require multiple integrations to support different configurations or subsystems and your name should make it clear which specific element the integration connects to.

Once you are happy with your integration name, click Generate App Key.

BigPanda will create an App Key and internal System ID for the integration. Both may be necessary later during integration install or configuration, so make note of both.

Integration ID

The Integration ID is automatically created from the integration name. The ID can be used in BPQL searches, and in API calls.

Once the ID is assigned, it cannot be changed.

Time-Based Alert Resolution

With Time-Based Alert Resolution, you can set up automatic resolution for orphaned or outstanding alerts to easily reduce noise and help increase MTTR.

Use the Auto-Resolve drop-down menu to select the time period for when alerts are automatically resolved. Alerts that are not updated within the auto-resolve time frame will automatically be resolved.

Initial Resolution

The default auto-resolve time is 30 days. When first turning on Time-Based Alert Resolution for an integration, all alerts older than 30 days will be automatically resolved.

The Auto-Resolve time can also be edited after the integration has been created. To edit the Auto-Resolve time, navigate to Settings, then Integrations. Find the integration from the list, and click Edit Integration to change the Auto-Resolve time.

Adjust with Caution

When a shorter time frame is selected, the new auto-resolution rule will apply to all existing alerts from that integration. Any outstanding alerts that meet the new time-rule will immediately be slotted for auto-resolution.

Validate and Troubleshoot the Integration

After first setting up an integration, compare the incidents in BigPanda with alerts in the native monitoring system. This will help ensure that data is flowing correctly into BigPanda.

This can be done by searching for incidents from a specific monitoring system over a specified time frame. From that same time frame, search within the native monitoring application. Check to make sure that alerts from all servers are entering BigPanda.

If alerts are missing, the following may be occurring:

  • BigPanda is deduplicating the alerts.

  • The alert was sent with an invalid status.

  • The alert was not configured to be sent. Some source systems allow you to choose what is sent to BigPanda. Confirm that the configuration in the monitoring tool is correctly configured.

  • The integration instance was not connected. If there are multiple instances of an integration, confirm that each one is connected to BigPanda.

See Troubleshoot an Integration for more information about fixing errors and other issues.

Delete an Integration

Deleting an integration requires that you remove the integration in both the integrated system and BigPanda. We recommend that you first uninstall the integration on the integrated system to prevent traffic from being sent and rejected by BigPanda, since the app_key will not exist once you delete the integration in BigPanda.

Caution during replacement

When replacing an existing integration with a new tool or system, we recommend configuring the new integration first to ensure no data is lost.

Delete an Inbound Integration

Inbound integrations can be deactivated to disable the integration without deleting the configuration and settings. We recommend deactivating an inbound integration before permanently disabling it.

Deactivate Inbound Integration

If you want to stop sending data to BigPanda but don’t want to delete your integration, you can temporarily deactivate it.

To deactivate an inbound integration:

  1. In BigPanda, navigate to the Integrations tab and select the desired integration from the list. This will open integration details on the right side of the window.

  2. At the top of the integration details, click the Active/Inactive toggle next to the application name to change the status of the integration.

In the integrations list, inactive integrations will be marked with a gray bar.

Stop sending data from BigPanda

In BigPanda, disable any settings that send data to the integrated system. This includes modifying or removing AutoShare rules or Environments that are tied to the integration.

Delete the integration in BigPanda

Take the following steps to delete the integration from BigPanda:

  1. In BigPanda, navigate to the Integrations tab and select the desired integration from the list.

  2. In the integration details on the right of the page, click the trash icon, then confirm you want to delete the integration. The integration will be removed immediately.

Data removal: active alerts

All active alerts from the integration will be resolved after deletion.

Delete an Outbound Integration

Outbound integrations cannot be deactivated within BigPanda. To deactivate an outbound integration without removing the configuration or settings, remove the integration from configured automations and deactivate the receiver in the destination tool.

Stop sending data from BigPanda

In BigPanda, disable any settings that send data to the integrated system. This includes modifying or removing AutoShare rules or Environments that are tied to the integration.

Delete the integration in BigPanda

Take the following steps to delete the integration from BigPanda:

  1. In BigPanda, navigate to the Integrations tab and select the desired integration from the list.

  2. In the integration details on the right of the page, click the trash icon, then confirm you want to delete the integration. The integration will be removed immediately.

️Data will not be removed from BigPanda or integrated systems

This procedure does not remove any data from BigPanda or the integrated system. As needed, remove data from each system before deleting the integration.

Delete an Inbound Integration

Inbound integrations can be deactivated to disable the integration without deleting the configuration and settings. We recommend deactivating an inbound integration before permanently disabling it.

Deactivate Inbound Integration

If you want to stop sending data to BigPanda but don’t want to delete your integration, you can temporarily deactivate it.

To deactivate an inbound integration:

  1. In BigPanda, navigate to the Integrations tab and select the desired integration from the list. This will open integration details on the right side of the window.

  2. At the top of the integration details, click the Active/Inactive toggle next to the application name to change the status of the integration.

In the integrations list, inactive integrations will be marked with a gray bar.

Stop sending data from BigPanda

In BigPanda, disable any settings that send data to the integrated system. This includes modifying or removing AutoShare rules or Environments that are tied to the integration.

Delete the integration in BigPanda

Take the following steps to delete the integration from BigPanda:

  1. In BigPanda, navigate to the Integrations tab and select the desired integration from the list.

  2. In the integration details on the right of the page, click the trash icon, then confirm you want to delete the integration. The integration will be removed immediately.

Data removal: active alerts

All active alerts from the integration will be resolved after deletion.

Delete an Outbound Integration

Outbound integrations cannot be deactivated within BigPanda. To deactivate an outbound integration without removing the configuration or settings, remove the integration from configured automations and deactivate the receiver in the destination tool.

Stop sending data from BigPanda

In BigPanda, disable any settings that send data to the integrated system. This includes modifying or removing AutoShare rules or Environments that are tied to the integration.

Delete the integration in BigPanda

Take the following steps to delete the integration from BigPanda:

  1. In BigPanda, navigate to the Integrations tab and select the desired integration from the list.

  2. In the integration details on the right of the page, click the trash icon, then confirm you want to delete the integration. The integration will be removed immediately.

️Data will not be removed from BigPanda or integrated systems

This procedure does not remove any data from BigPanda or the integrated system. As needed, remove data from each system before deleting the integration.

Whitelist Source IPs

To enable outbound integrations with certain collaboration tools such JIRA and ServiceNow, you may need to whitelist BigPanda IP addresses.

Outbound IPs

BigPanda uses the following IP addresses for outbound integrations. We recommend you whitelist these IP addresses:

US Regions:

  • 54.151.42.136

  • 52.53.42.221

  • 54.236.197.177

  • 18.213.73.104

  • 52.70.92.71

  • 3.129.47.16 (Used for Biggy)

  • 52.202.174.130 *

  • 34.206.214.75 *

  • 100.24.96.213 *

  • 52.88.166.255 *

  • 54.185.33.241 *

EU Outbound IPs

BigPanda uses a set list of IPs for outbound integrations to the EU. Add these IP address to your firewall rules to allow BigPanda to create tickets and share updates with the respective systems.

  • 18.198.221.213

  • 18.198.124.132

  • 3.64.169.118

  • 52.58.7.255

  • 52.58.83.1

  • 3.124.97.0

  • 18.158.124.29

  • 34.248.210.211 *

  • 108.128.243.45 *

  • 34.246.3.55 *

Disaster recovery IP addresses

The IP addresses marked with asterisks (*) are disaster recovery IPs.

Additional IP addresses may be needed

Add these IP addresses to your firewall rules to allow BigPanda to create tickets and share updates with the respective systems.

Custom integrations may use additional outbound IPs not listed here. These IPs are configured as part of the integration setup with your team and BigPanda. Contact your account team for more information.

Inbound IPs

At this time, BigPanda does not have dedicated IP addresses for sending data to BigPanda, but instead leverages an AWS IP block.

The IP addresses for our API endpoints could change at any time to an address within AWS's IP block. You can find an up-to-date list of AWS IPs here.

Outbound IPs

BigPanda uses the following IP addresses for outbound integrations. We recommend you whitelist these IP addresses:

US Regions:

  • 54.151.42.136

  • 52.53.42.221

  • 54.236.197.177

  • 18.213.73.104

  • 52.70.92.71

  • 3.129.47.16 (Used for Biggy)

  • 52.202.174.130 *

  • 34.206.214.75 *

  • 100.24.96.213 *

  • 52.88.166.255 *

  • 54.185.33.241 *

EU Outbound IPs

BigPanda uses a set list of IPs for outbound integrations to the EU. Add these IP address to your firewall rules to allow BigPanda to create tickets and share updates with the respective systems.

  • 18.198.221.213

  • 18.198.124.132

  • 3.64.169.118

  • 52.58.7.255

  • 52.58.83.1

  • 3.124.97.0

  • 18.158.124.29

  • 34.248.210.211 *

  • 108.128.243.45 *

  • 34.246.3.55 *

Disaster recovery IP addresses

The IP addresses marked with asterisks (*) are disaster recovery IPs.

Additional IP addresses may be needed

Add these IP addresses to your firewall rules to allow BigPanda to create tickets and share updates with the respective systems.

Custom integrations may use additional outbound IPs not listed here. These IPs are configured as part of the integration setup with your team and BigPanda. Contact your account team for more information.

Inbound IPs

At this time, BigPanda does not have dedicated IP addresses for sending data to BigPanda, but instead leverages an AWS IP block.

The IP addresses for our API endpoints could change at any time to an address within AWS's IP block. You can find an up-to-date list of AWS IPs here.

Custom Integrations

In addition to the standard integrations, you can use email content or the Notifications Webhook to build custom integrations with other messaging, ticketing, or collaboration systems.

Build Webhooks

The Notifications Webhook lets you share incidents with a collaboration tool via a callback URL. The webhook will send incident and alert data to the recipient application, which can process the information based on the business login you configure.

To learn more about using webhooks to create sharing channels, or see available sharing fields and example share payloads, see the Notifications Webhook documentation.

Email-Based Integrations

BigPanda emails and SMS messages are sent using a standard format that can be parsed to populate tickets and messaging in other collaboration tools.

Incident ID

The BigPanda incident link includes the unique incident ID number as the last 24 characters of the URL. You can parse the email for the ID, and use it as a unique key to help determine if the notification is for a new incident or for an update to an existing one.

Email Subject Format 

<User name> shared with you the incident: <Incident subjects> / <Alerts summary>

Email Body Format 

<Sharing annotation>

<User name> shared this incident with you.

Details as of:<Last change to incident><Link to Incident>

Incident Details:

Status:<Incident status>

Started at:<Incident start time>

Source system:<Source system>< - Integration name>(one entry for each source system)

Preview:<Link to incident preview page>

BigPanda:<Link to incident details>

Timeline:<Link to incident timeline>

Service :<Incident subjects>

Check:<Alerts summary>

This incident contains: (<Number of active alerts>)<Status of alerts>(One entry for each active alert) <Alert status> <Alert source system>

<Alert subject>

<Alert name>

<Link to Incident>

emailtemplate.png

SMS Message Format

<Incident status> <Incident subjects>

<Link to BigPanda incident preview page>

<Alerts summary>

Message length limits

BigPanda sends only one SMS message per incident update. To limit the length of the SMS message, incident subjects and the alerts summary may be truncated in the message.

Build Webhooks

The Notifications Webhook lets you share incidents with a collaboration tool via a callback URL. The webhook will send incident and alert data to the recipient application, which can process the information based on the business login you configure.

To learn more about using webhooks to create sharing channels, or see available sharing fields and example share payloads, see the Notifications Webhook documentation.

Email-Based Integrations

BigPanda emails and SMS messages are sent using a standard format that can be parsed to populate tickets and messaging in other collaboration tools.

Incident ID

The BigPanda incident link includes the unique incident ID number as the last 24 characters of the URL. You can parse the email for the ID, and use it as a unique key to help determine if the notification is for a new incident or for an update to an existing one.

Email Subject Format 

<User name> shared with you the incident: <Incident subjects> / <Alerts summary>

Email Body Format 

<Sharing annotation>

<User name> shared this incident with you.

Details as of:<Last change to incident><Link to Incident>

Incident Details:

Status:<Incident status>

Started at:<Incident start time>

Source system:<Source system>< - Integration name>(one entry for each source system)

Preview:<Link to incident preview page>

BigPanda:<Link to incident details>

Timeline:<Link to incident timeline>

Service :<Incident subjects>

Check:<Alerts summary>

This incident contains: (<Number of active alerts>)<Status of alerts>(One entry for each active alert) <Alert status> <Alert source system>

<Alert subject>

<Alert name>

<Link to Incident>

emailtemplate.png

SMS Message Format

<Incident status> <Incident subjects>

<Link to BigPanda incident preview page>

<Alerts summary>

Message length limits

BigPanda sends only one SMS message per incident update. To limit the length of the SMS message, incident subjects and the alerts summary may be truncated in the message.

Standard Integrations

Standard integrations are any integration that has a tile in BigPanda, or uses the Open Integration Manager or Email Parser. BigPanda offers 50+ standard integrations to streamline receiving ops tools data and sharing information with your collaborators through other systems.

BigPanda 's inbound integrations make it simple to bring together monitoring, change, and topology tools. and normalize events and enrich them with deep contextual information.

BigPanda's outbound collaboration integrations communicate bi-directionally to keep ticketing, notifications, and chat tools in sync across your teams.

https://files.readme.io/06bb7b2-integrationsOverview.png

Full Integrated Suite

Best Practices

Before you begin to configure standard integrations, we recommend taking preparation steps to ensure a smooth launch.

For all integrations

  • Identify the tool version and ensure it is compatible with BigPanda.

  • If integrating a monitoring tool, ensure it has the ability to send outbound event notifications.

  • Check that the tool has access to the internet to outbound event notifications.

  • Check that all security requirements (such as whitelisting) are met to send traffic outside the core network.

  • Review the BigPanda integration instructions and requirements for your tool.

For Open Integration Manager enabled integrations

  • Confirm that the monitoring event payload headers and body be customized.

  • Check that the event headers support org bearer token authentication.

  • Ensure event payload bodies can be formatted in JSON.

For standard Email Parser integrations

  • Configure email recipients to be sent to a BigPanda inbox.

  • Format email bodies into text or HTML.

  • Ensure that email templates remain consistent between event types.

Types of Integrations

BigPanda offers several types of integrations:

  • Monitoring integrations allow BigPanda to receive alerts from your monitoring systems, such as Nagios, SolarWinds, and AppDynamics. Many users start by integrating these systems.

  • Collaboration integrations allow you to share incidents from BigPanda with your co-workers through other systems such as Jira or Slack.

  • Changes integrations allow BigPanda to receive change notifications from your change systems, such as CloudTrail, Jenkins, ServiceNow, and Jira.

  • Topology integrations allow you to enrich alerts coming into BigPanda with topology information from configuration management, cloud and virtualization management, service discovery, APM, and CMDB tools.

Agent vs. Webhook Integrations

BigPanda has the flexibility to support both SaaS and on-premise monitoring tools.

Most SaaS tools (such as CloudWatch or New Relic) are integrated using Webhooks. Whenever the SaaS tool generates an alert, it posts an HTTP message directly to BigPanda. BigPanda listens to incoming messages and processes them.

Many on-premise tools are integrated using the BigPanda agent. The agent is a low-footprint daemon installed on the master host of your monitoring tool. It consumes alerts from the tool in real time, and then transmits them to BigPanda via SSL-encrypted HTTP calls.

The agent can require some additional steps to configure. To learn more about using the agent, see the BigPanda Agent documentation.

Standard vs. Custom Integrations

Standard integrations are any integration that has a tile in BigPanda, or uses the Open Integration Manager or Email Parser. See the diagram below for more information about the difference between standard and custom integrations.

https://files.readme.io/7b3d6eb-Custom_vs_Standard_Chart_11x8.5_FNL.jpg

Deciding Between Standard or Custom Integrations

To learn about options relating to custom integrations, contact your BigPanda support or your onboarding team.

Monitoring Integrations

The following standard monitoring integrations are available:

Product

Supported Versions

Type

Authentication Type

Airbrake

SaaS Deployments (Deprecated)

Webhook

API Fortress

SaaS and On-Premise Deployments

Webhook

Org Bearer Token

AppDynamics

4.1+; On-Premise, Dedicated SaaS Deployments

Webhook

Org Bearer Token

AppOptics

SaaS Deployments

Webhook

Org Bearer Token

Azure Monitor

SaaS Deployments

Webhook

Org Bearer Token

CA Spectrum

9.4.x

Spectrum Scripts

Org Bearer Token

Catchpoint

SaaS Deployments

Webhook

Org Bearer Token

Cisco Meraki

SaaS Deployments

Webhook

Org Bearer Token

CloudWatch

SaaS Deployments

CloudFormation, Webhook

Org Bearer Token

Cribl

<= 4.0.4

Webhook

Org Bearer Token

Datadog

SaaS Deployments

Webhook

Org Bearer Token

Dynatrace APM

SaaS Deployments

Webhook

Org Bearer Token

Entuity

v19 to v21

Webhook

Org Bearer Token

Grafana

Grafana >= v5.0.0

Webhook

Org Bearer Token

Icinga

1, 2

Agent

Org Bearer Token

Librato

SaaS Deployments

Webhook

Org Bearer Token

Logentries

SaaS Deployments

Webhook

Org Bearer Token

LogicMonitor

SaaS Deployments

Webhook

Org Bearer Token

Logscale

1.98.0

Webhook

Org Bearer Token

Logz.io

SaaS Deployments

Webhook

Org Bearer Token

Nagios

3, 4

Agent

Org Bearer Token

Nagios XI

4, 5

Agent

Org Bearer Token

New Relic

SaaS Deployments

Webhook

Org Bearer Token

Opsview

Nagios-Compatible Versions (Version 5 and older)

Agent

Org Bearer Token

Oracle Enterprise Manager

12c, 13c

Email Parser

N/A

Panopta

SaaS Deployments (Depreciated)

Webhook

Pingdom

SaaS Deployments

Webhook

Org Bearer Token

Prometheus

Alertmanager >= v0.16.0

Webhook

Org Bearer Token

PRTG

14.4+; English Language (Only)

Webhook

Org Bearer Token

ScienceLogic

< 11.3.0

Action Script/Webhook

Org Bearer Token

SCOM (Microsoft System Center Operations Manager)

System Center 2012 R2 and 2016

Webhook

Org Bearer Token

Scout

SaaS Deployments (Deprecated)

Webhook

Sematext

SasS Deployments (Deprecated)

Webhook

 

Sensu

0.12+

Webhook

Org Bearer Token

Sentry

SaaS Deployments

Webhook

Org Bearer Token

Site24x7

SaaS Deployments

Webhook

Org Bearer Token

SiteScope

<=2022.11

Webhook

Org Bearer Token

SNMP (Simple Network Management Protocol)

v1, v2, v2c

Daemon and Agent

Org Bearer Token

SolarWinds

Orion Server, Versions 2015.1+; Network Performance Monitor (NPM) 10.4+

Webhook

Org Bearer Token

Splunk

Splunk Enterprise, Splunk Cloud <= 9.0

Native App (v6.3+)

Action Script (pre v6.3)

Org Bearer Token

SQL Sentry

<= 2023.2.9

Webhook

Org Bearer Token

StatusCake

SaaS Deployments (Deprecated)

Webhook

Sumo Logic

SaaS Deployments

Webhook

Org Bearer Token

ThousandEyes

SaaS Deployments

Webhook

Org Bearer Token

Tivoli EIF

7, 8

Agent

Org Bearer Token

VMWare Aria

<=8.10

Webhook

Org Bearer Token

Wavefront

SaaS Deployments

Webhook

Org Bearer Token

Zabbix

2.2, 3.0, 3.2

Agent

Org Bearer Token

Zenoss

Zenoss Core 4, 5, 6

Agent

Org Bearer Token

Collaboration Integrations

The following standard monitoring integrations are available:

Product

Supported Versions

Type

Authentication Type

Ansible Automation Platform

<= v2.4

Webhook

Org Bearer Token

Asana

SaaS Deployments

API

User API Key

Jira

Jira Cloud <= 9.4

API

User API Key and Org Bearer Token

OpsGenie

SaaS Deployments

API

User API Key

PagerDuty

SaaS Deployments

API

Org Bearer Token

ServiceNow

BigPanda App v2.8+ - Xanadu, Washington, Vancouver, Utah, Tokyo, San Diego, Rome, Quebec, Paris, Orlando, New York, Madrid, London, Kingston, Jakarta, Istanbul

BigPanda App v2.3-2.7 - Washington, Vancouver, Utah, Tokyo, San Diego, Rome, Quebec, Paris, Orlando, New York, Madrid, London, Kingston, Jakarta, Istanbul

BigPanda App <v2.3 - Quebec, Paris, Orlando, New York, Madrid, London, Kingston, Jakarta, Istanbul

API

User API Key and Org Bearer Token

Slack

SaaS Deployments

API

Org Bearer Token

xMatters

<= Jun/Jul 2022

API

User API Key

Changes

Product

Supported Versions

Type

Authentication Type

CloudTrail

SaaS

API

User API Key

Jenkins

1.546 or later

Native Plugin, Webhook

User API Key

Jira Changes

Jira Cloud, Jira Server

Native App, Webhook

User API Key and Org Bearer Token

ServiceNow Changes

Tokyo (v2.3+), San Diego (v2.3+), Rome (v2.3+), Quebec, Paris, Orlando, New York, Madrid, London, Kingston, Jakarta, Istanbul

Native App, API

User API Key and Org Bearer Token

Topology

Product

Supported Versions

Type

Authentication Type

Datadog Topology

SaaS

API

Org Bearer Token

Dynatrace Topology

SaaS Deployments

API

Org Bearer Token

ServiceNow CMDB

Tokyo (v2.3+), San Diego (v2.3+), Rome (v2.3+), Quebec, Paris, Orlando, New York, Madrid, London, Kingston, Jakarta, Istanbul

Native App, API

User API Key and Org Bearer Token

vCenter Inventory

vCenter Server 6.5 update 2 and newer

Native Plugin

Org Bearer Token

Best Practices

Before you begin to configure standard integrations, we recommend taking preparation steps to ensure a smooth launch.

For all integrations

  • Identify the tool version and ensure it is compatible with BigPanda.

  • If integrating a monitoring tool, ensure it has the ability to send outbound event notifications.

  • Check that the tool has access to the internet to outbound event notifications.

  • Check that all security requirements (such as whitelisting) are met to send traffic outside the core network.

  • Review the BigPanda integration instructions and requirements for your tool.

For Open Integration Manager enabled integrations

  • Confirm that the monitoring event payload headers and body be customized.

  • Check that the event headers support org bearer token authentication.

  • Ensure event payload bodies can be formatted in JSON.

For standard Email Parser integrations

  • Configure email recipients to be sent to a BigPanda inbox.

  • Format email bodies into text or HTML.

  • Ensure that email templates remain consistent between event types.

Types of Integrations

BigPanda offers several types of integrations:

  • Monitoring integrations allow BigPanda to receive alerts from your monitoring systems, such as Nagios, SolarWinds, and AppDynamics. Many users start by integrating these systems.

  • Collaboration integrations allow you to share incidents from BigPanda with your co-workers through other systems such as Jira or Slack.

  • Changes integrations allow BigPanda to receive change notifications from your change systems, such as CloudTrail, Jenkins, ServiceNow, and Jira.

  • Topology integrations allow you to enrich alerts coming into BigPanda with topology information from configuration management, cloud and virtualization management, service discovery, APM, and CMDB tools.

Agent vs. Webhook Integrations

BigPanda has the flexibility to support both SaaS and on-premise monitoring tools.

Most SaaS tools (such as CloudWatch or New Relic) are integrated using Webhooks. Whenever the SaaS tool generates an alert, it posts an HTTP message directly to BigPanda. BigPanda listens to incoming messages and processes them.

Many on-premise tools are integrated using the BigPanda agent. The agent is a low-footprint daemon installed on the master host of your monitoring tool. It consumes alerts from the tool in real time, and then transmits them to BigPanda via SSL-encrypted HTTP calls.

The agent can require some additional steps to configure. To learn more about using the agent, see the BigPanda Agent documentation.

Standard vs. Custom Integrations

Standard integrations are any integration that has a tile in BigPanda, or uses the Open Integration Manager or Email Parser. See the diagram below for more information about the difference between standard and custom integrations.

https://files.readme.io/7b3d6eb-Custom_vs_Standard_Chart_11x8.5_FNL.jpg

Deciding Between Standard or Custom Integrations

To learn about options relating to custom integrations, contact your BigPanda support or your onboarding team.

Agent vs. Webhook Integrations

BigPanda has the flexibility to support both SaaS and on-premise monitoring tools.

Most SaaS tools (such as CloudWatch or New Relic) are integrated using Webhooks. Whenever the SaaS tool generates an alert, it posts an HTTP message directly to BigPanda. BigPanda listens to incoming messages and processes them.

Many on-premise tools are integrated using the BigPanda agent. The agent is a low-footprint daemon installed on the master host of your monitoring tool. It consumes alerts from the tool in real time, and then transmits them to BigPanda via SSL-encrypted HTTP calls.

The agent can require some additional steps to configure. To learn more about using the agent, see the BigPanda Agent documentation.

Standard vs. Custom Integrations

Standard integrations are any integration that has a tile in BigPanda, or uses the Open Integration Manager or Email Parser. See the diagram below for more information about the difference between standard and custom integrations.

https://files.readme.io/7b3d6eb-Custom_vs_Standard_Chart_11x8.5_FNL.jpg

Deciding Between Standard or Custom Integrations

To learn about options relating to custom integrations, contact your BigPanda support or your onboarding team.

Monitoring Integrations

The following standard monitoring integrations are available:

Product

Supported Versions

Type

Authentication Type

Airbrake

SaaS Deployments (Deprecated)

Webhook

API Fortress

SaaS and On-Premise Deployments

Webhook

Org Bearer Token

AppDynamics

4.1+; On-Premise, Dedicated SaaS Deployments

Webhook

Org Bearer Token

AppOptics

SaaS Deployments

Webhook

Org Bearer Token

Azure Monitor

SaaS Deployments

Webhook

Org Bearer Token

CA Spectrum

9.4.x

Spectrum Scripts

Org Bearer Token

Catchpoint

SaaS Deployments

Webhook

Org Bearer Token

Cisco Meraki

SaaS Deployments

Webhook

Org Bearer Token

CloudWatch

SaaS Deployments

CloudFormation, Webhook

Org Bearer Token

Cribl

<= 4.0.4

Webhook

Org Bearer Token

Datadog

SaaS Deployments

Webhook

Org Bearer Token

Dynatrace APM

SaaS Deployments

Webhook

Org Bearer Token

Entuity

v19 to v21

Webhook

Org Bearer Token

Grafana

Grafana >= v5.0.0

Webhook

Org Bearer Token

Icinga

1, 2

Agent

Org Bearer Token

Librato

SaaS Deployments

Webhook

Org Bearer Token

Logentries

SaaS Deployments

Webhook

Org Bearer Token

LogicMonitor

SaaS Deployments

Webhook

Org Bearer Token

Logscale

1.98.0

Webhook

Org Bearer Token

Logz.io

SaaS Deployments

Webhook

Org Bearer Token

Nagios

3, 4

Agent

Org Bearer Token

Nagios XI

4, 5

Agent

Org Bearer Token

New Relic

SaaS Deployments

Webhook

Org Bearer Token

Opsview

Nagios-Compatible Versions (Version 5 and older)

Agent

Org Bearer Token

Oracle Enterprise Manager

12c, 13c

Email Parser

N/A

Panopta

SaaS Deployments (Depreciated)

Webhook

Pingdom

SaaS Deployments

Webhook

Org Bearer Token

Prometheus

Alertmanager >= v0.16.0

Webhook

Org Bearer Token

PRTG

14.4+; English Language (Only)

Webhook

Org Bearer Token

ScienceLogic

< 11.3.0

Action Script/Webhook

Org Bearer Token

SCOM (Microsoft System Center Operations Manager)

System Center 2012 R2 and 2016

Webhook

Org Bearer Token

Scout

SaaS Deployments (Deprecated)

Webhook

Sematext

SasS Deployments (Deprecated)

Webhook

 

Sensu

0.12+

Webhook

Org Bearer Token

Sentry

SaaS Deployments

Webhook

Org Bearer Token

Site24x7

SaaS Deployments

Webhook

Org Bearer Token

SiteScope

<=2022.11

Webhook

Org Bearer Token

SNMP (Simple Network Management Protocol)

v1, v2, v2c

Daemon and Agent

Org Bearer Token

SolarWinds

Orion Server, Versions 2015.1+; Network Performance Monitor (NPM) 10.4+

Webhook

Org Bearer Token

Splunk

Splunk Enterprise, Splunk Cloud <= 9.0

Native App (v6.3+)

Action Script (pre v6.3)

Org Bearer Token

SQL Sentry

<= 2023.2.9

Webhook

Org Bearer Token

StatusCake

SaaS Deployments (Deprecated)

Webhook

Sumo Logic

SaaS Deployments

Webhook

Org Bearer Token

ThousandEyes

SaaS Deployments

Webhook

Org Bearer Token

Tivoli EIF

7, 8

Agent

Org Bearer Token

VMWare Aria

<=8.10

Webhook

Org Bearer Token

Wavefront

SaaS Deployments

Webhook

Org Bearer Token

Zabbix

2.2, 3.0, 3.2

Agent

Org Bearer Token

Zenoss

Zenoss Core 4, 5, 6

Agent

Org Bearer Token

Collaboration Integrations

The following standard monitoring integrations are available:

Product

Supported Versions

Type

Authentication Type

Ansible Automation Platform

<= v2.4

Webhook

Org Bearer Token

Asana

SaaS Deployments

API

User API Key

Jira

Jira Cloud <= 9.4

API

User API Key and Org Bearer Token

OpsGenie

SaaS Deployments

API

User API Key

PagerDuty

SaaS Deployments

API

Org Bearer Token

ServiceNow

BigPanda App v2.8+ - Xanadu, Washington, Vancouver, Utah, Tokyo, San Diego, Rome, Quebec, Paris, Orlando, New York, Madrid, London, Kingston, Jakarta, Istanbul

BigPanda App v2.3-2.7 - Washington, Vancouver, Utah, Tokyo, San Diego, Rome, Quebec, Paris, Orlando, New York, Madrid, London, Kingston, Jakarta, Istanbul

BigPanda App <v2.3 - Quebec, Paris, Orlando, New York, Madrid, London, Kingston, Jakarta, Istanbul

API

User API Key and Org Bearer Token

Slack

SaaS Deployments

API

Org Bearer Token

xMatters

<= Jun/Jul 2022

API

User API Key

Changes

Product

Supported Versions

Type

Authentication Type

CloudTrail

SaaS

API

User API Key

Jenkins

1.546 or later

Native Plugin, Webhook

User API Key

Jira Changes

Jira Cloud, Jira Server

Native App, Webhook

User API Key and Org Bearer Token

ServiceNow Changes

Tokyo (v2.3+), San Diego (v2.3+), Rome (v2.3+), Quebec, Paris, Orlando, New York, Madrid, London, Kingston, Jakarta, Istanbul

Native App, API

User API Key and Org Bearer Token

Topology

Product

Supported Versions

Type

Authentication Type

Datadog Topology

SaaS

API

Org Bearer Token

Dynatrace Topology

SaaS Deployments

API

Org Bearer Token

ServiceNow CMDB

Tokyo (v2.3+), San Diego (v2.3+), Rome (v2.3+), Quebec, Paris, Orlando, New York, Madrid, London, Kingston, Jakarta, Istanbul

Native App, API

User API Key and Org Bearer Token

vCenter Inventory

vCenter Server 6.5 update 2 and newer

Native Plugin

Org Bearer Token

Troubleshoot an Integration

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

If an issue or problem occurs with integration payloads, BigPanda allows you to troubleshoot errors and issues right in the console. BigPanda will automatically mark integrations with failed payloads on the Integrations tab. Review these errors to identify and troubleshoot integration issues so that no events are missed.

Limited Time Frame

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

Troubleshoot an Integration

Integration errors can be seen and investigated on the Integrations tab.

Any integration that has a failed payload in the last seven days will list the number of errors on the integration ribbon. If a payload failed within the last 24 hours, this number will be highlighted in red.

To troubleshoot an integration:

  1. Navigate to the Integrations tab.

  2. The Integrations List shows the name and recent activity for each installed integration.

    Multiple Integrations for a Single Tool

    If you’ve configured multiple integrations for the same tool, each integration is listed separately in the left pane.

  3. (Optional) Filter the list by searching for an integration name.

  4. Click the desired integration to see more details in the right pane, including App Key, ID, Errors, and more.

  5. Click Troubleshooting to view details on errors. The Errors field lists a count of recent event payloads that triggered issues on arrival in BigPanda.

Integration Status

Integrations that have not yet received data are marked with an orange No Data label.

Error Details

The Integrations Troubleshooting log only tracks errors that are received by BigPanda. Errors that fail to send or that cannot be parsed by the BigPanda pipeline will not appear in the list.

Error count and details are only maintained for seven days.

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. The troubleshooting log can be filtered by searching for an existing payload description, or by filtering by date.

Identifying when the integration stopped working

The Last Event label can help you identify timelines using the time the last successful event was received. For integrations that have never received a payload, the Last Event will show the creation time of the integration.

https://files.readme.io/64ea0b2-Troubleshooting_popup_-_screenshot_for_docs2.png

The Troubleshooting Log

Payload Details

To view the payload in a code editor of your choice, click Copy to add the payload to your clipboard.

Once the issue has been identified, reconfigure the source tool or the integration to fix the parsing errors.

Error Types

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.

Troubleshoot an Integration

Integration errors can be seen and investigated on the Integrations tab.

Any integration that has a failed payload in the last seven days will list the number of errors on the integration ribbon. If a payload failed within the last 24 hours, this number will be highlighted in red.

To troubleshoot an integration:

  1. Navigate to the Integrations tab.

  2. The Integrations List shows the name and recent activity for each installed integration.

    Multiple Integrations for a Single Tool

    If you’ve configured multiple integrations for the same tool, each integration is listed separately in the left pane.

  3. (Optional) Filter the list by searching for an integration name.

  4. Click the desired integration to see more details in the right pane, including App Key, ID, Errors, and more.

  5. Click Troubleshooting to view details on errors. The Errors field lists a count of recent event payloads that triggered issues on arrival in BigPanda.

Integration Status

Integrations that have not yet received data are marked with an orange No Data label.

Error Details

The Integrations Troubleshooting log only tracks errors that are received by BigPanda. Errors that fail to send or that cannot be parsed by the BigPanda pipeline will not appear in the list.

Error count and details are only maintained for seven days.

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. The troubleshooting log can be filtered by searching for an existing payload description, or by filtering by date.

Identifying when the integration stopped working

The Last Event label can help you identify timelines using the time the last successful event was received. For integrations that have never received a payload, the Last Event will show the creation time of the integration.

https://files.readme.io/64ea0b2-Troubleshooting_popup_-_screenshot_for_docs2.png

The Troubleshooting Log

Payload Details

To view the payload in a code editor of your choice, click Copy to add the payload to your clipboard.

Once the issue has been identified, reconfigure the source tool or the integration to fix the parsing errors.

Error Types

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.

Next Steps

Find your way around the Integration Tab

Learn how to Troubleshoot an Integration

View a list of BigPanda's Standard Integrations

In this section: