Research

Research seriesL2data science

Runtime Observability for Non-Deterministic AI

Traditional APM assumes deterministic services; autonomous AI systems are not. This series builds runtime observability for non-deterministic agents from the ground up: why classic monitoring fails, traces + metrics + evals as first-class telemetry, semantic capture of reasoning and tool calls (OpenTelemetry GenAI), detecting regressions without ground truth, and a cost-, privacy-, and sampling-aware reference architecture. Grounded in NIST AI RMF, NIST SP 800-137, OWASP LLM Top 10, the OpenTelemetry GenAI conventions, and the evaluation-methodology literature.

Murali Chillakuru·5 articles
  1. 1
    The Observability Gap: Why Traditional APM Fails on Non-Deterministic AI Systems

    APM assumes determinism, a binary success oracle, and bounded cardinality. Autonomous AI breaks all three - here is why observability must be rebuilt.

  2. 2
    The Pillars for AI: Traces, Metrics, and Evals as First-Class Telemetry

    Classic observability rests on logs, metrics, and traces - none of which carry correctness. For AI the load-bearing triad becomes traces, metrics, and evals.

  3. 3
    Semantic Telemetry: Capturing Reasoning, Tool Calls, and Decision Provenance with OpenTelemetry GenAI

    A trace with only timing is syntactic. Semantic telemetry records meaning - plan, tool I/O, and the evidence that grounded each claim - so a decision is auditable and replayable.

  4. 4
    Detecting Regressions Without Ground Truth: Reference-Free Evals and Drift Signals

    In production there is no answer key. You cannot measure accuracy - so you detect that behavior changed, from proxy signals, and infer whether it got worse.

  5. 5
    An Observability Reference Architecture: Sampling, Cost, Privacy, and the Feedback Loop

    Signals only matter once they are assembled into a system - with a sampling strategy, an honest cost model, a privacy plane, and a loop that turns alarms back into fixes and eval data.