← Site Reliability

How to use status.banno.com

Prerequisites

To update status.banno.com a few things must be configured and installed.

Clone this repo

  • git clone git@github.com:Banno/status.banno.com.git

Ruby

Ruby should already be set up on your machine, and in theory all you should have to do is:

  • bundle install

AWS Command Line Utilities

AWS command line utilities and an AWS account are required to upload the changes to status.banno.com.

  • brew install awscli

  • AWS Acct Setup includes the AWS account configuration and shell variables required.

Shell Variables

export AWS_ACCESS_KEY_ID=""
export AWS_SECRET_ACCESS_KEY=""

Usage

Before you do anything

  • To make sure you have the latest copy of changes git pull in the folder where you cloned status.banno.com.

Check to make sure there’s not an existing status message in _posts/YYYY-MM-DD. By default https://status.banno.com will appear all green indicating all services are operational.
Default Status
If it doesn’t look like this skip ahead to the update section.

Start an incident

  • ./start_incident.sh "Name of Post" "Post content"
  • If the post is good push up:
    • ./deploy.sh && git push
  • If you need to edit the post before pushing it:
    • Should you need to edit the post before pushing it up, locate your post in ./_posts/ and edit it before running
      • ./deploy.sh && git commit -am "Status Update" && git push

If you’re not seeing the page update, it’s possible you’re viewing a cached version in your browser. In Chrome you can force a hard reload by pressing shift+command+r.

Stop an incident

This step will remove ALL EXISTING POSTS on status.banno.com and return the status to All services are operational

  • ./stop_incident.sh
  • ./deploy.sh && git push

Update Incident or Change Severity

  • Determine if your update should be appended to the current message or replace it entirely. If appending add the current time stamp as the first portion of your message.

  • Severity level translates to the color of the dot in the Message Title.

    • high=red, medium=yellow, low=grey

  • Locate your post file, in ./_posts/ and edit it with the editor of your choice.

    • If you want to open the folder so you can point and click, you can run open ./_posts/ in your terminal

  • ./deploy.sh && git commit -am "Status Update" && git push

Message templates

Banno Online

We are experiencing issues with Banno Online services where some users may experience errors when attempting to sync or trying to log in. Our engineers are engaged to resolve as quickly as possible. We will continue to update our status.

Our engineers have been alerted to a potential degradation of Banno Online services. Some users may experience latency or timeouts when trying to sync their apps or difficulty logging in. Our engineers are engaged and working to resolve this as quickly as possible. Updates will be posted to this site as they become available.

Our engineers received alerts indicating some mobile users may be experiencing latency or errors at this time. The appropriate teams are engaged and will resolve this issue as quickly as possible. Updates will be posted as they become available.

Remote Deposit Anywhere (RDA)

We have received alerts indicating that some users may be seeing latency or errors when depositing checks in mobile. The Banno team and EPS-RDA support are fully engaged and updates will be posted as quickly as possible.

Banno.com

We have received reports of errors signing into banno.com and our engineers are investigating the cause. We will keep our status updated as their work progresses.

Network/DataCenter issues

We are experiencing network connectivity issues out of our data center. Banno Online users would not be able to sync to update balances or move money. Inside the Admin, you will not be able to update any user settings at this time. Our engineers remain actively engaged and we will continue to update status as we know more.

Banno Content

Our engineers are investigating an issue with CMS sites being slow to respond. We will continue to keep our status updated.

All services are restored to full operation. However, our engineers remain fully engaged monitoring the health of our services stack and researching the underlying root cause.