Skip to main content

Monitoring

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

If you do not see your tool listed below, it may still be able to integrate with BigPanda using the Alerts Rest API, Open Integration Manager, or the Email Parser.

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

Install an Alerts Rest API Integration

Easily push custom alert types to BigPanda using our REST API for Alerts. View your custom alerts alongside insights from the rest of your monitoring systems, so you can understand and respond faster to critical issues.

Open Integration Manager

Normalization is a key tool to reducing event noise and reaching faster resolution times. If possible, we recommend connecting tools through the Open Integration Manager Alerts Rest API instead of the basic Alerts Rest API.

The Alerts Rest API can be configured with standard restful API calls or powershell.

Compare supported data fields and best practices in the Alerts Rest API documentation.

Alerts Rest API

Integrate a monitoring tool using the basic alerts REST API.

Create an App Key

Create an app key in BigPanda.

Integration specific

You'll need a separate app key for each integrated system.

https://files.readme.io/9865f2f-Integrations_App_Key_Creation.jpg

App Key Configuration in BigPanda

Make a REST Call From Your Monitoring System

Configure the integrated system to call the Alerts API endpoint:

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

Use the following HTTP headers:

Authorization: Bearer <Your Org Bearer Token>
Content-Type: application/json

The JSON payload can contain all or a subset of the following fields:

  • app_key: Application key from the first step.

  • status: Status of the alert. One of [ ok, critical, warning, acknowledged ].

  • host, service, application: Main object that caused the alert. Can be the associated host or, if a host isn’t relevant, a service or an application. If you want to include more than one of these fields, consider specifying the primary and secondary properties.

  • timestamp: (Optional) Time that the alert occurred in unix format (UTC timezone). If the time is not specified, the value defaults to the current time.

  • check: (Optional) Secondary object or sub-item that caused the alert (often shown as an incident subtitle in BigPanda).

  • description: (Optional) Additional free-form text information about this alert.

  • cluster: (Optional) Server cluster or logical host-group from which the alert was sent. This value is used to correlate alerts into high-level incidents.

  • Additional attributes: (Optional) Additional information you want to have available in the BigPanda Incident Dashboard. You can add any number of custom JSON attributes with a string value to the payload.

For information on how to send multiple alerts or configure primary and secondary properties, see the Alerts API documentation.

Below is an example of a full payload:

{
"app_key": "<Your App Key>",
"status": "critical",
"host": "production-database-1",
"timestamp": 1402302570,
"check": "CPU overloaded",
"description": "CPU is above upper limit (70%)",
"cluster": "production-databases",
"my_unique_attribute": "my_unique_value"
}

Create a Test Alert

To validate that everything is configured correctly, send a test alert by running the following command in Shell:

curl -XPOST -H "Content-Type: application/json" \
-H "Authorization: Bearer <Your Org Bearer Token>" \
https://api.bigpanda.io/data/v2/alerts \
-d '{ "app_key": "<Your App Key>", "status": "critical", "host": "production-database-1", "check": "CPU overloaded" }'

The alert should now appear in the Incidents dashboard. Close the alert by running:

curl -XPOST -H "Content-Type: application/json" \
-H "Authorization: Bearer <Your Org Bearer Token>" \
https://api.bigpanda.io/data/v2/alerts \
-d '{ "app_key": "<Your App Key>", "status": "ok", "host": "production-database-1", "check": "CPU overloaded" }'

Alert Rest API with PowerShell

Integrate a monitoring tool with REST API using PowerShell.

Create an App Key

Create an app key in BigPanda.

Integration specific

You'll need a separate app key for each integrated system.

https://files.readme.io/9865f2f-Integrations_App_Key_Creation.jpg

App Key Configuration in BigPanda

Send an Alert

To validate that everything is configured correctly, send a test alert by running the following command in PowerShell:

$json = @{ app_key = "<Your App Key>"; status = "critical"; alert = "Hello from PowerShell"; host = "testing" }
$url = "https://api.bigpanda.io/data/v2/alerts"
$headers = @{"Authorization" = "Bearer <Your Org Bearer Token>"}
Invoke-RestMethod $url -Method Post -Headers $headers -Body $json -UseBasicParsing

The alert should now appear in the Incidents dashboard. Close the alert by running:

$json = @{ app_key = "<Your App Key>"; status = "ok"; alert = "Hello from PowerShell"; host = "testing" }
$url = "https://api.bigpanda.io/data/v2/alerts"
$headers = @{"Authorization" = "Bearer <Your Org Bearer Token>"}
Invoke-RestMethod $url -Method Post -Headers $headers -Body $json -UseBasicParsing