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.
The need to implement 360° monitoring of a multi-service infrastructure is almost a universal truth among growing companies. With an expanding pool of clients and services to monitor, segmentation is the key to smooth operation. Monitoring with subaccounts is prime management solution. The trick is to simplify your account structure without limiting your visibility. To evaluate, we’re going to dive to a cellular level. Size matters.
Uptime.com checks can test anytime, from anywhere, to catch the downtime incidents you need caught. With worldwide probes, or through private locations that monitor your internal network, we reliably detect outages and monitor performance across your websites, applications, servers and infrastructure. Read on to explore 15 use cases for the HTTP(S) check type. HTTP(S) checks validate if a server is up or down, while reducing the possibility of false positives.
Uptime.com is GDPR compliant as of 2021. Becoming GDPR compliant required an organization-wide dedication to maintaining privacy and security to meet these new standards. These updates impact everything from working with support to our team logging in for work each day. Today, we’ll tackle what GDPR means to our organization, how these changes affect your usage of Uptime.com, and what we’re doing now (and into the future) to protect your personal data.
With a service as intricate as monitoring it’s nearly impossible to have all your questions answered just by exploring the product website. No matter how clear the pricing and feature descriptions are, it’s hard for a feature description to tell you if it can rise to every occasion your devops team will face. A free trial is an opportunity to connect with a service and test for your use cases.
Your site or application runs on a server, which is just another computer inside some server warehouse. That server is subject to the same kinds of limitations as your personal computer, and you need a way to determine usage of those resources similar to the internal monitoring for disk space or CPU usage that you find inside a Windows or Mac operating system. These internal metrics collectively determine the power or capacity of your server.
You likely do not own your server, but you do have an interest in making sure the applications you run on your server remain responsive. You need to know the full story, and a combination of external and internal monitoring is how you get there. Marketers understand the word “responsive” to mean “capable of rendering on any screen”, but we can think about responsive in more fundamental terms.
Not all the waves we make are extreme. This is our fancy way of saying that we’ve been making a lot of small, behind the scenes updates lately targeting improvements to reporting and performance. For a full rundown, check out our release updates.
Monitis, once a stand alone monitoring solution, has become Teamviewer Web Monitoring. If you don’t like or don’t need the changes offered you may be looking for alternatives to Monitis. Monitoring is integral to your growing suite of web and application monitoring, and it can be difficult to find a replacement that will do everything you need in one software.
Let’s talk about The Legend of Zelda: A Link to the Past, and how it relates to DevOps. The game tasks our hero with finding three pendants, which unlock a Master Sword he can use to travel to an alternate realm and ultimately take down the bad guy. The US version of this SNES masterpiece came packaged with a fairly detailed instruction manual that contained an optional guide at the end to help locate the three pendants.
