Observability Agentic Harness (OAH) — Agentic Observability Pipeline

Status: pre-alpha. S1–S9 (surface mapping through the production readiness report) are implemented and tested — see Installation below to run them. S10–S11 (applying instrumentation and dynamically validating it) are not built yet. Follow ROADMAP.md for progress.

OAH is an agentic harness that builds LLM observability into an existing product (or produces observability requirements for a product being designed). Given access to a repository, it runs a multi-stage pipeline: it maps every LLM call site, retrieval step, and tool invocation; inventories existing telemetry; designs a target observability architecture; produces an implementation plan; then — in fix mode — generates and applies the instrumentation code and validates that telemetry actually flows by exercising the product and checking emitted events against a versioned schema.

OAH ships two co-equal deliverables:

1. Working instrumentation — code, event schema, collector config, and a validated Trace Completeness Rate for the target product.
2. A production readiness decision — a structured five-question readiness report (schema) ending in one of six evidence-led recommendations: ready / ready with conditions / remediate before release / pause and redesign / escalate for review / rollback or pause expansion — with the epistemic position stated (confirmed vs. assumed vs. unknown), scope exclusions, named owners, and the evidence that would change the decision. The gate never advances on confidence, urgency, or a successful demo alone.

The two reinforce each other: the readiness decision is only as good as the signals behind it, and the installed signals are designed backwards from the decisions they must support — every signal names the decision it serves and the owner who acts, or it is not built (the anti-metric-hoarding gate).

Inspiration & credit

The architecture of this project is directly inspired by Visa Vulnerability Agentic Harness (VVAH) — Visa's open-source agentic SAST pipeline built on learnings from Anthropic's Project Glasswing. We adopt its core design pattern and adapt it from vulnerability management to observability engineering:

We are not affiliated with Visa. VVAH is licensed under Apache-2.0; this project is an independent implementation of the pattern in a different domain and is also released under Apache-2.0.

Why

For LLM products, the dominant failure class is not "the call failed" but "the call succeeded and the output was bad": hallucination, irrelevant retrieval, silent context truncation, instruction bypass. Classic APM sees green dashboards while the product degrades. Observability for LLM systems therefore needs a domain model of its own — traces, generations, retrieval spans, tool spans, feedback events, eval datasets — plus governance over the telemetry itself (prompts and outputs are sensitive data).

The pipeline itself doesn't know it's about LLMs, though: S1–S3's mapping/gap-model mechanics, the S4 ops lens (release identifiers, alert plan, decision menu), S5's invariant gates, S7's runbook/roll-up structure, S8–S9's DTO and readiness-report shapes, and S11's TCR/validation-ladder concept are domain-agnostic SRE engineering. What's LLM-specific is concentrated in docs/event-model.md (the Generation/Retrieval entities S3 diffs against) and three of S4's eight lenses (generation-capture, retrieval, realtime-multimodal) — call it the GenAI domain pack the harness ships with. That's a scope choice, not an architectural limit: LLM observability is where OTel semantic conventions and APM tooling are least mature, so it's where a gap-modeling harness adds the most value first.

Retrofitting this by hand into an existing codebase is slow, inconsistent, and usually stalls after the first dashboard. OAH turns it into a repeatable, reviewable, agent-executed pipeline with human gates.

Pipeline (4 phases, 11 stages)

Detailed stage-by-stage description: docs/architecture.md. Target telemetry domain model: docs/event-model.md.

Installation

From PyPI

pip install oah
oah doctor .

Local development (venv)

git clone https://github.com/arno49/observability-agentic-harness.git
cd observability-agentic-harness
python3 -m venv .venv
source .venv/bin/activate          # Windows: .venv\Scripts\activate
pip install -e ".[dev]"

oah doctor .                       # sanity check
python -m pytest tests/ -q         # run the test suite

pip install -e ".[dev]" is an editable install: changes to oah/ take effect immediately without reinstalling. Drop [dev] if you only want to run the CLI, not the test suite.

S1–S9 need Python ≥ 3.10. The LLM-driven stages (everything past map --no-disambiguate/inventory/gaps/interview) also need an ANTHROPIC_API_KEY (or another provider supported by LiteLLM) in the environment — see Requirements below.

CLI

Implemented today (S1–S9):

oah doctor <target>                              # check credentials, backends, repo access
oah estimate <target>                            # scope & cost estimate — spends nothing
oah map <target> [-o out.json] [--no-disambiguate]     # S1: surface map (standalone audit)
oah inventory <target> [-o out.json]              # S2: existing telemetry inventory
oah interview <target> [-o context.yaml]          # S3: interactive owner interview
oah gaps <target> [--context context.yaml] [-o out.json]        # S3: gap model
oah design <target> [--context context.yaml] [-o out.json]      # S4 lenses + S5 gates + S6 panel
oah event-schema <target> [--context context.yaml] [-o out.json]  # S7: event schema
oah dtos <target> [--context context.yaml] [-o out.json]          # S8: implementation DTOs
oah readiness <target> [--context context.yaml] [-o out.json]     # S9: readiness report

--no-disambiguate on map, plus doctor/estimate/inventory/interview/gaps, run with no LLM credential required. design, event-schema, dtos, and readiness call the S4 lens skills and need an API credential.

oah map is intentionally a standalone deliverable: a one-shot observability audit of a codebase has value even if you never proceed to instrumentation.

Planned, not yet built (S10–S11):

oah instrument --repo ./product     # S10, --mode report-only|fix
oah validate --repo ./product       # S11
oah scan --repo ./product           # full run; --stop-after s9 for analysis-only
oah resume <run_id>                 # continue a crashed or session-limit-terminated run
                                     # from its last completed unit of work
oah check-drift --repo ./product    # cheap staleness check against DTOs' retest_triggers,
                                     # no full pipeline re-run

⚠️ Following VVAH's convention and warning: a full run in fix mode will edit source files in the target repo. --mode report-only and --stop-after s9 will be the non-mutating paths. Every applied change is planned to land as an individual commit/PR for review.

Design principles

1. Model before you design. The gap model (S3) focuses all downstream work, the same way VVAH's threat model focuses vulnerability hunting.
2. Skills, not a monolith. Every LLM stage is a versioned skill with a declared input/output schema, testable in isolation against a reference corpus (docs/SKILLS.md).
3. Deterministic where possible, LLM where necessary. AST scanning finds call sites; the LLM resolves ambiguity and designs. Invariant gates (S5) are pure code.
4. OpenTelemetry as the transport floor. Generated instrumentation targets OTel GenAI semantic conventions regardless of chosen backend, insuring the client against vendor lock-in. Opinionated backend targets (self-hosted Langfuse, OTel-only, managed) are selected by constraints, not fashion.
5. Never claim more validation than performed. S11 has an explicit degradation ladder (full dynamic → unit-level → generated smoke → needs_review); see docs/validation.md.
6. Telemetry is sensitive data. PII masking, role-scoped access to trace content, and retention policy are first-class requirements, not add-ons (docs/event-model.md, docs/security.md).
7. Signals exist for decisions. A health check says the service is reachable — not that users receive correct, approved, region- and role-appropriate, safely escalated answers. Every designed signal names the decision it supports and the role that acts; alerts no one owns are not created; evidence is judged by coverage class, not test count.
8. Dogfooding. Every OAH run emits a trace of its own stages in the very schema it installs for clients.
9. Language and modality are plugins, not the core. S1's registry and the S4 design lenses are architected so a new source language (TypeScript, Java, ...) or a new call-site modality (voice, image) is an additive extension, not a pipeline rewrite — Python and text-first are the first concrete targets because a pilot needs one deep example, not because the architecture assumes them.

Repository layout

docs/          architecture, event model, skills system, validation ladder, security
schemas/       JSON Schemas for inter-stage artifacts (the contract backbone)
skills/        skill drafts (SKILL.md per stage lens)
corpus/        reference repositories & eval fixtures for skill testing (planned)
.github/       CI, incl. a skills-bundling Action — debug tooling, not the
               pipeline itself; see docs/skills-bundle.md
ROADMAP.md     milestones, epics, spikes

Requirements (planned)

• Python ≥ 3.10 (S1–S9, implemented today)
• Models are configured per stage role through a LiteLLM abstraction layer — any provider or a local model (Ollama/vLLM) for skill stages; light-tier defaults for high-volume stages. S4's lens skills (and everything that depends on them: design, event-schema, dtos, readiness) need an ANTHROPIC_API_KEY (or another LiteLLM-supported provider) today. The planned agentic stages S10–S11 will additionally require the claude CLI — mirroring VVAH's Anthropic-only remediation/validation constraint. Enterprise deployments behind a private gateway supported via base-URL override + mTLS.

Limitations (read before you trust output)

• LLM-generated, non-deterministic. Designs and code changes are candidates requiring human review at the S9 gate and at every S10 commit.
• Dynamic validation depends on the target's runnability. If the product cannot be exercised (no tests, no compose, no smoke path), the best achievable verdict is needs_review — never validated.
• Elevated privilege. The harness reads source code that may contain prompts, keys, and data samples, and in fix mode edits it. Run only against repositories you own or are authorized to modify. See docs/security.md.
• No accuracy numbers yet. Skill precision/recall against the reference corpus will be published as the corpus lands (Epic E7).

License

Apache License 2.0 — see LICENSE and NOTICE.