The SignifAI Community Hub

Welcome to the SignifAI Community Hub.
This is the place for you to find something new, express your thoughts, share and collaborate with other people. You'll find comprehensive guides and documentation to help you start working with SignifAI as quickly as possible, as well as support if you get stuck. Let's jump right in!


Integrating with Sensu monitoring platform

Integrating with Sensu

Sensu is a free open-source monitoring platform for your entire infrastructure. Sensu allows you to reuse monitoring checks and plugins from legacy monitoring tools like Nagios, Icinga, Zabbix, and many more.

With SignifAI, you can integrate Sensu to receive all the alerts in a single place, transform all your alerts into higher level issues which are automatically correlated, enriched and prioritized with any other data stream coming from your infrastructure. SignifAI will also run automatic anomaly detection on your Sensu streams of data as part of the integration.


We have written a dedicated Sensu plug-in which should be installed on the server. The plugin was certified and approved by the Sensu Open Source Community and is part of the plug-ins echo-system.


Assuming you have installed Sensu for your platform, you should be able to download our gem and install it. If you elect to use the "embedded" Ruby that comes with Sensu, you may want to (at least temporarily) add their Ruby to your PATH:

export EMBEDDED_RUBY="true"
export PATH="/opt/sensu/embedded/bin:$PATH"

Then, simply run:

sudo -E gem install sensu-plugins-signifai

Verify that which handler-signifai.rb gives you a valid path; if so, the plugin is installed and ready to use.


The SignifAI event handler is what Sensu calls a 'pipe' handler type, and you will need to configure it before it will forward events for you.

Write out a file, /etc/sensu/conf.d/signifai.json , that looks like this:

  "handlers": {
    "signifai": {
      "type": "pipe",
      "filter": "state_change_only",
      "command": "/opt/sensu/embedded/bin/handler-signifai.rb"
  "signifai": {
    "api_key": "YOUR_API_KEY"
  "sensu_plugin": {
    "disable_deprecated_filtering": true
  "filters": {
    "state_change_only": {
      "negate": false,
      "attributes": {
        "occurrences": "eval: value == 1 || ':::action:::' == 'resolve'"

Use your SignifAI Security Token For Sensu which can be found inside the Sensu Sensor section as your API Key

If you don't want to add the sensu_plugin setting because you are currently relying on the deprecated filtering (more information) you can, instead, set the "enable_deprecated_filtering": false per-check.

For any check whose results you want to forward to SignifAI, refer to this example:

  "checks": {
    "sleep": {
      "command": "/opt/sensu/embedded/bin/check-process.rb -p sleep",
      "subscribers": ["dev-sensu"],
      "handlers": ["signifai"],
      "interval": 60

You can use either the handler attribute with just the string "signifai" or you can use handlers with "signifai" alongside any other handlers you may need.

Need help with the integration?

Contact us at: [email protected] and we will be happy to help.

Updated about a year ago


Integrating with Sensu monitoring platform

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.