A couple of us are here in Portland for Monitorama this week, and hooked up with the team at Slack to get an integration done while we listened to lots of talks, ate many donuts, and observed general hipster goings on.
Long story short, we now support Slack! Check out the screenshots below, and the help article to get everything set up.
You can read all about it with our help article, feel free to reach out if you have any questions or comments.
A few months ago we launched Component Subscriptions as our first step towards getting the right notification to the right end user. Today, we’re taking this concept to the next level with StatusPage.io Multitenancy.
The Right Status Page For The Right User
System status is something that’s hard to get right for larger companies with thousands, if not hundreds of thousands of customers. Operations and support teams have legitimate questions around how to appropriately communicate status. At what severity level should we post an incident? Is everyone affected by this issue or just a subset of users? If it’s only a subset of users, how do we let them know without scaring the rest of our users unaffected by the issue? At what point should we send email and/or sms alerts vs. only displaying information on our status page? The list goes on.
StatusPage.io Multitenancy addresses the majority of these problems by allowing for end user specific status pages and notifications. Customer Support and Ops can sleep happy knowing they aren't scaring users with irrelevant status notifications, while end users receive a cleaner status page UI and pertinent status notifications.
See It In Action
Open multitenancydemo.statuspage.io in three incognito windows and authenticate with email@example.com, firstname.lastname@example.org, and email@example.com. You'll notice that live incidents, scheduled maintenance, components, and incident history are completely dependent on the user.
Feli’s page on the left is showing Partial System Outage since Acme's API is down, while all systems are up for Brennan since he does not use Acme’s API and is therefore not affected by the current outage.
How It Works
Let StatusPage.io know about your users and the relevant infrastructure they live on or the services they use through the API.
End users authenticate when visiting your status page in order to view the current status and subscribe to updates.
Based on end user authentication, we'll show the right system status information for that user.
Component status, live incidents, metrics, and incident histories will be completely dependent on the user.
If you’re interested in getting setup with Multitenancy, give us a shout at firstname.lastname@example.org and we’d love to line up a call to see how we can help out!
We're happy to announce some improvements to the Custom HTML/CSS editor. The UI looks quite similar but you'll notice two enhancements.
The old editor windows were hard to work with at times. They were fixed in height and you had to scroll horizontally to see the ends of lines. You can now collapse unused editor windows which will cause the other windows to expand to fill up the remaining space. This will allow you to focus more on one editor window at a time. We now have a graceful line wrapping system implemented so you no longer have to scroll horizontally to see the contents of long lines.
Support For SASS, SCSS And LESS
The biggest improvement comes in the form of a new feature: the ability to use SASS, SCSS or LESS when writing CSS. We've teamed up with incredible folks at CodePen.io to be able to accept and compile these new input modes. You can switch from vanilla CSS to any of these modes by clicking the "options" gear in the header label of the CSS section.
A Custom Header/Footer Template
We've created a public GitHub Repo with the HTML and CSS for a template that you can use as a jumping off point. If you are limited on design resources, the template provides a nice looking, responsive, easily customizable Custom Header and Footer to use on your page.
You can find the GitHub repo here.
Over the past few months we've heard a request from many of our larger customers: "We need more relevant customer notifications." Digging in a bit further, the issue with general notifications for these companies is that one customer may use a set of products or services that is completely different from the products or services another customer uses. Potentially overwhelming users with irrelevant information can be scary.
Today, we're incredibly excited to launch Component Subscriptions to all of our Business level accounts.
As a subscriber
Component Subscriptions lets your customers opt-in to the components that they care about. As an example, SmugMug, one of the best photo sharing services on the web, has several components listed on their status page including
Support & Help Pages, and
Uploads. However, as a SmugMug customer, I may only care to receive updates whenever new uploads or existing uploaded photos are having issues and not when their website or support portal are down.
After I subscribe for global notifications, I'll be redirected to my unique subscription management page where I can opt-in or out to specific components.
As a StatusPage.io admin
With Component Subscriptions activated, you will have the ability to associate an incident with specific components on incident creation and incident updates.
Once an incident is created or updated, we'll check on the backend to see exactly which subscribers should be notified about the issue based on their pre-defined subscriptions.
Every notification will also link back to a subscriber's individual subscription management page if they ever need to adjust their subscription.
How to get started
Component Subscriptions are available for all Business customers. To get started, head to Notifications in the management portal and check the box to allow subscribers to subscribe to individual components.
If you're looking to upgrade from an existing plan, click on the Account tab in the top right hand drop-down and into Billing. We're glad to help out as well with any questions about the new functionality.
Where we are going from here
Component Subscriptions are our first step towards customer specific status pages and notifications, which we're dubbing 'multi-tenant status pages.' We'd love to hear from anyone interested in being part of the beta.
Also, for anyone wanting to try out the new functionality, we're offering a 50% off discount for 3 months to ease you into the new plan.
Feel free to email us at email@example.com if you'd like to discuss further.
A month ago, we rolled out our new Activity Log with a built in HipChat integration. Today, we're excited to add Campfire to the mix! Similar to our HipChat integration, any Campfire customer can now pipe updates to their status page straight into a company Campfire room.
To get started, you'll want to read our documentation on Activity Log and authenticating your Campfire account. Once you've linked your account and added a room, that's it. We'll get to posting to your activity feed items right as they come in.
Give us a shout if you have any questions or feedback with the integration!
As many of you know, we're a distributed team. While we think we do a pretty good job at working remotely, the human aspect of face to face communication and hanging out is impossible to replace with software. So, we decided a couple months ago to do quarterly StatusPage.io bootcamps, with the first one taking place last week in Fort Collins, Colorado.
Along with growing sub-par moustaches in remembrance of Movember, we cranked out the finishing touches on some new features that we're very excited to launch.
Keeping your team in sync
Activity Log is a real-time feed of all core updates to your StatusPage.io account, including component updates, incident updates, and user provisioning. It eliminates the need to email the whole ops team when a user needs to know who created an incident or changed the status of a component. It gives developers the piece of mind that their whole team is on the same page during an incident, allowing the right people to fix the problems at hand instead of wasting time replying to chat and email.
Along with the new Activity Log, we've baked in a native HipChat integration. The integration takes internal status communication to the next level, keeping all employees of a company in the know during unscheduled downtime. You can read more about the integration on HipChat's blog.
Activity Log is available for all accounts. Within the management dashboard, click on the top right hand drop down and into Activity Log to take a look for yourself.
To pipe page updates into HipChat, first take a look at our knowledge base article.
Customized branding for a consistent look and feel
You may have seen StatusPage.io pages recently with custom headers and footers. A few of our favorite examples include Bitbucket, TestFlight, and UserVoice status pages. These companies have been part of our beta for Custom HTML, which is now live in our new page editor!
The new editor allows you to make changes to the custom css/html and preview those changes at the same time. With a few tweaks to your header and footer, your status page will now have a consistent look and feel with that of our own app or website.
Before diving in, read our docs on custom html. Custom CSS is available for all Startup and Business customers. Custom HTML is available for all Business customers.
Adding metrics to your page from any data source
Until now, you had to be a customer of one of our metrics providers (New Relic, Pingdom, TempoDB, Librato, DataDog) to display metrics on your page about your technology stack - things that your users experience like uptime, response time, and error rate. While these services cover some of our customer base, many of you asked to display metrics on your page from all sorts of external data sources including other vendors and in-house Graphite systems. In order to accommodate these requests, we built flexible API endpoints to ingest custom metrics from any external service or system. All we need are key-value pairs of timestamp/metric value in 30 second roll-ups.
As long as you have access to the data you would like to display, we can graph it.
To get started, first watch our video on creating a custom metric.
Once the metric is created, you'll be able to submit data for the metric through our API.
As always, let us know if you have any questions with these new features!
It's been too long since our last product update. Since Y Combinator ended, we've been heads down working on some awesome features. A few of these features will be released in November, but in the meantime, we've redesigned the incident update flow, incident update notifications, and postmortem creation.
Creating a new update
Instead of the typical modal that we've used in the past for updating an incident, you'll now see a redesigned incident update layout, allowing you to change the status of the associated degraded component at the same time. This change should help customers from forgetting to update a component status if necessary. We've also added an incident update history trail at the bottom of the update, giving you more context into the incident without having to go back and view the actual status page.
Email notification redesign
Our email notifications for incident creation and incident updates were fairly lackluster up until now. Here's a quick look at past updates vs. the new refresh.
Similar to the incident history trail on updating an incident, your subscribers will now see the complete incident history within every update notification as well as the timestamp for each update.
Postmortems are a great way to discuss a significant outage in further detail after the incident has been resolved. Customers generally want to understand the following:
- Were we affected?
- When did the issue begin?
- When was it resolved?
- What exactly happened and why?
- What is being done to make sure the same issue doesn't happen again in the future?
Before the new design, writing a postmortem for a resolved incident was fairly hidden within the interface and not user friendly to actually save and publish the postmortem. The new postmortem creation with Github Flavored Markdown and Preview functionality built in should help to better design and communicate with your customers after the dust settles.
A few of our most highly requested features over the past month included a responsive management portal, incident templates, and component descriptions...so we've built them for all of you fine StatusPagers.
Unexpected downtime doesn't wait for you to get back to your computer to fix the bug in your last deploy. Instead, you'll need to open an incident on your status page wherever you are to make sure your customers know about the issue. Understanding this pain point, we've taken the time to build a mobile friendly version of the StatusPage management dashboard.
When your site is down and you're updating your status page, you don't want to be laboring over what to name an incident and what the message should say. You can now create Incident Templates to use as a jumping off point for creating incidents. Once you've created templates within the Incidents view, you'll be able to choose from your templates on creation of the incident as seen below.
You can now add descriptions to your components. The description will appear in a tooltip next to the component on your status page. To add a description to an existing component, head over to the components page and click the edit link next to the given component. Here's a great example from Pantheon's status page.
We're excited to announce the rollout of our very own Heroku addon!
We've also done some great work to let you integrate your current status with the error page and maintenance page functionality of Heroku. In short, this means that whenever your app encounters an error or is viewed while in maintenance mode, we display for your web visitors a slimmed down version of your status page. This is a great way to get some awesome value out of a status page, and will let you cut down on support tickets when you're having trouble.
You can check out the addon at http://addons.heroku.com/statuspage - it's even free until we launch it publicly with Heroku, and then we'll work with you to get you set up with an appropriate plan.
Discuss this on Hacker News: https://news.ycombinator.com/item?id=6053897
Today is a big day for StatusPage.io - we're rolling out our next big iteration of tools for SaaS app creators and infrastructure providers, and introducing a few more pricing options to allow providers of all sizes to benefit from the product we've been hard at work building these past couple months.
Today's release includes a major new feature we're dubbing "Public Metrics", and we like to think of this as an amazing hands-off sales and support tool for businesses of all types.
How it works
We've partnered with some of the biggest and best data houses we know, and are launching with the ability to use your data from Pingdom, New Relic, Librato, Datadog, and TempoDB. In just a few simple clicks, you'll be up and running with live metric data on your very own page.
Whether you fancy uptime, API response time, or something more domain-specific, integrations with these data providers is sure to allow you to use whichever tool fits your business best.
Sales while you sleep
Public Metrics is one of the best ways that you as a business can flex your technical prowess to prospective customers. So much of what we do on the internet relies on word of mouth and familiarity, and overcoming entrenched competitors can be a tough challenge.
Using Public Metrics to show - in raw numbers - how much volume you're handling, how much that volume is growing, a beautifully flat API response time, etc, is a tremendous marker of competency and transparency. Stop losing sales due to lack of information, and start winning the bigger clients that usually go with the "safe" BigCo.
Although customer support can be a great opportunity, it's also a huge liability for your business, and letting your customers help themselves saves both of you precious time and frustration. By providing for customers a public page where they can self-diagnose who is at fault or where the problem lies, you can effectively diffuse confusing situations that would otherwise generate a bucket of support tickets.
Public Metrics helps out not when things are completely up or completely down, but in those times when you may have a localized outage or degradation of performance that is causing timeouts, slow API calls, delayed background job processing, etc.
Data integration partners
If you do not yet have a one stop shop for all of your system health metrics, you'll want to check out our data partners who are the best in the business.
- New Relic (offering their standard account for free to all StatusPage.io customers)
Over the next few months, you'll be seeing us add support for different chart types such as uptime heatmaps or histograms, and thresholds to color your charts appropriately and to set components into different states. We'll continue to add support for other data providers such as Graphite (both Hosted and private), and we'll be releasing a limited set of APIs for you to push data to us should your stack be locked down with Fort Knox security.