Sensu is an open-core monitoring platform that empowers organizations to compose comprehensive monitoring & telemetry solutions that meet their unique business requirements. By providing a platform to build upon, Sensu enables you to focus on what to monitor and measure, rather than how.

Supported Versions


Authentication Type



Bearer Token

Key Features

  • Execute Service Checks - Sensu can monitor application and system services, detecting those in an unhealthy state. Service checks can be used, for example, to determine if a service like HAProxy is up or down, or if a web application is responding to requests.

  • Collect Metrics - Sensu simplifies the process of gaining insightful metrics from complex distributed systems. The Sensu check format is composed of an exit status code, and an arbitrary payload (e.g. message string, PerfData, JSON, animated cat GIFs, etc). This simplicity provides a single platform to collect every metric data point that is meaningful to your business.

  • Dynamic Client Registry - Sensu's use of the pubsub pattern of communication allows for automated registration & de-registration of ephemeral systems — allowing you to dynamically scale your infrastructure up and down without fear of generating false-positive alert storms.

  • Send Notifications - Sensu notifies your team about events before your customers do, using services such as Email, PagerDuty, Slack, IRC, etc.

  • Documented API - Sensu’s API provides access to event and client data, the ability to request check executions, and resolve events. The API also provides a key/value store which can be leveraged to extend Sensu's functionality in a variety of ways.

  • Self-Service Monitoring - Sensu provides support for centralized and decentralized (or distributed) monitoring, enabling operations teams to maintain a standard service level for the entire organization without placing unnecessary restrictions on developers. Give your users access to monitoring without relinquishing control.

  • Secure Connectivity - Sensu leverages transports that offer SSL encryption, authentication, and granular ACLs. Sensu's connections traverse complex network topologies, including those that use NAT and VPNs.

  • External Input - Sensu’s monitoring agent (sensu-client) provides a TCP and UDP socket that can accept external JSON data. Applications can leverage this interface to report errors directly to Sensu or ship application-specific metric data.

Uninstalling Sensu

You must update the configuration file on the Sensu server to stop sending alerts to BigPanda.


  • Manually resolve any open incidents related to the integration to remove them from your incident feed. Optionally, remove any additional data in BigPanda. For example, modify or remove any Environments or AutoShare rules that reference the integration.

  • Obtain access to the Sensu server.


  1. On the Sensu server, go to the checks configuration directory. By default, the directory is located at: /etc/sensu/conf.d

  2. For each check, delete the BigPanda handler. For example, you would remove the "bigpanda" handler from this check definition.

  "checks": {
  "<check_name>": {
  "handlers": ["<handler_1_name>", "<handler_2_name>", ..., "bigpanda"]
  1. Remove the Bigpanda Handler and configuration files, which are located at:
  • /etc/sensu/handlers/bigpanda.rb

  • /etc/sensu/conf.d/handler_bigpanda.json

  1. Restart the Sensu server by running the following command:

sudo /etc/init.d/sensu-server restart


Delete the integration in BigPanda to remove the Sensu integration from your UI.