[et_pb_section fb_built=”1″ admin_label=”Section” _builder_version=”4.22.0″ _module_preset=”default” custom_margin=”0px||0px||false|false” custom_padding=”0px||0px||false|false” locked=”off” global_colors_info=”{}”][et_pb_row column_structure=”1_4,3_4″ _builder_version=”4.27.0″ _module_preset=”default” custom_padding=”50px||||false|false” custom_css_main_element=”z-index:0!important;” global_colors_info=”{}”][et_pb_column type=”1_4″ disabled_on=”on|on|off” _builder_version=”4.22.0″ _module_preset=”default” custom_padding=”||||false|false” sticky_position=”top” sticky_offset_top=”100px” sticky_limit_bottom=”section” motion_trigger_start=”top” global_colors_info=”{}”][et_pb_text admin_label=”indice” _builder_version=”4.27.0″ _module_preset=”default” custom_margin=”||0px||false|false” custom_padding=”||14px||false|false” link_option_url=”#1″ global_colors_info=”{}”]<\/p>\n
Sections<\/strong><\/p>\n [\/et_pb_text][\/et_pb_column][et_pb_column type=”3_4″ _builder_version=”4.27.0″ _module_preset=”default” custom_css_main_element=”z-index:0!important;” global_colors_info=”{}”][et_pb_text admin_label=”seccion” module_id=”1″ module_class=”ittopicscontent” _builder_version=”4.27.4″ _module_preset=”default” z_index=”0″ custom_margin=”0px||0px||true|false” custom_padding=”0px||0px||false|false” hover_enabled=”0″ custom_css_main_element=”font-family:%22Pandora-Light%22;” locked=”off” global_colors_info=”{}” sticky_enabled=”0″]$6,803 per second. It sounds like Jeff Bezos’ earnings, and we wouldn’t be far off, because that was Amazon’s loss<\/A> during a Fastly CDN service outage on June 8, 2021. Just over an hour, $32 million lost, because every second of downtime means lost sales, interrupted work, and frustrated customers who leave and never return. That’s why implementing uptime monitoring, or availability monitoring, is crucial for our technological infrastructure. Uptime monitoring<\/Strong> is a supervision system that ensures our digital services\u2014ranging from websites to APIs, servers, or Industrial Control Systems\u2014are always operational. Technically, it is a set of protocols and tools that automatically and continuously verify the health of IT infrastructure components. In practice, this involves establishing scheduled checks to evaluate:<\/p>\n For example, if a company uses Kubernetes, uptime monitoring doesn’t just verify that nodes are active but also ensures that critical pods, like an authentication service, are running correctly.<\/p>\n The cost of a service outage goes beyond direct financial losses. For instance:<\/p>\n However, service interruptions add another critical cost that is difficult to quantify: the loss of customer trust<\/strong>. According to data<\/a>, 47% of users abandon a website if it takes more than 2 seconds to load, and 80% don\u2019t return after a bad experience. You can be alive, but barely hanging on. That\u2019s why uptime monitoring isn\u2019t limited to checking whether a server responds. We must apply techniques that, when combined, detect failures across various layers of infrastructure, starting with the basics.<\/p>\n This involves sending ICMP packets to a device<\/strong> to verify basic connectivity. It identifies total outages or network cuts if the ping does not receive a response. This technique not only ensures that the web service responds but also that it returns an HTTP 200 OK code and has valid SSL certificates. As long as this is the case, we can ensure that end-users can access and use the website or API. This technique monitors DNS resolution and propagation times, preventing your domain from becoming unreachable due to misconfigurations, DNS poisoning attacks, and more. This technique checks the accessibility and performance of specific ports on a network. This ensures that services dependent on TCP protocols (HTTP, SMTP, FTP…) and UDP (video streaming, VoIP…) are operational. Another powerful technique is monitoring through the Simple Network Management Protocol (SNMP), which keeps an eye on the network and alerts to any issues or unusual behavior. It works by collecting data from routers, switches, or IoT devices. Although we work with machines, we ultimately serve people<\/Strong>, and they require service guarantees considering how catastrophic every second of downtime can be. How these concepts interconnect: There\u2019s a fascinating, award-winning documentary titled Man on Wire (2008). It recreates the incredible feat of French tightrope walker Philippe Petit, who, in 1974, illegally strung a wire between New York\u2019s Twin Towers\u2026 and walked across it. Each step forward was a challenge, and even the slightest mistake or unexpected event could have meant the end. The walk was nerve-wracking\u201445 minutes to cross the 400 meters eight times. There\u2019s no such thing as a perfect metric\u2014only the most suitable ones for an organization based on its activity. However, some metrics are fundamental for uptime monitoring and SLA compliance, including the following:<\/p>\n\n
\nToday, everything is faster than ever, but nothing is quicker than user impatience, and nothing feels as endless as an hour without documents, chats, or work applications, while watching profits go down the drain.
\nErrors will always happen. The difference lies in mitigation, which starts by instantly detecting any anomaly. That’s why here is a complete guide on uptime monitoring, including what it is, techniques, tools, examples, strategies, criteria for choosing a good solution, and much more.<\/p>\nWhat is Availability Monitoring and Why is it Essential?<\/h2>\n
\nThis allows organizations to:<\/p>\n\n
\n
The Impact of Downtime: More Than Just Numbers<\/h3>\n
\n
\nIn this context, uptime monitoring is no longer optional\u2014it’s the minimum requirement to ensure continuity whenever possible.
\nHow Do We Start?
\nThe key is to combine basic techniques, like pinging the service, with more advanced strategies such as network monitoring<\/a> and user experience (UX) and web user experience (WUX<\/A>) monitoring to create a multilayered safety net.
\nLet\u2019s explore the main techniques available to build this framework.<\/p>\nKey Uptime Monitoring Techniques<\/h2>\n
Ping Monitoring (ICMP): The Foundation of Monitoring<\/h3>\n
\nBut what if our WordPress site cannot connect to its database due to a configuration error? The ping will tell us the page is alive, but not that it\u2019s failing. That\u2019s why we need to implement other techniques.
\nOtherwise, relying solely on ping monitoring could turn into the meme of the dog sitting with a cup of coffee while everything around it burns. The server says, “Everything is fine” when asked, but chaos reigns all around.<\/p>\nHTTP\/S Monitoring: The Next Step<\/h3>\n
\nThis approach is especially useful when, for instance, your WooCommerce store throws a 500 error on Black Friday\u2014because Finagle’s law always applies: “Anything that can go wrong, will go wrong at the worst possible moment.”
\nIn such cases, it\u2019s also advisable to combine this with synthetic monitoring<\/a>, simulating real transactions to verify their functionality and optimize user experience.<\/p>\nDNS Monitoring: Ensuring Domain Resolution<\/h3>\n
\nImagine a bank that has recently merged with another. As part of this process, DNS updates are required. However, an error in the MX records could block customers from accessing their online banking services.
\nTools like DNS monitoring<\/a>, which include alerts for unauthorized changes or resolution failures, would notify the team immediately about such issues.<\/p>\nTCP\/UDP Monitoring, monitoring key ports<\/h3>\n
\nFor example, a hospital securely accesses medical records through port 443, but the intern (it’s always the intern) has reconfigured the firewall and accidentally blocked the port. A TCP\/UDP monitor would detect this instantly with an alert, not later, through the doctors’ shouting.
\nThis is where we see the importance of solutions that integrate IT infrastructure monitoring<\/A>.<\/p>\nSNMP Monitoring: The Network’s Watchdog<\/h3>\n
\nIs the office printer suddenly sending gigabytes of data to an unknown server? Sure, that’s “completely normal” (no, it’s definitely not). But SNMP monitoring would catch such anomalies immediately. Implementing this approach helps avoid major headaches\u2014here\u2019s a guide to setting up SNMP<\/a>.
\nA robust uptime monitoring strategy must combine these techniques based on your organization’s operational and technical needs. This ensures you won\u2019t be stuck in a situation where a ping test says “everything’s fine,” while your online transaction API is down\u2014and no one knows.
\nThe ultimate goal is to ensure compliance with Service Level Agreements (SLA)<\/Strong>. Therefore, it’s worth diving deeper into this concept and related terms.<\/p>\nSLA, SLO, SLI, and Their Relationship to Uptime Monitoring<\/h2>\n
\nThis is where these key acronyms come into play, and why it’s essential to be familiar with them:<\/p>\n\n
\nSLI measures SLO, and SLO in turn, which is internal and more strict than SLA, ensures the compliance of the latter.<\/p>\nHow Uptime Monitoring Impacts SLAs<\/h3>\n
\nFascinating, seriously, but here\u2019s the important part: when it comes to SLAs, we\u2019re in a similar situation. Progress is slow and tough, scraping for every fraction of improvement in SLAs and SLOs to move those indicators upward. But falling short is easy. Just one incident of downtime can pull us off the wire.
\nUptime monitoring acts as the safety net, verifying compliance and alerting us immediately to mitigate any fall. Without uptime monitoring:<\/p>\n\n
Key Examples of Uptime and SLA Metrics<\/h3>\n