← All lessons
Browse lessons

Week 2: Instrumentation and Reliability Engineering · Lesson 2.5

How instrumentation requirements differ by system type

What must be captured for this system type so we can diagnose the failures that matter?

Retired course. Due to the fast pace of AI, this course was retired before full release. Exercises, datasets, and videos referenced in this lesson are not available. The slide content and frameworks remain free to study.

Slide 1 of 17

Reader Notes

The v1 instrumentation built previously logs every pipeline stage: inputs, outputs, latency, status. This lesson reveals that generic span logging misses architecture-specific failures. Different system types fail in different ways. A pure LLM app fails differently than a RAG system, which fails differently than an agent. The system-type instrumentation framework covers three patterns that specify exactly what fields each architecture needs. When a PM asks why SQL generation is failing 10% of the time, the answer requires more than "status: failed." Instrumentation that captures decision boundaries, not just execution boundaries, is needed. That's what this lesson unlocks.

Go deeper with AI Analytics for Builders

5-week course: metrics, root cause analysis, experimentation, and storytelling. Think like a Product Data Scientist.

Book 1-on-1 with Shane

30-minute AI evals Q&A. Talk through your specific evaluation challenges and get hands-on guidance.

Finished all 36 lessons? Take the exam and get your free AI Evals certification.