Jump to content

jbrooksuk

Members
 View Profile  See their activity

  • Posts

    17

  • Joined

  • Last visited

  • Days Won

    3

 Content Type 

Posts posted by jbrooksuk

  1. Network Status And Schedule Maintenance

    in The Lounge

    Posted

    So here is an update on where Cachet is at!

    We're currently working on v2.4 which so far contains:

    1. Incident Updates
    2. You can now skip verifying of subscribers
    3. Improved setup
    4. Cleaned dashboard
    5. Stickied incidents
    6. 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...

  3. Network Status And Schedule Maintenance

    in The Lounge

    Posted

    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!

  5. Php7

    in The Lounge

    Posted

    yes, your right, I was prefering mysqli in place of PDO, because coding syntax are more close to mysql, and I'm not willing to work with other db than mysql

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

  6. Php7

    in The Lounge

    Posted

    Some of my custom script use mysqi I was preffering to pdo , do I have to worry ?

     

    Do you think  mysqi will be still supported on the long run with PHP7?

    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!

  7. Network Status And Schedule Maintenance

    in The Lounge

    Posted

    Can you also group servers into a overall status? Like say... you have 200 of shared hosting servers, 500 of reseller servers, and 2 dedicated servers, just for giggles. Then you group them into three groups, respectively naming them shared, reseller and dedicated and show the server status for each group instead of individual ones, if so desired.

     

    Is it possible to have an overall status of the servers and have a... indicator of sorts for a server having issues? That way a customer can click on the indicator and be shown the specific server having issues... or something. Or does Cachet already have something like that?

     

    Sort of. We have Component Groups, but they're not fully implemented yet. By that, I mean that we don't do anything with them (not till V2), but in the future we'll show these groups on the status page and allow you to update the status of a whole group too.

     

    In regards to your last question... We do show the overall system status (at the top) this is based on any component being anything but Operational or having any non-Fixed incidents.

  8. Network Status And Schedule Maintenance

    in The Lounge

    Posted

    Would it be best to only display the days there is issues?

    This feature has been asked for quite a lot, so I've now added it to the issue tracker.

     

    Nice... I think I'll most definitely be using this when this gets released.

     

    We have our own status page... but it's at Pingdom and... while that's great, as a server status page... it's not great for letting customers know that "Yes, we're aware of the issue and are working on it. Here's what's going on."

     

    This presents that nicely, I believe... although I do have a question:

     

    What happens when you get into the hundreds or thousands of servers?

    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?

  10. Network Status And Schedule Maintenance

    in The Lounge

    Posted

    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.

    1. We'll be introducing an update system, which will sort out everything for you; migrations, updating/installation of packages etc.
    2. The API will be polished off. There are a few loose ends and differences between a couple of the endpoints.
    3. 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.
    4. Notification support; Twitter, emails, IRC, Slack etc. And as an added bonus, customers will be able to subscribe to email updates.
    5. More translations.

    Except for perhaps the API, nothing should be incompatible with the current master codebase.

     

    What's next for Cachet?

    1. A rewrite using Laravel 5. This gives us a lot of added power and makes maintaining much easier.
    2. oAuth support for third-party applications.
    3. Displaying component groups on the status page.
    4. Support for multiple applications.
    5. SAML & LDAP authentication support.
    6. Team invitation system.
    7. Complete integration to the component tags feature.
    8. Status page templates.
    9. 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

  14. Network Status And Schedule Maintenance

    in The Lounge

    Posted

    First of all, we merged in Scheduled Maintenance yesterday. You can see a demo of it at https://status.cachethq.io

     

    Hello and welcome..

     

    I have looked at cachetHQ but didnt see a way to install via web browser only SSH

     

    I am not a big fan of installing software this way.. Still interested in the software.. especially if there is a way to plug in via blesta

     

    Regards

     

    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

  17. Network Status And Schedule Maintenance

    in The Lounge

    Posted

    Hey all,

     

    My name is James Brooks, I'm the developer behind Cachet.

     

    Im looking for something like statuspage.io but cheaper as i think their prices are a little to high

     

    This is exactly why I started writing Cachet.

     

    Would this be something good for you mate: https://cachethq.io/

     

    Thanks for sharing the link!

     

    I was looking at that but it doesnt have a scheduled maintenance part only recent incidents :) I think I may have to get someone to right a small script lol

     

    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

×
×
  • Create New...