Operations | Monitoring | ITSM | DevOps | Cloud

Databases are the core of modern applications, whether it is an e-commerce platform, a banking system, or a social media app. Slow database performance or unexpected downtime can cause serious problems, from lost revenue to poor customer experience. Proactive database performance monitoring helps teams identify issues before they escalate. Unlike reactive monitoring, which only addresses problems after they occur, proactive monitoring ensures your database remains fast, stable, and reliable.

Node.js has become a cornerstone for modern application development because of its non-blocking and asynchronous architecture. According to Stack Overflow Developer Survey, Node.js remains among the most widely used technologies for web applications, powering millions of services globally. While this event-driven model provides scalability and efficiency, it also introduces challenges.

The least exciting part of an operations or SRE role is often the manual, repetitive task of generating reports. It’s the Monday morning scramble to summarize weekly infrastructure health for the team, or the end-of-quarter push to build a capacity planning document. This is boilerplate work that pulls you away from critical engineering tasks. We believe that if a process is repeatable, it should be automated. That’s why we’re introducing Scheduled AI Investigations and Insights.

When DNS or domain name server resolution processes fail, or become sluggish, users can experience timeouts, connection errors, and degraded performance — often without clear indication of the root cause. This is where DNS checks in Grafana Cloud Synthetic Monitoring come in, allowing you proactively monitor domain name resolution, verify that domains resolve to the correct IP address, and even measure how quickly that resolution occurs.

Ever “pinged” a server and wondered what those milliseconds actually mean? If you’re a network admin or IT pro, you already use ping as a quick sniff test. But ICMP is more than a green checkmark or a scary timeout. In this article, we’ll define ICMP, walk through how echo requests and replies work, and show how to turn basic pings into useful network and ICMP monitoring.

OpenTelemetry is a broader, vendor-neutral framework for generating and collecting telemetry data (logs, metrics, traces), offering flexible backend integration. Jaeger, on the other hand, is focused on distributed tracing in microservices. Earlier Jaeger had its own SDKs based on OpenTracing APIs for instrumenting applications, but now Jaeger recommends using OpenTelemetry instrumentation and SDKs. Warning The original Jaeger client SDKs (based on OpenTracing) are archived and no longer maintained.

We have launched Request Mirror, a little free service to reflect HTTP requests. We've also open-sourced it: you can read the code in the ohdearapp/request-mirror.ohdear.app repo on GitHub. In this blog post I'd like to explain why we built it and how you can use it.

When Microsoft rolled out Windows Server 2025 last November, it marked a turning point in how IT teams think about monitoring. Suddenly, AI-powered features like anomaly detection, predictive resolution, and even self-healing aren’t ideas on a roadmap — they’re built into the very fabric of enterprise infrastructure.

Slow logons, laggy VDI sessions, and poor Horizon performance are common pain points IT admins face frequently. When Omnissa Horizon environments slow down, both end-users and IT teams feel the pressure—users grow frustrated while admins struggle to troubleshoot without complete visibility. To uncover the real-world Horizon issues admins face, we turned to Reddit forums like r/VMwareHorizon, r/sysadmin, and r/Citrix, where IT professionals openly share their Horizon troubleshooting struggles.