Sensu + Flapjack Notifications

[Michael Holt]

Hi,

I've got Sensu and Flapjack configured but i'm having issues with notifications.

First issue was I wanted to go with using Amazon SNS for notifications, but can't seem to get it working (See: https://github.com/flapjack/flapjack/issues/829)

My second issue is since I couldn't get SNS working yet I decided to go the route of setting up SMTP Email Notifications.  I got it working, however when I cause a check to fail in Sensu I get a continuous stream of emails from Flapjack.  I've looked over all of the configuration as well as browsing through the github issues and this group and can't find anyone else with this issue.

Does anyone have any idea what's causing it?

[Michael Holt]

I got email working but still no luck with SNS

[Jesse Reynolds]

What did you find to be the cause of the continuous emails? 

403 from SNS would tend to indicate a lack of permission to access that function. I've not used SNS so not sure what the setup requirements are around roles, access etc.

--

---
You received this message because you are subscribed to the Google Groups "flapjack" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flapjack-proje...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Michael Holt]

The two things that I did was add this to the Contact media:

"interval": 1800,

and then I created a notification rule for the entity.

[

  {

    "id": "f75a7d5c-a91a-48d5-8612-94957f9ca95d",

    "tags": [

    ],

    "regex_tags": [

    ],

    "entities": [

      "sensu.rlcit.org"

    ],

    "regex_entities": null,

    "time_restrictions": null,

    "unknown_media": [

      "email",

      "sns"

    ],

    "warning_media": [

      "email"

    ],

    "critical_media": [

      "sns",

      "email"

    ],

    "unknown_blackhole": false,

    "warning_blackhole": false,

    "critical_blackhole": false,

    "links": {

      "contacts": [

        "21"

      ]

    }

  }

]

As far as SNS is concerned, I thought it was a permission issue as well with the IAM user but I gave the user full admin access to the entire account and it still didn't work