Observability Designer

**TL;DR** - Design your observability stack before you need it. Not after.

The 10-Second Pitch

• Maps your services and generates a complete observability strategy
• Recommends instrumentation points based on service boundaries
• Generates alert rules with appropriate SLO thresholds
• Produces runbooks that trigger from the alerts it generates

Setup in 3 Steps

1. Describe your architecture: services, SLO targets, data flows

2. Review the generated observability plan

3. Apply the instrumentation recommendations

**Example Prompt:**

Design an observability strategy for our e-commerce platform. SLO: 99.9% uptime, p99 checkout latency under 2s.

Verdict

You don't want to be debugging with printf statements when your checkout service is down. Design your observability before you need it.