If all you have is the beginning and the end, you’re left with a short, boring story: “Once upon a time, it was UP…then, it was DOWN.” Knowing the twists and turns of your transaction pathways is not only illuminating, but profitable. Information channels dry up when all you have are pieces.
HR people have a saying: right person, right place, right time, meaning that the right resources can make all the difference when it counts. The same goes for Incident management and response, where very often the wrong person, place, or time can contribute to mounting catastrophe. As systems grow, the right person really can make the difference during an outage simply due to command or knowledge of the system.
Once upon a time there was the internet, and it was good, and it was global. We built our businesses across its networks and expanded our commerce from computer to cloud. Like with any physical trade route, the journeys are not always consistent. If your website is your flagship, your reports are your map. Sites rely on servers and it’s possible that your site might be UP in the UK but DOWN in Dallas.
Having a Status Page is like having a dog. A dog alerts you to an incident; sudden noise, approaching neighbor, squirrel… A dog sounds the alarm on an intruder. A dog even alerts you to maintenance by barking at every handyman, garbage truck, and gardener within sight. As a dog fetches the same stick over and over, so does a status page fetch the attention of your users – especially during a live incident – with each browser refresh they wait for the status to change.
Chaos theory tells us that disruption strongly relates to time; and that the interval between chaos events either increases or decreases based on the amount of action. It sounds like a complex concept but the internet has managed to prove this theory and make it viral – not Rick Roll viral, more like DogeCoin viral – where profits are instantly influenced by volatile popularity. Inside the internet, speed equals profit so it makes sense to monitor it…but what does that mean?
Oh no. Your website is down. And regardless of what time it is we guarantee it’s not a convenient time for your website to crash. An outage can cause a panicked fight-or-flight response when teams are unprepared for the consequences. One of the worst ways to deal with downtime is to try and wait it out thinking it’ll just magically resolve itself.
External servers need to be monitored but it’s your backend infrastructure that supports them. Looking for a reliable way to monitor your internal networks? You’re in luck! Uptime.com Private Location monitoring is just the tool for you.
Digital experience monitoring (DEM) is software dedicated to monitoring end-user experience. To do this, DEM software tracks user data, resources, and applications to highlight areas of performance for improvement; from site navigation to product usability.
Uptime.com maintains a Github, which we update with important and useful resources for those seeking a command-line approach to Uptime.com. We also house important files there for users of our private location probe servers. When you want to use our REST API, and you need help getting started, our Github is a good place to begin. Access our Github here. Today, we want to introduce you to our project, discuss why we chose Github, and share what we hope to accomplish in the future.
Our bread and butter is checking for uptime, and we always recommend users begin their monitoring with the HTTP(S) check. We call it a basic check type, but its functionality is boosted when you start exploring optional parameters. The Uptime.com HTTP(S) check can do a lot more than check for server status 200 OK.
