From 4dde92040159d589c0f45abd3c30c5c27a18fdf6 Mon Sep 17 00:00:00 2001 From: Patrick Cieplak Date: Tue, 20 Aug 2013 15:36:52 -0700 Subject: [PATCH 1/2] first draft blog post --- ...013-08-19-balanced-status-notifications.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 _posts/2013-08-19-balanced-status-notifications.md diff --git a/_posts/2013-08-19-balanced-status-notifications.md b/_posts/2013-08-19-balanced-status-notifications.md new file mode 100644 index 0000000..89185f9 --- /dev/null +++ b/_posts/2013-08-19-balanced-status-notifications.md @@ -0,0 +1,19 @@ +--- +layout: post +author: Patrick Cieplak +title: "Balanced Status Notifications" +tags: +- balanced +- notifications +- Twilio +- Finite State Machines +- Google App Engine +--- + +## Receive Balanced Status Notifications via SMS, Email, and Twitter + +As an open company, we strive to be transparent in everything we do, from opening up our internal discussions on GitHub to open-sourcing our dashboard. This week we released a real-time notification system for our system status that will alert subscribers of any incidents or downtime for the Balanced API, balanced.js, and for the Balanced dashboard. Customers can now receive notifications via email, text message, and Twitter. + +![Image](https://raw.github.com/balanced/balanced.github.com/master/img/notifications.png) + +Justin, a.k.a. [NodeSocket](https://github.com/nodesocket), modeled the notification system as a finite state machine, which can be seen [here on GitHub](https://github.com/balanced/status.balancedpayments.com/blob/master/situation/models.py#L77). Essentially, the system polls the API, the dashboard, and balanced.js minute by minute to check their states, and sends the proper notifications on state transitions. SMS messages sent through Twilio, emails are sent through Google App Engine, and tweets are sent, naturally, htrough Twitter. \ No newline at end of file From bea33407eda22d41f36bff9663fbd307bf7170b0 Mon Sep 17 00:00:00 2001 From: Patrick Cieplak Date: Sun, 25 Aug 2013 15:51:52 -0700 Subject: [PATCH 2/2] typo --- _posts/2013-08-19-balanced-status-notifications.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2013-08-19-balanced-status-notifications.md b/_posts/2013-08-19-balanced-status-notifications.md index 89185f9..4ef5cf8 100644 --- a/_posts/2013-08-19-balanced-status-notifications.md +++ b/_posts/2013-08-19-balanced-status-notifications.md @@ -16,4 +16,4 @@ As an open company, we strive to be transparent in everything we do, from openin ![Image](https://raw.github.com/balanced/balanced.github.com/master/img/notifications.png) -Justin, a.k.a. [NodeSocket](https://github.com/nodesocket), modeled the notification system as a finite state machine, which can be seen [here on GitHub](https://github.com/balanced/status.balancedpayments.com/blob/master/situation/models.py#L77). Essentially, the system polls the API, the dashboard, and balanced.js minute by minute to check their states, and sends the proper notifications on state transitions. SMS messages sent through Twilio, emails are sent through Google App Engine, and tweets are sent, naturally, htrough Twitter. \ No newline at end of file +Justin, a.k.a. [NodeSocket](https://github.com/nodesocket), modeled the notification system as a finite state machine, which can be seen [here on GitHub](https://github.com/balanced/status.balancedpayments.com/blob/master/situation/models.py#L77). Essentially, the system polls the API, the dashboard, and balanced.js minute by minute to check their states, and sends the proper notifications on state transitions. SMS messages sent through Twilio, emails are sent through Google App Engine, and tweets are sent, naturally, through Twitter.