You’ll learn what an HTTP monitor is and what it can do for you. We then part ways while sharing some final thoughts.Īs promised, let’s start with the basics.
HTTP WEBSITE MONITOR HOW TO
We’re just that nice.Īfter walking you through the important metrics you should know, we cover the importance of alerts and how to configure and use them wisely, under penalty of getting underwhelmed by the sheer volume of them. It’s important to distinguish the wheat from the chaff and we’ll help you with that. As it turns out, there are quite a few of them, but not all generate the same value for you. After that, we’ll walk you through some of the main metrics you should care about when considering adopting HTTP monitoring. We’ll start with the “what” question, by explaining what an HTTP monitor is and the ways in which it can help you. These are the questions we’ll answer in this post. But what is an HTTP monitor, anyway? And why else would you need it? It was actually lucky for us that he had that monitor: it helped everyone fix things before our clients could notice. He was using an HTTP monitor that emailed him every time the API was down, slow, or unresponsive. But the truth is that he wasn’t doing that at all.
There were times when we even thought he had nothing else to do than constantly refresh the web page. We were so worried about bringing the API up that we never paid attention to how he was able to be one step ahead of us. One day, one of our main web APIs was down, and the first person that knew it was my boss.