Log Mic Lab / Connected ideas
Connect a system question to the evidence that can answer it. This collection brings together event design, AI request boundaries, and the choice between logs, metrics, and traces. Start with the question you need to investigate, then work outward to the context and signals that make the answer reviewable.
Use these guides to decide what belongs in an event, where correlation should travel, and when a different signal is more appropriate. They emphasize boundaries and interpretation rather than assuming that collecting more information automatically produces a clearer explanation.
3 connected guides
Trace a model request through timings, retries, tool calls, configuration changes, and outcomes without collecting every message.
Read AI logging: what to capture around a model request
Use logs for event detail, metrics for measured behavior, and traces for the path of an operation, with a workflow that connects all three.
Read Logs, metrics, and traces: choosing the right signal
Design readable events with stable fields, clear outcomes, useful timing, and an investigation query to prove they work.
Read Structured logging: a practical guide to useful eventsExplore a shared question across different kinds of logs. Each collection brings together relevant guides and a useful reading path.