Background

BigPanda.io provides AI-powered ITOps and Incident Management to many enterprise customers. With MarketSpark's Command Center software release on February 24th, 2025, our customers are now able to direct their Location Offline and Power Source notifications to the BigPanda Send Alerts API.

Purchasing

To enable the BigPanda feature for your Organization, please reach out to MarketSpark's Sales team. This feature is not enabled by default.

Configuration

Once enabled, entitled customers will see a new BigPanda card on their Organization overview page within Command Center. 

This card indicates the state of notifications (Enabled or Disabled) as well as the status of your BigPanda "Org Token" and "App Key" entry - green if enabled and complete.

Control over the Notifications and management of the Token is controlled using the settings modal icon in the upper-right hand corner of the BigPanda card. The modal provides:

Events

When enabled, and your Organization is in good standing with MarketSpark, and also not in our Pilot phase, Operational Locations will send their location and power status events into BigPanda's Send Alerts API.

The following state change events are sent:

Location Online -> Location Offline:

-data '{ "app_key": "<APP KEY>",  "status": "critical",  "host": "$MarketSpark_Location_Identifier",  "application": "Location Offline",  "description": "The location has gone offline and cannot make or receive telephone calls",  "incident_identifier": "$MarketSpark_Ticket_ID",  "primary_property": "host",  "secondary_property": "application"}'

Location Online -> Location Trouble:

-data '{ "app_key": "<APP KEY>",  "status": "warning",  "host": "$MarketSpark_Location_Identifier",  "application": "Location Trouble",  "description": "The location is experiencing trouble and some port(s) cannot make or receive telephone calls",  "incident_identifier": "$MarketSpark_Ticket_ID",  "primary_property": "host",  "secondary_property": "application"}'

Power Source AC (Mains) -> Power Source DC (Battery):

-data '{ "app_key": "<APP KEY>",  "status": "warning",  "host": "$MarketSpark_Location_Identifier",  "description": "AC mains power is offline. The location has switched to backup (DC) battery power",  "application": "Power Source Change",  "incident_identifier": "$MarketSpark_Ticket_ID",  "primary_property": "host",  "secondary_property": "application"}'

Location Offline -> Location Online:

-data '{ "app_key": "<APP KEY>",  "status": "ok",  "host": "$MarketSpark_Location_Identifier",  "description": "The location is now online and can successfully make and receive telephone calls",  "application": "Location Online",  "incident_identifier": "$MarketSpark_Ticket_ID",  "primary_property": "host",  "secondary_property": "application"}'

Location (In) Trouble -> Location Online:

-data '{ "app_key": "<APP KEY>",  "status": "ok",  "host": "$MarketSpark_Location_Identifier",  "description": "Trouble has cleared and all port(s) can make or receive telephone calls",  "application": "Location Online",  "incident_identifier": "$MarketSpark_Ticket_ID",  "primary_property": "host",  "secondary_property": "application"}'

Power Source DC (Battery) -> Power Source AC (Mains):

-data '{ "app_key": "<APP KEY>",  "status": "ok",  "host": "$MarketSpark_Location_Identifier",  "description": "AC mains power is online. The location is no longer on backup (DC) battery power",  "application": "Power Source Change",  "incident_identifier": "$MarketSpark_Ticket_ID",  "primary_property": "host",  "secondary_property": "application"}'

Each event includes the name of the Location within Command Center ($MarketSpark_Location_Identifier) and the Ticket ID used by MarketSpark's own Support team for incident tracking purposes ($MarketSpark_Ticket_ID) as well as status (severity), a description, and the application.