AnyoneLearnAI
Start learning
Chapter DProduction monitoring labPage 4 of 8

Production monitoring lab

Validate outputs and schemas

Production monitoring lab is production work only when one frozen failure can be reproduced, one measurable gate can stop a release, and one operator can safely reverse it.

~14 minValidation

Before you start

Why this matters

Read this incident aloud: retrieval returns fewer chunks after an index refresh while HTTP status and model latency remain normal. In two minutes, write the earliest deterministic check that should fail, the telemetry signal you would inspect, and the action that must not happen automatically. Compare your answer with this chapter's boundary: operators see aggregates and redacted traces; raw user text requires break-glass access.

1Learn the idea

Read

Test behavior and evaluate quality

Testing this system requires more than checking that JSON parses. Build a small matrix with one normal case, one boundary case, the known failure, and one adversarial case. Freeze randomness and time. Stub the provider with recorded semantic outcomes rather than brittle prose snapshots. Then assert the decision, prohibited behavior, emitted metric, and absence of sensitive fields. The key behavioral assertion for this topic is assert decision.severity == "page" and decision.suspected_span == "retrieve".

Evaluate at two resolutions. First, case-level reasons must tell a developer exactly which expectation failed. Second, aggregate grounded answer rate by intent and release must meet at least 0.93 grounded, error rate below 1%, and p95 below 2500 ms on the frozen set and on important slices. A global pass can hide a severe intent, carrier, release, or customer workflow. Report numerator and denominator beside every rate; 0 failures over two cases is not strong evidence.

Before accepting a metric, attack it. If a shorter refusal raises a keyword score while usefulness collapses, the metric is being gamed. If lower cost excludes retries, the denominator is wrong. If latency ignores timeouts, the sample is censored. Compare automated scores with a small blinded human review and record disagreements as future fixtures.

For validation, execute the full matrix and print a machine-readable report plus a short developer summary. Exit nonzero on a violated critical gate; do not round a failing value into a pass.

Read

Focused implementation artifact

import pytest

CASES = [
    pytest.param({"release":"2026.07.18-canary","request_id":"req_a19","intent":"account_recovery","retrieved_count":0,"groundedness":0.22,"latency_ms":1180,"status":200,"cost_usd":0.011}, id="known-boundary"),
]

@pytest.mark.parametrize("case", CASES)
def test_behavioral_gate(case):
    decision = monitor.evaluate(events, baseline="2026.07.11", window="10m")
    assert decision.severity == "page" and decision.suspected_span == "retrieve"

def test_release_gate(report):
    assert report.sample_count >= 10
    assert report.critical_failures == 0

Read

Build the evaluation report

Expand the parameterized test into four named fixtures: benign control, threshold boundary, known regression, and adversarial misuse. For every row, assert the decision and at least one negative fact, such as no leak, no unauthorized action, no duplicate write, or no candidate promotion. Provider prose can vary; policy outcomes and required evidence cannot.

Aggregate the case results into grounded answer rate by intent and release and preserve numerator, denominator, critical failures, and slice keys. Apply at least 0.93 grounded, error rate below 1%, and p95 below 2500 ms exactly. Compare baseline and candidate on the same fixtures, then review disagreements where the automated score and a blinded human label diverge. Those disagreements are useful data, not noise to discard.

The regression named the global dashboard masks a 35% quality drop limited to account-recovery requests must fail before the fix and pass after it. Verify support_answer_grounded_ratio is emitted for both outcomes and that the failing report points to fixture IDs and trace IDs without embedding sensitive content. A failed gate leads operators to freeze promotion, page the owner, inspect retrieval traces, then roll back the index alias if confirmed.

Checking tutor…

Continue learning · glossary & guides