# AgentOps／AI-SRE CURRENT_STATUS: UNKNOWN OBSERVATION: SPEC_ONLY FRESHNESS: UNKNOWN PAGE_TYPE: reference CANONICAL_URL: /tools/ea-052-agentops-ai-sre CLAIM_IDS: none EVIDENCE_IDS: EVD-EA-052-URL-06C934AF218E, EVD-EA-052-URL-0744228B978B, EVD-EA-052-URL-01FA52816728, EVD-EA-052-URL-6ACAC33977CC, EVD-EA-052-URL-0F5EEBDD1974, EVD-EA-052-URL-9C2E21D90560, EVD-EA-052-URL-56E7946F43C6, EVD-EA-052-URL-DA8E50A714DD, EA-052-R11-RESEARCH, EA-052-R11-WEB-READBACK UNKNOWN_IDS: EA-052-UNKNOWN-01, EA-052-UNKNOWN-CURRENTNESS OPS_IDS: none ## Summary “AgentOps/AI-SRE is best treated as conventional SRE extended with AI-specific outcome and trajectory measurements. Availability and latency remain necessary but are insufficient: production agents also need task/end-state correctness, policy compliance, dependency behavior, repeated-run consistency, evaluation provenance and cost visibility. Automated evaluators are measurement instruments rather than ground truth, and benchmark pass rates should not be converted directly into production SLOs. Define auditable SLIs first, then apply SLO/error-budget, alerting, incident and continuous-improvement practices.” ## Current judgment - AgentOps/AI-SRE should be framed as an extension of SRE, not a replacement. Classical availability, latency, saturation, dependency health, change control, SLOs and error budgets remain necessary because agents still run on ordinary distributed systems. - AI-specific reliability needs additional outcome layers: task/end-state success, business-rule compliance, tool/retrieval correctness, refusal/safety behavior, trajectory consistency, human escalation rate, token/cost, and evaluation quality. A successful HTTP/model response is only transport/service success. - Keep SLI specification separate from SLI implementation. “Correctly completed customer task” is an outcome specification; an LLM judge score is only one possible measurement implementation and can itself drift or fail. - Evaluation telemetry should attach to the execution trace/session so operators can move from a degraded aggregate metric to the exact model/tool/retrieval trajectory. EA-051 provides the interoperability substrate for that linkage. - Reliability cannot be represented by one pass@1 or aggregate success metric. The cited 2026 research motivates repeated-run consistency, perturbation robustness, controlled dependency-failure tests and task-horizon sensitivity as separate axes. - Long-horizon workflows need explicit reliability budgets or step/trajectory risk analysis. Even when per-step reliability is high, dependent multi-step execution compounds failure risk; benchmark horizons must not be assumed representative of production horizons. - Error-budget logic can be adapted to AI outcomes, but only after an auditable SLI exists. Example: “percentage of in-scope claims-processing runs ending in policy-compliant terminal state within 120 s” is budgetable; “average judge score looks good” is insufficient without threshold, population and measurement reliability. - Incident response must preserve the full provenance needed for replay/diagnosis: prompt/config/model revision, tools and tool versions, retrieved evidence identifiers, policy version, trace, evaluator version and external dependency state. Exact content retention remains privacy-governed. ## Scope Enterprise AI Core / operations / governance / observability / benchmark-evaluation / implementation / incident response ## Confirmed - AgentOps/AI-SRE should be framed as an extension of SRE, not a replacement. Classical availability, latency, saturation, dependency health, change control, SLOs and error budgets remain necessary because agents still run on ordinary distributed systems. - AI-specific reliability needs additional outcome layers: task/end-state success, business-rule compliance, tool/retrieval correctness, refusal/safety behavior, trajectory consistency, human escalation rate, token/cost, and evaluation quality. A successful HTTP/model response is only transport/service success. - Keep SLI specification separate from SLI implementation. “Correctly completed customer task” is an outcome specification; an LLM judge score is only one possible measurement implementation and can itself drift or fail. - Evaluation telemetry should attach to the execution trace/session so operators can move from a degraded aggregate metric to the exact model/tool/retrieval trajectory. EA-051 provides the interoperability substrate for that linkage. - Reliability cannot be represented by one pass@1 or aggregate success metric. The cited 2026 research motivates repeated-run consistency, perturbation robustness, controlled dependency-failure tests and task-horizon sensitivity as separate axes. - Long-horizon workflows need explicit reliability budgets or step/trajectory risk analysis. Even when per-step reliability is high, dependent multi-step execution compounds failure risk; benchmark horizons must not be assumed representative of production horizons. - Error-budget logic can be adapted to AI outcomes, but only after an auditable SLI exists. Example: “percentage of in-scope claims-processing runs ending in policy-compliant terminal state within 120 s” is budgetable; “average judge score looks good” is insufficient without threshold, population and measurement reliability. - Incident response must preserve the full provenance needed for replay/diagnosis: prompt/config/model revision, tools and tool versions, retrieved evidence identifiers, policy version, trace, evaluator version and external dependency state. Exact content retention remains privacy-governed. ## UNKNOWN - EA-052-UNKNOWN-01: consensus terminology for AgentOps vs AI-SRE; validated local thresholds for quality SLOs; evaluator drift controls; how to budget compounded long-horizon risk; provider-equivalent telemetry coverage. - EA-052-UNKNOWN-CURRENTNESS: 外部根拠の再確認日がcanonical body/control-planeで確定していないため、currentnessはUNKNOWNとして保持する。日付を推測補完しない。 ## Evidence - EVD-EA-052-URL-06C934AF218E (RESEARCH): author/org: Google SRE — https://sre.google/workbook/implementing-slos/ - EVD-EA-052-URL-0744228B978B (RESEARCH): author/org: Google SRE / Steven Thurgood — https://sre.google/workbook/error-budget-policy/ - EVD-EA-052-URL-01FA52816728 (RESEARCH): author/org: Google SRE — https://sre.google/workbook/alerting-on-slos/ - EVD-EA-052-URL-6ACAC33977CC (RESEARCH): author/org: Arize AI / OpenInference — https://arize-ai.github.io/openinference/spec/ - EVD-EA-052-URL-0F5EEBDD1974 (RESEARCH): author/org: OpenTelemetry opentelemetry-python-genai contributors — https://github.com/open-telemetry/opentelemetry-python-genai/issues/98 - EVD-EA-052-URL-9C2E21D90560 (RESEARCH): author/org: Aayush Gupta — https://arxiv.org/abs/2601.06112 - EVD-EA-052-URL-56E7946F43C6 (RESEARCH): author/org: Shubhra Mittal — https://arxiv.org/abs/2609.01660 - EVD-EA-052-URL-DA8E50A714DD (RESEARCH): author/org: Harsh Raj et al. — https://arxiv.org/abs/2605.10516 - EA-052-R11-RESEARCH (RESEARCH): EA-052 監査済みresearch / canonical revision binding - EA-052-R11-WEB-READBACK (IMPL): EA-052 Web body identity / canonical readback ## Failure / limits Google SRE guidance is general service-operations guidance, not an AI-agent standard. Its value is the control-loop model, not direct proof of AI-specific thresholds. ## Failure / limits 2026 agent reliability papers are research evidence; they do not establish universal production failure rates or product guarantees. ## Failure / limits LLM-as-judge or automated evaluator output is measurement, not ground truth. Evaluator model/version/prompt changes can create apparent SLI movement without product behavior change. ## Failure / limits Offline benchmark gains may not survive real permissions, data freshness, rate limits, UI drift, business rules, or long task horizons. ## Failure / limits Provider telemetry gaps can make nominally identical SLO calculations non-comparable across stacks. ## Failure / limits Retry can improve user-visible success while increasing latency/cost and masking per-attempt instability; report logical-run and attempt-level metrics separately. ## Failure / limits bounded initial packet complete. Reopen when local production data exists, EA-051 schema mapping is finalized, or a provider-specific operational profile is built. --- ## Practice Production trace/evaluation linkage requires sufficient instrumentation coverage from EA-051. ## Practice Ground-truth or high-quality adjudication may require human review samples, domain validators or deterministic end-state checks. ## Practice Organization policy determines whether prompts/outputs/tool payloads can be retained for incident analysis. ## Practice Provider/model version changes require re-baselining when they materially alter quality or cost distributions. ## Practice Status: operational pattern is implementable now; universal AI-SRE standard is not established. Recommended minimum control loop: ## Practice Define user/business outcome SLIs first. ## Practice Add classical service SLIs: availability, latency, dependency/tool error, queue/saturation. ## Practice Add AI execution SLIs: valid terminal state, tool/retrieval correctness, policy compliance, escalation/refusal, trajectory length/retry, token/cost. ## Practice Attach offline/online evaluations to traces with evaluator provenance. ## Practice Set SLOs/error budgets only for measures with defensible denominators and measurement procedures. ## Practice Alert on burn/degradation; freeze or canary risky model/prompt/tool changes when agreed reliability budget is exhausted. ## Practice Run postmortems with trajectory/provenance evidence and convert findings into regression/fault-injection tests. ## Practice Use a portfolio rather than one score: repeated execution; semantically equivalent perturbations; dependency fault injection (timeouts/rate limits/partial responses/schema drift); long-horizon tasks; cost/latency distribution; policy/end-state validators. Report benchmark version, task horizon and environment. Do not turn research benchmark numbers into production SLO targets without local measurement. ## Practice Security/privacy: incident traces can contain the most sensitive AI data. Apply least-retention, redaction and access control; preserve hashes/IDs/version metadata when payloads cannot be retained. Audit: evaluator identity/version/prompt, policy version and model/tool/retrieval versions must accompany quality decisions. Cost: treat token/tool/retry spend as operational SLIs where economically material; reconcile telemetry-derived costs against billing sources. Operability: distinguish model-quality degradation from platform outage, provider outage, tool failure, retrieval/data failure, evaluator drift and policy change so the response owner is clear. ## Practice Use EA-051 to define the trace/evaluation event model required for operational SLIs. ## Practice Create an SLI catalog template separating outcome specification, measurement implementation, denominator/population, evaluator version, threshold and owner. ## Practice Add TEST_PROFILEs for repeated-run consistency, semantic perturbation, dependency fault injection and long-horizon regression. ## Practice For each provider mapping, document telemetry blind spots before claiming comparable SLO coverage. ## Practice Add incident taxonomy: platform/model/tool/retrieval/data/policy/evaluator/credential/GUI-browser dependency. ## Practice AgentOps/AI-SRE is retained as an evidence-backed dictionary operating-model proposal extending conventional SRE with AI-specific outcome/trajectory/evaluation signals; no universal production thresholds are asserted. Automated evaluators are measurement instruments, not ground truth. Research benchmark numbers are not production SLO targets. Preserve telemetry dependency on EA-051 and all OPEN_UNKNOWN. ## WHY_THIS_MATTERS_TO_UPDATE AgentはHTTP成功/失敗だけでは品質を測れない。モデル呼出し自体が成功しても、誤ったtool選択、partial completion、business-rule違反、長期trajectory崩壊、コスト暴走が起こり得る。公開後更新では、従来SREを捨てずにAI固有のquality/trajectory/evaluation signalsを重ねる運用モデルが必要になる。 ## SCOPE_ROUTING Enterprise AI Core / operations / governance / observability / benchmark-evaluation / implementation / incident response ## CLAIM_OR_RESEARCH_QUESTION AgentOps/AI-SREは従来SREと別物なのか、それともSREのservice reliability control loopにAI固有SLIとevaluationを追加する拡張として設計すべきか。production agentの可靠性を単一success rateではなく何で管理すべきか。 ## EVIDENCE TABLE 1. source class: primary operations guidance exact title: Implementing SLOs author/org: Google SRE canonical URL: https://sre.google/workbook/implementing-slos/ publication/update/access: Google SRE Workbook; accessed 2026-09-14 version/revision: web edition locator: SLI specification vs implementation; success ratios; SLO and error budget construction evidence label: VERIFIED_SPEC / SOURCE_REPORT relation: support/context 2. source class: primary operations guidance exact title: Example Error Budget Policy author/org: Google SRE / Steven Thurgood canonical URL: https://sre.google/workbook/error-budget-policy/ publication/update/access: policy dated 2018-02-19; accessed 2026-09-14 version/revision: web edition locator: release freeze/reliability work when error budget is exhausted; postmortem triggers evidence label: SOURCE_REPORT relation: support/context 3. source class: primary operations guidance exact title: Alerting on SLOs author/org: Google SRE canonical URL: https://sre.google/workbook/alerting-on-slos/ publication/update/access: accessed 2026-09-14 version/revision: web edition locator: burn-rate based alerting and budget-consumption model evidence label: SOURCE_REPORT relation: support/context 4. source class: author-maintained AI telemetry specification exact title: OpenInference Specification / Semantic Conventions author/org: Arize AI / OpenInference canonical URL: https://arize-ai.github.io/openinference/spec/ publication/update/access: accessed 2026-09-14 version/revision: current docs locator: traces across LLM/tool/retrieval/agent operations; human/LLM/code evaluator feedback; evaluation/annotation attachment evidence label: VERIFIED_SPEC / OSS_PRACTICE relation: support 5. source class: author-maintained implementation-gap report exact title: Add metrics support to Anthropic & Groq GenAI instrumentations #98 author/org: OpenTelemetry opentelemetry-python-genai contributors canonical URL: https://github.com/open-telemetry/opentelemetry-python-genai/issues/98 publication/update/access: opened 2026-05-14; accessed 2026-09-14 version/revision: issue #98 locator: cited signal coverage differs across provider instrumentations evidence label: SOURCE_REPORT / OSS_PRACTICE / PRODUCT_VOLATILE relation: limit 6. source class: research / reproducible benchmark proposal exact title: ReliabilityBench: Evaluating LLM Agent Reliability Under Production-Like Stress Conditions author/org: Aayush Gupta canonical URL: https://arxiv.org/abs/2601.06112 publication/update/access: 2026-01-03; accessed 2026-09-14 version/revision: arXiv 2601.06112 locator: repeated-run consistency, semantic perturbation robustness, tool/API fault injection; reliability surface R(k, ε, λ) evidence label: RESEARCH relation: support/context 7. source class: research exact title: How Fast Do Agents Rot? An Empirical Study of Long-Horizon Degradation in LLM Agents for Production Decision-Making author/org: Shubhra Mittal canonical URL: https://arxiv.org/abs/2609.01660 publication/update/access: 2026-08-31; accessed 2026-09-14 version/revision: arXiv 2609.01660 locator: long-horizon degradation; step-count reliability framing; benchmark-to-production horizon gap evidence label: RESEARCH relation: support/counter 8. source class: research exact title: Consistency as a Testable Property: Statistical Methods to Evaluate AI Agent Reliability author/org: Harsh Raj et al. canonical URL: https://arxiv.org/abs/2605.10516 publication/update/access: 2026-05-11; accessed 2026-09-14 version/revision: arXiv 2605.10516 locator: distinction between capability and execution robustness; trajectory-level consistency under semantically preserving perturbations evidence label: RESEARCH relation: support/context ## FINDINGS - AgentOps/AI-SRE should be framed as an extension of SRE, not a replacement. Classical availability, latency, saturation, dependency health, change control, SLOs and error budgets remain necessary because agents still run on ordinary distributed systems. - AI-specific reliability needs additional outcome layers: task/end-state success, business-rule compliance, tool/retrieval correctness, refusal/safety behavior, trajectory consistency, human escalation rate, token/cost, and evaluation quality. A successful HTTP/model response is only transport/service success. - Keep SLI specification separate from SLI implementation. “Correctly completed customer task” is an outcome specification; an LLM judge score is only one possible measurement implementation and can itself drift or fail. - Evaluation telemetry should attach to the execution trace/session so operators can move from a degraded aggregate metric to the exact model/tool/retrieval trajectory. EA-051 provides the interoperability substrate for that linkage. - Reliability cannot be represented by one pass@1 or aggregate success metric. The cited 2026 research motivates repeated-run consistency, perturbation robustness, controlled dependency-failure tests and task-horizon sensitivity as separate axes. - Long-horizon workflows need explicit reliability budgets or step/trajectory risk analysis. Even when per-step reliability is high, dependent multi-step execution compounds failure risk; benchmark horizons must not be assumed representative of production horizons. - Error-budget logic can be adapted to AI outcomes, but only after an auditable SLI exists. Example: “percentage of in-scope claims-processing runs ending in policy-compliant terminal state within 120 s” is budgetable; “average judge score looks good” is insufficient without threshold, population and measurement reliability. - Incident response must preserve the full provenance needed for replay/diagnosis: prompt/config/model revision, tools and tool versions, retrieved evidence identifiers, policy version, trace, evaluator version and external dependency state. Exact content retention remains privacy-governed. ## LIMITS / COUNTEREVIDENCE / FAILURE ENVELOPE - Google SRE guidance is general service-operations guidance, not an AI-agent standard. Its value is the control-loop model, not direct proof of AI-specific thresholds. - 2026 agent reliability papers are research evidence; they do not establish universal production failure rates or product guarantees. - LLM-as-judge or automated evaluator output is measurement, not ground truth. Evaluator model/version/prompt changes can create apparent SLI movement without product behavior change. - Offline benchmark gains may not survive real permissions, data freshness, rate limits, UI drift, business rules, or long task horizons. - Provider telemetry gaps can make nominally identical SLO calculations non-comparable across stacks. - Retry can improve user-visible success while increasing latency/cost and masking per-attempt instability; report logical-run and attempt-level metrics separately. ## AVAILABILITY_GATES - Production trace/evaluation linkage requires sufficient instrumentation coverage from EA-051. - Ground-truth or high-quality adjudication may require human review samples, domain validators or deterministic end-state checks. - Organization policy determines whether prompts/outputs/tool payloads can be retained for incident analysis. - Provider/model version changes require re-baselining when they materially alter quality or cost distributions. ## IMPLEMENTATION_STATE Status: operational pattern is implementable now; universal AI-SRE standard is not established. Recommended minimum control loop: 1. Define user/business outcome SLIs first. 2. Add classical service SLIs: availability, latency, dependency/tool error, queue/saturation. 3. Add AI execution SLIs: valid terminal state, tool/retrieval correctness, policy compliance, escalation/refusal, trajectory length/retry, token/cost. 4. Attach offline/online evaluations to traces with evaluator provenance. 5. Set SLOs/error budgets only for measures with defensible denominators and measurement procedures. 6. Alert on burn/degradation; freeze or canary risky model/prompt/tool changes when agreed reliability budget is exhausted. 7. Run postmortems with trajectory/provenance evidence and convert findings into regression/fault-injection tests. ## BENCHMARK_OR_EVAL Use a portfolio rather than one score: repeated execution; semantically equivalent perturbations; dependency fault injection (timeouts/rate limits/partial responses/schema drift); long-horizon tasks; cost/latency distribution; policy/end-state validators. Report benchmark version, task horizon and environment. Do not turn research benchmark numbers into production SLO targets without local measurement. ## SECURITY / PRIVACY / AUDIT / COST / OPERABILITY Security/privacy: incident traces can contain the most sensitive AI data. Apply least-retention, redaction and access control; preserve hashes/IDs/version metadata when payloads cannot be retained. Audit: evaluator identity/version/prompt, policy version and model/tool/retrieval versions must accompany quality decisions. Cost: treat token/tool/retry spend as operational SLIs where economically material; reconcile telemetry-derived costs against billing sources. Operability: distinguish model-quality degradation from platform outage, provider outage, tool failure, retrieval/data failure, evaluator drift and policy change so the response owner is clear. ## SAFE_WORDING_FOR_FUTURE_BOOK “AgentOps/AI-SRE is best treated as conventional SRE extended with AI-specific outcome and trajectory measurements. Availability and latency remain necessary but are insufficient: production agents also need task/end-state correctness, policy compliance, dependency behavior, repeated-run consistency, evaluation provenance and cost visibility. Automated evaluators are measurement instruments rather than ground truth, and benchmark pass rates should not be converted directly into production SLOs. Define auditable SLIs first, then apply SLO/error-budget, alerting, incident and continuous-improvement practices.” ## UPDATE_WORK_HANDOFF 1. Use EA-051 to define the trace/evaluation event model required for operational SLIs. 2. Create an SLI catalog template separating outcome specification, measurement implementation, denominator/population, evaluator version, threshold and owner. 3. Add TEST_PROFILEs for repeated-run consistency, semantic perturbation, dependency fault injection and long-horizon regression. 4. For each provider mapping, document telemetry blind spots before claiming comparable SLO coverage. 5. Add incident taxonomy: platform/model/tool/retrieval/data/policy/evaluator/credential/GUI-browser dependency. ## OPEN_UNKNOWN consensus terminology for AgentOps vs AI-SRE; validated local thresholds for quality SLOs; evaluator drift controls; how to budget compounded long-horizon risk; provider-equivalent telemetry coverage. ## STOP_CONDITION bounded initial packet complete. Reopen when local production data exists, EA-051 schema mapping is finalized, or a provider-specific operational profile is built. --- ## AUDITED_BOUNDARY AgentOps/AI-SRE is retained as an evidence-backed dictionary operating-model proposal extending conventional SRE with AI-specific outcome/trajectory/evaluation signals; no universal production thresholds are asserted. Automated evaluators are measurement instruments, not ground truth. Research benchmark numbers are not production SLO targets. Preserve telemetry dependency on EA-051 and all OPEN_UNKNOWN. NEXT: /agent/start.json STOP: This is a knowledge projection, not an execution order.