[bisq-network/proposals] Bisq Network Monitor Revisited (#62)

Florian Reimair notifications at github.com
Mon Feb 11 12:27:01 UTC 2019


**Settled** is coming up! However, the only thing left in the list of features is the
## Notification
However, there is some decision making required.

### Options
- **Email:** Quite an evergreen. However, in order to make that work, we have to do some configuration.
  - First, we need a sender email address (e.g. monitoring at bisq.network)
  - Second, we need an SMTP service which accepts the aforementioned sender email address and does that in a way that common spam filters do not consider a message as junk!
  - Third, of course, we need credentials for that SMTP service so we can configure Grafana appropriately
  - Furthermore, we need the recipient addresses of all which should be notified of an alarm. However, mapping the recipients to the appropriate alarm has to be done manually (at least that is what I have learned by now). And that brings up some facts:
    - A seed node operator has to state an email address (which does compromise her identitiy)
    - Grafana knows these email addresses
    - Mating a faulty seed node alarm with the appropriate email address has to be done manually.
- **Slack:** As I am quite unfamiliar with Slack and there has been discussions on whether to switch to an other platform, I am not certain, that this is the best option. However, it is possible, given [that](https://api.slack.com/incoming-webhooks) can be done with our Slack plan.
- **others:** Grafana brings a [whole lot more options](http://docs.grafana.org/alerting/notifications/#all-supported-notifier) for alert notifications. Most notably IMHO is the [Webhook](http://docs.grafana.org/alerting/notifications/#webhook) option. However, I am not quite sure how to use it in order to make things easy.

### Quick solution
All in all, I have a feeling that the **Slack** option is the most suitable and versatile. The monitor reports to Slack in case any alarm triggers (e.g. a seed node failed). Slack takes care of the email notification to those who subscribed.
- On the plus-side, the seed node operators have an additional layer between them and their seed node address + one cannot easily determine which seed node is operated by whom. More generally, an independent (propably even subscriber-controlled) email notification platform seems like to scale much better as reconfiguring Grafana for each and every alarm.
- Downside is, that subscribers get notified even if the alarm is not meant for her. (Is there a notification filter on Slack?)
**Make or break**: does our Slack plan support [incoming webhooks](https://api.slack.com/incoming-webhooks)

What do you think?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/proposals/issues/62#issuecomment-462310214
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190211/55689e0f/attachment.html>


More information about the bisq-github mailing list