Cachet v2.2.0

On March 27th we released version 2.2.0 of Cachet. We've made some pretty big changes that we're excited about, so here are the highlights. You can check out the full list of changes on GitHub.

Upgrade Notification

To ease future upgrades of the Laravel framework, we had to sync up some of the internal configuration files. One of these changes has altered the setup of SQLite databases.

If you're using SQLite then follow these simple steps:

  1. Modify .env and copy the value of the the DB_HOST key, if it's linking to a file.
  2. Create a new key named DB_DATABASE and set the value to what DB_HOST was.
  3. Save the file, then run php artisan config:cache.

So for example, if you previously had this:


You need to change it to this:


v2.2.0 Highlights

If you're interested in a TL;DR version, then here are the highlights!

AJAX Metrics

Heavy use of metrics would previously slow down your Cachet installation — this is of no use when your customers are trying to see what's occurring!

We now the metric points with AJAX, after the status page has loaded.

The metric points API is now paginated.

Metric Point Data Type

The database type for metrics has been changed to DECIMAL(15,3) which now allows for greater accuracy in your data.

Component Badges (Shields)

As powered by our Badger package, you can now embed your Component statuses into your documents or websites using the Shields badge.

For example, in our demo instance this:


Will generate the following shield:

API Component

Subscriber Changes

Subscribers are now able to manage their subscriptions. This page can be accessed through the link in any e-mails sent out from Cachet.


We've improved some of the details in the Cachet design. Including a refresh on the dashboard and login page.

Component groups are now split to better show them as individual items when collapsed.

Custom Headers & Footers

You can now supply custom HTML for both the headers and footers.

Please note that when supplying this code, the existing headers and footers will be hidden.

API Changes

Squashed Bugs

Numerous bug fixes have also been made in this release.

What's next for Cachet?

Alongside v2.2.0 we've been working on some new features, a couple of which you'll currently see in the Pull Requests page.

Refactoring Scheduled Maintenance

Currently Scheduled Maintenance is stored alongside Incidents. Whilst this works, it limits us in what we can do.

This refactor will:

Incident Updates

This is probably the feature I'm most looking forward to as it'll redefine how you use Cachet and communicate incidents with your customers.

You'll be able to finally create the main incident, then add updates to it, without editing the original incident! This means that you'll finally have a proper timeline of updates, with API access and more.

A change like this requires modifications to the status page view, so expect some cool things to happen!

Improved Metric Point Storage

As we've found out with v2.2.0 a lot of metric points can affect the speed of your status page and whilst we've tried to avoid this, we can take it further.

Metric point values will now be grouped together if they're added with the same value in a customizable time-frame.

Essentially, you can store the same amount of points in less memory.

We'll also look at caching this data to make it faster all round.


Of course there is more, but we'll have to come back to that!

Share Comment on Twitter