jbrooksuk

So here is an update on where Cachet is at!
We're currently working on v2.4 which so far contains:
Incident Updates You can now skip verifying of subscribers Improved setup Cleaned dashboard Stickied incidents Numerous bug fixes And there is still a lot more to come before the release:
Improved design Scheduled maintenance will become a first-class citizen in Cachet, not bolted into incidents Much more...

Hi all,
 
I know that some people are wary of installing beta software in a production environment, so let me give you a quick rundown of what's going to be changing before the release of V1.
We'll be introducing an update system, which will sort out everything for you; migrations, updating/installation of packages etc. The API will be polished off. There are a few loose ends and differences between a couple of the endpoints. General code clean up. There are a few things that have been left in the code from the start - these will be stripped back and tidied up. Notification support; Twitter, emails, IRC, Slack etc. And as an added bonus, customers will be able to subscribe to email updates. More translations. Except for perhaps the API, nothing should be incompatible with the current master codebase.
 
What's next for Cachet?
A rewrite using Laravel 5. This gives us a lot of added power and makes maintaining much easier. oAuth support for third-party applications. Displaying component groups on the status page. Support for multiple applications. SAML & LDAP authentication support. Team invitation system. Complete integration to the component tags feature. Status page templates. Incident Templates, templating system (variables etc, to be used by the API). On top of that, I have a lot more news that I'm preparing for the beginning of V2.
 
Hope that helps,
 
James

So here is an update on where Cachet is at!
We're currently working on v2.4 which so far contains:
Incident Updates You can now skip verifying of subscribers Improved setup Cleaned dashboard Stickied incidents Numerous bug fixes And there is still a lot more to come before the release:
Improved design Scheduled maintenance will become a first-class citizen in Cachet, not bolted into incidents Much more...

So here is an update on where Cachet is at!
We're currently working on v2.4 which so far contains:
Incident Updates You can now skip verifying of subscribers Improved setup Cleaned dashboard Stickied incidents Numerous bug fixes And there is still a lot more to come before the release:
Improved design Scheduled maintenance will become a first-class citizen in Cachet, not bolted into incidents Much more...

nice! looking good 

We've made a lot of changes for the upcoming v2.2 release including:
Loading metric points with AJAX, your status page will no longer slow down when you're sending hundreds of thousands of points! Metric points are now stored as DECIMAL(15,3) for more accurate logging. Your components now have Shields that can be embedded on websites, documents etc. Visitors can now subscribe to a single component. They can also manage their subscriptions. The metric points API endpoint is now paginated (performance related) The component groups design has changed to make it easier to differentiate between non-grouped components and component groups which are collapsed by default. Meta content is updated to include Open Graph data. French is no longer German. New version API endpoint. You can now supply custom header and footer HTML. API results can now be sorted. API results can now be filtered. Metrics now show the y-axis scale bars. Probably a few more things left before a release too!

We've made a lot of changes for the upcoming v2.2 release including:
Loading metric points with AJAX, your status page will no longer slow down when you're sending hundreds of thousands of points! Metric points are now stored as DECIMAL(15,3) for more accurate logging. Your components now have Shields that can be embedded on websites, documents etc. Visitors can now subscribe to a single component. They can also manage their subscriptions. The metric points API endpoint is now paginated (performance related) The component groups design has changed to make it easier to differentiate between non-grouped components and component groups which are collapsed by default. Meta content is updated to include Open Graph data. French is no longer German. New version API endpoint. You can now supply custom header and footer HTML. API results can now be sorted. API results can now be filtered. Metrics now show the y-axis scale bars. Probably a few more things left before a release too!

We've made a lot of changes for the upcoming v2.2 release including:
Loading metric points with AJAX, your status page will no longer slow down when you're sending hundreds of thousands of points! Metric points are now stored as DECIMAL(15,3) for more accurate logging. Your components now have Shields that can be embedded on websites, documents etc. Visitors can now subscribe to a single component. They can also manage their subscriptions. The metric points API endpoint is now paginated (performance related) The component groups design has changed to make it easier to differentiate between non-grouped components and component groups which are collapsed by default. Meta content is updated to include Open Graph data. French is no longer German. New version API endpoint. You can now supply custom header and footer HTML. API results can now be sorted. API results can now be filtered. Metrics now show the y-axis scale bars. Probably a few more things left before a release too!

We're actually doing that now anyway, it was done before 2.0

You should absolutely still use PDO, because who knows what will happen in the future.

Not if you don't upgrade.
 
For me PHP 7 is a massive step forward, from the tests I've ran it's at least twice as fast. Since I write my code on Laravel it's already mostly compatible, which is great!

This feature has been asked for quite a lot, so I've now added it to the issue tracker.
 
You should be able to start using Cachet now
 
Yeah, Pingdom is great for server monitoring but not informing customers of why the service went down in the first place.
 
In regards to the hundreds or thousands of servers, how do you mean "what happens"? How do you list them all?

Today I'm really excited to announce our new blog; https://blog.cachethq.io
 
As extra news, we've moved the demo instance of Cachet to https://demo.cachethq.io so that we can use https://status.cachethq.io ourselves

Crazy is my middle name haha.

Hi all,
 
I know that some people are wary of installing beta software in a production environment, so let me give you a quick rundown of what's going to be changing before the release of V1.
We'll be introducing an update system, which will sort out everything for you; migrations, updating/installation of packages etc. The API will be polished off. There are a few loose ends and differences between a couple of the endpoints. General code clean up. There are a few things that have been left in the code from the start - these will be stripped back and tidied up. Notification support; Twitter, emails, IRC, Slack etc. And as an added bonus, customers will be able to subscribe to email updates. More translations. Except for perhaps the API, nothing should be incompatible with the current master codebase.
 
What's next for Cachet?
A rewrite using Laravel 5. This gives us a lot of added power and makes maintaining much easier. oAuth support for third-party applications. Displaying component groups on the status page. Support for multiple applications. SAML & LDAP authentication support. Team invitation system. Complete integration to the component tags feature. Status page templates. Incident Templates, templating system (variables etc, to be used by the API). On top of that, I have a lot more news that I'm preparing for the beginning of V2.
 
Hope that helps,
 
James

You're crazy

Oh, the "timeline" view? I was thinking about that, but it'd be hard to distinguish.

First of all, we merged in Scheduled Maintenance yesterday. You can see a demo of it at https://status.cachethq.io
 
 
Thanks Dean!
 
You need to get it setup over SSH unless you can deploy to Heroku - after that it's all browser-based configuration.
 
Cheers,
 
James

Hey all,
 
My name is James Brooks, I'm the developer behind Cachet.
 
 
This is exactly why I started writing Cachet.
 
 
Thanks for sharing the link!
 
 
Scheduled maintenance is coming soon: https://github.com/cachethq/Cachet/pull/404 the feature should be merged in shortly. We're working really hard to get V1 out, so it definitely won't be long.
 
Cheers,
 
James

Hey all,
 
My name is James Brooks, I'm the developer behind Cachet.
 
 
This is exactly why I started writing Cachet.
 
 
Thanks for sharing the link!
 
 
Scheduled maintenance is coming soon: https://github.com/cachethq/Cachet/pull/404 the feature should be merged in shortly. We're working really hard to get V1 out, so it definitely won't be long.
 
Cheers,
 
James

Thanks!
 
Ok, well if there is a way we can integrate to Blesta - not now, but perhaps in the future - I'd be interested.

Thanks!
 
Ok, well if there is a way we can integrate to Blesta - not now, but perhaps in the future - I'd be interested.

Thanks Licensecart.
 
I don't see why not. Cachet has a fairly friendly API (although still in progress for V1). We're trying more for people to send data back to Cachet. Is this something Blesta could do?

Hey all,
 
My name is James Brooks, I'm the developer behind Cachet.
 
 
This is exactly why I started writing Cachet.
 
 
Thanks for sharing the link!
 
 
Scheduled maintenance is coming soon: https://github.com/cachethq/Cachet/pull/404 the feature should be merged in shortly. We're working really hard to get V1 out, so it definitely won't be long.
 
Cheers,
 
James