Skip to content
This repository has been archived by the owner on Sep 1, 2018. It is now read-only.

Implement error notifications for the automated script #18

Open
guiweber opened this issue May 17, 2017 · 3 comments
Open

Implement error notifications for the automated script #18

guiweber opened this issue May 17, 2017 · 3 comments

Comments

@guiweber
Copy link
Member

guiweber commented May 17, 2017

It would be nice to be notified when broken rules are detected when the fully automated script runs. Possible solutions:

  • Email: Require additional config and credential storage when deploying the script.
  • OS Notifications: Simpler, no credentials/configuration necessary. (https://github.com/mikaelbr/node-notifier). Need to test if notifications are persistant and can be made to be non cummulative (we only want the notification from the latest script run to be displayed). May take a while to see the notification in comparison to other more direct solutions.
  • SMS: Require additional config and credential storage. Free solutions may not be viable.
@pgaskin
Copy link
Contributor

pgaskin commented May 17, 2017

  • For email, I usually use sparkpost.
  • There could also be self-hosted push notifications or a web-based status page.
  • For sms, there is the free (limited plan), or the self-hosted version of textbelt: https://textbelt.com/

@Schokobecher
Copy link
Contributor

A chatbot for Slack or Telegram would also work - both require an account, but in Telegram you could a Channel where the Bot could announce updates to the registry without people spamming. Or you could subscribe to it. I would willing to build such a beauty.

@guiweber
Copy link
Member Author

@Schokobecher That's something I had not considered. Would you be able to make a Gitter chatbot? Not sure what API/functionality Gitter offers, but since were using it for our dev chat it would be good to have it there. We could add a channel for updates and one for errors and you can subscribe to the channel you're interested in.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

3 participants