Using Statuspage.io

We understand the importance of keeping you informed about the status of our services. To ensure transparency and maintain your trust, we use Statuspage.io to provide you with real-time updates on our system's performance and any incidents that may occur. This easy-to-follow guide will help you understand how to use our Status Page to stay informed.

Accessing our Status Page

  1. To access our Status Page, simply click the following link or copy and paste it into your web browser: https://shiftboard-schedulepro.statuspage.io/

  1. Bookmark this link, so you can quickly access it whenever you want to check the status of our services.

Understanding the Status Page

Once you're on our Status Page, you'll see several sections.

  • System Status: This section displays the overall status of our services, such as "All Systems Operational" or "Partial System Outage."
  • Components: This section lists the different components of our services (e.g., Scheduling, API, System Access) and their respective statuses. A green checkmark means the component is operational, while a red exclamation mark indicates there's an issue.
  • Incident History: This section provides a list of past incidents, including their date, duration, and a brief description.

Subscribing to Updates

To receive real-time notifications about our system's status, you can subscribe to updates through E-mail, Slack, Phone Text Messages, Webhooks, or an Atom Feed/RSS Feed. To subscribe to those updates, choose one or more of the following options, on the top-right corner of the Status Page.

  • E-mail: Enter your email address in the provided field and click Subscribe.
  • Slack: Choose the Slack tab in the subscription window and follow the instructions to authorize and add our status updates to your desired Slack channel.
  • Phone Text Messages: Select the Phone tab from the menu, enter your phone number in the provided field, and click Subscribe.
  • Atom Feed or RSS Feed: If you prefer to receive updates through an Atom Feed or RSS Feed, click the Subscribe to Updates button, and then choose the Atom/RSS Feed tab in the subscription window. Copy the provided feed URL and add it to your favorite feed reader application or service.
  • Webhooks: To receive updates via Webhooks, you need to have an HTTP(S) endpoint that can receive POST requests. Select the Webhook tab, enter your endpoint in the provided field, and click Subscribe. Our servers will send notifications to this registered endpoint whenever there's an update. Need help with the Webhooks notifications? Refer to section 4 of this document.

Webhooks Notifications

Webhook notifications are a bit like messages you get from a mobile app. These messages are sent from the app to your phone to inform you about something. Our system with the webhooks works the same way, it informs you about issues in our system, by letting you know about changes in the current status of our services.

When we're experiencing any issues (which we call "incidents"), we'll send a message about that. The message will tell you what the issue is, what we're doing about it, and when you can expect it to be resolved.

These messages, or notifications, come in a certain format. Your IT manager will create a way to interpret these messages and react accordingly, which helps you stay updated in real-time about the status of our services.

In a nutshell, webhook notifications are your ally in staying informed about the latest happenings with our service without having to check the status page every time. They work behind the scenes, making sure you're informed, so you can focus on your day-to-day tasks.

Webhook Setup

Webhooks are HTTP POST requests that our servers send to the registered endpoint. Endpoints are required to respond with a 2xx response code (3xx is considered a failure) and must respond within 30 seconds of initial connection.

Create a URL in your infrastructure to receive these HTTP POST requests. The body will contain the incident information, such as in the JSON sample below.

{

   "meta":{

      "unsubscribe":"http://statuspagewebhook.shiftboard.com:5000/?unsubscribe=jwjsi38d92",

      "documentation":"https://shiftboard-schedulepro.statuspage.io/customer-notifications/webhooks/"

   },

   "page":{

      "id": "j2mfxwj97wnj",

      "status_indicator": "critical",

      "status_description": "Major System Outage"

   },

   "incident":{

      "backfilled":false,

      "created_at":"2013-05-29T15:08:51-06:00",

      "impact":"critical",

      "impact_override":null,

      "monitoring_at":"2013-05-29T16:07:53-06:00",

      "postmortem_body":null,

      "postmortem_body_last_updated_at":null,

      "postmortem_ignored":false,

      "postmortem_notified_subscribers":false,

      "postmortem_notified_twitter":false,

      "postmortem_published_at":null,

      "resolved_at":null,

      "scheduled_auto_transition":false,

      "scheduled_for":null,

      "scheduled_remind_prior":false,

      "scheduled_reminded_at":null,

      "scheduled_until":null,

      "shortlink":"http://j.mp/18zyDQx",

      "status":"monitoring",

      "updated_at":"2013-05-29T16:30:35-06:00",

      "id":"lbkhbwn21v5q",

      "organization_id":"j2mfxwj97wnj",

      "incident_updates":[

         {

            "body":"A fix has been implemented and we are monitoring the results.",

            "created_at":"2013-05-29T16:07:53-06:00",

            "display_at":"2013-05-29T16:07:53-06:00",

            "status":"monitoring",

            "twitter_updated_at":null,

            "updated_at":"2013-05-29T16:09:09-06:00",

            "wants_twitter_update":false,

            "id":"drfcwbnpxnr6",

            "incident_id":"lbkhbwn21v5q"

         },

         {

            "body":"We are waiting for the cloud to come back online and will update when we have further information",

            "created_at":"2013-05-29T15:18:51-06:00",

            "display_at":"2013-05-29T15:18:51-06:00",

            "status":"identified",

            "twitter_updated_at":null,

            "updated_at":"2013-05-29T15:28:51-06:00",

            "wants_twitter_update":false,

            "id":"2rryghr4qgrh",

            "incident_id":"lbkhbwn21v5q"

         },

         {

            "body":"The cloud, located in Norther Virginia, has once again gone the way of the dodo.",

            "created_at":"2013-05-29T15:08:51-06:00",

            "display_at":"2013-05-29T15:08:51-06:00",

            "status":"investigating",

            "twitter_updated_at":null,

            "updated_at":"2013-05-29T15:28:51-06:00",

            "wants_twitter_update":false,

            "id":"qbbsfhy5s9kk",

            "incident_id":"lbkhbwn21v5q"

         }

      ],

      "name":"Virginia Is Down"

   }

}

Monitoring Incidents

If there's an ongoing incident, you'll see it highlighted on our Status Page. Click on the incident title to see more details, such as a description of the issue, the affected components, and any updates from our team.

Conclusion

Our Status Page is an essential tool for staying informed about the performance and availability of our services. We encourage you to bookmark the page, subscribe to updates, and check it occasionally. If you have any questions or need assistance, please don't hesitate to contact our support team (www.shiftboard.com/contact/customer-support/).

We are committed to providing you with reliable, high-quality services and keeping you well-informed along the way.


How did we do?


Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)