Idempotence for notifications

[MooseQuest]

The provided platforms (Slack and JIRA) can be used if owner meets requirements. Possible to develop adapters for notification services that allow user to either develop, or send constructed .json to any endpoint?

This would prove valuable for different types of gear that might lie underneath. Construct the errors and process, and hand that off to the adapters or modules for the vendor. Specify those in the configuration, with a set of static configurations to be passed. Pointers can be used or objects, or simply the functions there of.

The idea here, is that no matter the call or notification we receive the same message each time, which can be passed to the necessary next stage. It should help also, if you have a noisy or something that sends multiple messages. Inherent by the definition, but the idea is, if we receive the the alert multiple times, don't create multiple tickets.

[cholcombe973]

This is partially handled in the new postgres database that bynar uses now. It won't create another jira ticket if one is already in progress for a particular device. I'm not sure but that might take care of the slack issue as well. I'll have to check again.