Operations | Monitoring | ITSM | DevOps | Cloud

How to combat alert fatigue like a ninja

When IT professionals become desensitized to the constant stream of system and network alerts, potentially missing critical issues amid the noise, the consequences can be significant. Join Field CTO Jeff Hunter as we discuss how to take a strategic approach to monitoring to help prevent alert fatigue with technicians and with end users.

How Alerting Works in SolarWinds Observability Self-Hosted

This training video from SolarWinds Academy provides a high-level overview of how the alerting process works within SolarWinds software. Technical trainer Cheryl Nomanson explains the step-by-step workflow, starting with the alerting engine continuously scanning the database for conditions that meet alert trigger thresholds. She covers how triggered elements are evaluated for suppressions (like time-of-day restrictions and scoping), and explains that only fully qualified conditions become actual alerts. The video details how alerts always display in the web console and may trigger additional actions like emails or scripts.

Enterprises don't fail because systems go down

They fail because human response breaks down under pressure. Over the past decade, organizations have invested heavily in monitoring, observability, and automation. Dashboards are everywhere. Alerts fire instantly. Tickets are created automatically. And yet, when a critical incident happens, the outcome is often painfully familiar. Someone doesn’t respond. Escalations stall. Ownership is unclear. Waste work in following up is created. And valuable time is lost.

What is IT Alerting?

IT alerting means that responsible and on-call employees receive IT alerts about disruptions and anomalies in IT systems and infrastructure. These notifications can come directly from the systems themselves or from monitoring tools. The goal is to reduce downtime, service limitations, security breaches, and data loss by responding quickly. In many cases, the stakes are high: data loss, reputational damage with customers, or even disruption of critical business processes.

Engineering reliable AI agents: The prompt structure guide

The difference between an AI assistant that "almost" works and one that consistently delivers high-value results is rarely a matter of raw model capability. Instead, the bottleneck is typically the quality and structure of the instructions provided. For DevOps and SRE teams building automated workflows, "magical prompt tricks" are no substitute for a repeatable, engineered structure.

Reducing Alert Noise with Composite Alerts in Hosted Graphite

Traditional alerts are simple by design: if a metric crosses a threshold, fire an alert. While that simplicity makes alerts easy to configure, it also leads to alert noise, because single metrics rarely tell the full story and often trigger during non-actionable conditions. Hosted Graphite Composite Alerts solve this by allowing you to combine multiple alert conditions using logical expressions like AND (&&) and OR (||).

AI Impact on software engineering (as I see it)

When I first started using AI (Cursor, to be more specific) for coding, I was very impressed to see how it could generate such high-quality code, and I understand why it's now one of the most widely used tools for software engineers. As I continued to use them more regularly, I realized they are far from perfect. Their effectiveness depends heavily on how they are used and the context in which they are applied.