*Don’t Bother Reading This Post about Website Monitoring*
November 7, 2018|
If you’re a developer or IT professional, you can stop reading right now.
There is nothing in this post about website monitoring you don’t already know.
Why am I writing it then? I’m only writing this post because I want to help promote a lesser-known but important topic: tag monitoring. While tag monitoring is very different from website monitoring, the same professionals that use one form of monitoring should be aware of the other.
So to be honest, this post is purely for SEO reasons. So unless you want to read a super basic explanation of website monitoring (something you probably already have), don’t bother reading any more. But if you want to learn more about tag monitoring, check out this post by my colleague Matt Thomas discussing tag monitoring.
You have been warned.
How 63 Minutes Cost Amazon $72M
How would you like to lose $72,400,000?
That’s Internet Retailer’s estimate of how much revenue Amazon lost because of a 63-minute outage during their Prime Day Sale.
The costs of website downtime are particularly painful for retail sites, but downtime can damage any company’s revenue, reputation or user experience. And while outages like Amazon’s aren’t totally preventable, you better believe Amazon was as ready as they could be to respond to the issue.
Website monitoring is how companies address challenges with downtime. But you already knew that. (I’m honestly not sure why you’re still reading this.)
What Is Website Monitoring?
Website monitoring is a technology-enabled method for monitoring whether or not a website and its features are available to users. Some common tools used for website monitoring include New Relic for application performance monitoring (APM) or Pingdom for uptime monitoring. In addition, website monitoring tools can give you insight into visitor count and usage trends.
For the most part website monitoring is a reactive process—monitoring tools tell you when your site goes down so you can respond. But website monitoring can be preventative in that it can help you identify trends in traffic spikes or performance issues. If historically you’ve seen spikes at certain times of day or whatnot, you can adjust server capacity for those times.
The Primary Website Monitoring Features
Different features of website monitoring solutions fulfill different use cases. Here are some of the most common:
Uptime monitoring: Determine whether or not your website is up and available to users.
Server monitoring: Monitor system health on the server-side.
Transaction monitoring: Monitor important user paths on your site (such as a login or purchasing path).
Page speed monitoring: Monitor page speed over time and receive alerts if page speed exceeds a defined threshold.
Webhooks: Trigger a script on a website of your choice when a website changes state (such as changing from up to down).
Website Monitoring vs. Tag Monitoring
ObservePoint is not a website monitoring solution. Instead, ObservePoint provides tag monitoring functionality as part of a suite of tag governance features. Tag governance is a subdiscipline within data governance focused on verifying whether or not tracking technologies (tags) are present and collecting data as expected.
Why are we drawing this connection between website monitoring and tag monitoring? Because these are both solutions that technology teams need to be aware of.