We all like fast sites, especially in 2018. But how can we determine if a website is snappy enough? Are there any response time standards that we can refer to? Do search engines prefer fast-loading sites as well? This article will answer those questions.
Icinga Camp Berlin is happening right now, and as promised in my talk about “Dev and ops stories: Integrations++” we are proud to bring you Dashing for Icinga 2 in its v2.0.0 release ?
We published open-source, simple and easy to use .NET Standard 2.0 library with some useful utilities.
It has been around 2 years since we changed our looks, so it is right about time to try something fresh! In addition to design changes, we also updated our free tools - Website Availability Test and Website Speed Test. Even though Availability Tool functionality is the same, Website Speed Test tool has been redesigned completely - now we test website speed from 11 different checkpoints around the globe, to give you a good overview of how your website performs far away from your datacenters.
A typical workday for your IT team may go from calm to all hands on deck. When a problem occurs on your servers, you may not know the cause right away, but before you can start figuring it out, customers are blowing up your phone and monitoring systems. Everything you do from this point has a timestamp attached to it. If you wait five minutes to put up a status page, that could equal 100 people who have submitted tickets. The longer you wait, the more people you will have to get back to.
For a couple reasons, building a support team is pretty hard. It’s hard because there are no shortcuts to finding and training the right person. There are a lot more mediocre and poor support advocates out there than there are excellent ones. And the excellent ones are probably pretty happy where they are.