Operations | Monitoring | ITSM | DevOps | Cloud

Let’s say you want to make sure your website works as expected. You do not want to check if it just loads. You also want to check if important buttons or features are there and working. Oh, and you don’t want to just do it once. You want to keep an eye on this pretty much all the time. And, of course, you don’t want to keep checking manually if anything broke – you want to be notified, alerted when (not if) things break. You can do this by creating a Browser Monitor.

How do you use ArgoCD and a GitHub workflow together with an external CI/CD tool (Jenkins in our case) to trace a specific PR/commit hash code in a GitHub repository that’s external to ArgoCD? The term ‘commit tracing’ comes from Michael Crenshaw – one of the lead developers of Argo.

As your business grows, so will your infrastructure and the number of applications or services running in it. In other words, forget about any sort of manual monitoring or home-grown scripts or tools if you want to keep your sanity. Whether you need performance metrics, service health and availability status, infrastructure, or application logs, you need a tool that will give you end-to-end visibility into the health of your infrastructure.

This guide aims to help your team shift testing left, simulate real user behavior, and catch critical issues early as part of CI/CD, prevent regressions from reaching production by automating tests as part of your CI/CD and aborting deployments that contain issues. Synthetic monitoring is a great way to check important flows in production and make sure everything is working the way it’s supposed to.

A recent LinkedIn poll by Peter Zaitsev asked: “What is the most common preventable cause of downtime in your environment?” Guess what most respondents said it was? Surprise, surprise – the top answer is Deploying Broken Code, with 57% of respondents selecting it. This reinforces how critical it is to catch issues before they hit production.

First of all, by frontend memory usage I mean the amount of memory that a user’s browser needs when using your website or webapp. Secondly, do you have any idea how much browser memory your website or webapp requires? Or do you know if or how much the memory footprint of your website/webapp has changed over the last few months? Or after the recent changes or releases you made? I’m guessing you don’t. Yet, this is important to monitor to avoid a bad user experience.

Ever found yourself drowning in a sea of log data, struggling to make sense of the overwhelming noise? Or perhaps faced a major system breakdown, only to find that your logs didn’t provide the answers you needed, leaving you in the dark? Effective logging is a critical yet often overlooked aspect of software development and operations, highlighting why logging is important – it’s the foundation upon which observability, troubleshooting, and system maintenance are built.

Server uptime monitoring is critical for ensuring the reliability and availability of your infrastructure and services. By keeping track of server uptime, you may be able to identify and address potential issues before they impact your end-users. Why just “may be able to”? Because “it depends”. It depends on whether your infrastructure/applications/deployments are built with redundancy in mind. Even if you have a redundant setup, it depends whether it actually works.

Observability is essential for understanding how modern applications perform and behave in production. OpenTelemetry has emerged as the industry standard for collecting, processing, and exporting telemetry data—traces, metrics, and logs—without vendor lock-in. This guide will walk you through OpenTelemetry’s core components, how it works, and why it’s a game-changer for observability.

Let’s Encrypt has announced that it will no longer send certificate expiration notification emails. If you’ve relied on those emails to remind you when to renew your SSL/TLS certificates, it’s time to rethink your approach.