We're really excited to announce the launch of a free tool we're calling Better Error Pages! Better Error Pages is a mini-site that helps you build customizable 404, 500-level, and maintenance pages in 60 seconds.
Here's how it works:
- We ask you a few questions about your company (things like Homepage URL and Support Email Address).
- You have the opportunity to personalize the look of your error pages.
- When you're done, we'll send you a link to download the flat HTML files for your shiny new 404, 503 and Maintenance pages.
You should check out Better Error Pages for yourself...it's free!
About 6 months ago, we launched the first version of a feature called Multitenancy, allowing for customer-specific status updates . Over these 6 months we've been working closely with a handful of enterprise customers and are extremely excited to launch V2 with new functionality and a new name - Access Control.
C2FO is the world’s market for working capital and risk-free profit. C2FO is the only working capital exchange that allows companies to optimize their working capital positions in a live, bid/ask environment. Companies across the globe use C2FO to increase their operating income while simultaneously producing vital working capital flows to their supply chain.
User: Patrick McDonald, Director of Network Ops
Infrastructure: Manages 20 servers in AWS, 10 in SoftLayer’s data centers
Team: Full 24x7 on-call organization with a 3 person Ops team outside of Patrick
Since launching the first version of StatusPage two years ago, every page has come with an incident history page built in. The history page allows end users to scan through past incidents, giving them a sense of overall company transparency, incident severity levels, and incident frequency. While the current history page does a good job of showcasing a company's transparency, we received several requests from customers to let end users filter through the history based on component(s).
Finding The Right Information Using Incident Filtering
Today, we're launching Incident Filtering for all Business customers so that finding incident history based on relevant components is a breeze. Instead of scrolling through the whole incident history list, end users can now pick and choose the history that they care to see. As an example, a typical business user of a product may only need to view incidents affecting a dashboard or portal, while an API user may only care to filter for incidents affecting an API.
Enable Component Subscriptions
To get started, you'll first need to enable Component Subscriptions within the management portal.
Associate Incidents with Components
With Component Subscriptions enabled, you'll now be able to associate incidents with whichever component(s) are affected during an outage.
Filter based on component
By choosing which components are affected by an incident, we'll be able to notify the right subscribers and also let end users filter through your page's incident history.
Shoot us a note at email@example.com if you have any questions or feedback!
Over the past few weeks we've been beta testing Component Groups and are happy to release the functionality to all users today. Here's a quick look at a few use cases.
There's a good chance your software relies on other external services to work on a day to day basis. For StatusPage.io, mission critical services include AWS for hosting, Mailgun for email notifications, and Twilio for SMS notifications. One perfect use case for Component Groups is taking any 3rd-Party Components that you've enabled and bundling them under a 3rd Party Services group as Datadog has done here.
As a CDN like CloudFlare or a hosting provider, your status page is most likely broken out by data center region. Within each region, there may be a varying amount of individual data centers. Instead of having to list each individual data center out on the page, Component Groups lets you group these data centers together into the appropriate region, keeping your page clean and easily accessible to end customers. Take a look at CloudFlare's status page as a great example.
One common use case for grouping similar components together is on the feature level. Using Raven Tools, an internet marketing software company, as an example, you'll see that individual features such as Campaigns, Email Metrics, and Research Central are broken out into their own groupings. This type of implementation makes sense when each feature's sub-components individually could have issues without impacting the entire application.
Internal User Groups
Many of our customers use StatusPage.io internally as the definitive source of status information and notifications for employees. While most of these companies take advantage of Component Subscriptions to let employees opt-in to relevant notifications, until now, the status page displays mostly consisted of long listings of internal components. To make for a better and logical end user experience, you should think about grouping components by end user group, such as customer support, sales, executives, or engineering.
Component Groups are accessible for all StatusPage.io subscriptions. To get started, take a read over the knowledge base article and then head to Components within your dashboard. If you have any questions or feedback, shoot us a note at firstname.lastname@example.org!
StatusPage.io is now an official HipChat add-on, eliminating the need to paste API keys and allowing all HipChat users to install the integration in just a few clicks. Using the add-on, users can automatically send status information such as component and incident updates directly into designated HipChat rooms, keeping everyone in a company up to date with system status while letting engineering focus on fixing the problem at hand.
"StatusPage.io's HipChat integration is by far the best way to keep our team updated when we're dealing with trouble. Things can get hectic at these times and it's great having the notifications in our room where they will not be missed." - Garret Heaton, Co-founder of HipChat
A few example incident updates piped directly into HipChat.
In order to further improve our first time user experience, we're moving to an "Add-on Store" model of selectively hiding features. The Add-on Store will allow you to enhance or turn on features that aren't part of the core experience of the product.
Feature Creep vs. First Run User Experience
Now that the company is a little over a year old, we're starting to feel "feature-creep" monster is starting to rear its ugly head. A little feature here, an integration over there, some options sprinkled around for good measure...and your once simple webapp is starting to look like Salesforce. You'll feel like you're improving things, but you're going to be crying the next time you do usability testing with some brand new users. Even if you personally know exactly what every knob and button in your app does, you have to be conscious of the fact that every detail takes away importance from every other detail -- and first-time users can only process so much before getting overwhelmed and calling it quits.
Adding Value Without Overwhelming
We feel like having an Add-on Store is a great way to not overwhelm first-time users while still giving power users the advanced features and control they want. It's very important to us that our users actually enjoy using our product, and products with too many features and settings rarely are a joy to use.
How It Affects You
The add-on store is live as Friday, June 20th. If you created your account before that, all of the add-ons in the store are activated for you. Any accounts created after the deploy have a few add-ons activated for demo purposes, but the rest are inactive by default. You can find the add-on store by clicking the link in the top right when logged in.