Operations | Monitoring | ITSM | DevOps | Cloud

Error Budget in SRE: The Complete Guide (2026)

An error budget is the acceptable amount of unreliability permitted by your SLO over a defined time window. It is not a target. It is not a stretch goal. It is a hard ceiling that, when breached, should trigger a pre-agreed organizational response — feature freezes, postmortems, or infrastructure investment. The formula is blunt: Error Budget = 1 - SLO Target Error Budget (time) = (1 - SLO Target) × Window Duration For a 30-day window: That last number should make you uncomfortable.

Building a CloudWatch metrics pipeline: parsing OpenTelemetry data

AWS delivers CloudWatch metrics in OpenTelemetry format via Firehose, but AppSignal uses its own internal format. Building the parser to bridge these two formats presented several technical challenges. The metrics arriving through this pipe power AWS automated dashboards. When AppSignal detects metrics from a supported AWS service, it creates a dashboard for it automatically, with pre-built charts grouped by category: compute, databases, networking, messaging, storage, and others.

From Signal Corps to Space: Building Networks That Can't Fail with Troy MacDonald

What does it take to succeed in networking when complexity is constantly increasing, and change never slows down? In this episode of Next-Gen Network Heroes, host Bob Slevin sits down with Troy (David) MacDonald, a network engineer at Blue Origin and former U.S. Army Chief Warrant Officer, to explore a career that spans from infantry beginnings to designing and managing large-scale, mission-critical networks.

Optimizing Team Strengths for Effective Operations

Most people think great network engineers are defined by technical expertise. This episode challenges that idea. Because what Troy McDonald shows is that the real differentiator isn’t just technical skill—it’s the ability to translate complexity into clarity. From military operations to enterprise networks, one lesson keeps showing up.

Unlock telemetry value with a well-planned data lake

Your SIEM only holds a slice of your telemetry. Your data lake holds the rest. We'll show you how to use that to your advantage for investigations, threat hunting, and reporting. Why your data lake beats your SIEM for investigations – Your SIEM keeps a short window of expensive, filtered data. Your data lake keeps everything. When something goes wrong, that difference matters more than you think Threat hunting without the handcuffs – Hunting across months of data in a SIEM is painful and costly. We'll show you how a well-planned lake makes broad, deep searches practical and affordable.