[observability] Observability Coverage Report - 2026-08-18 #53859
Closed
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-08-19T23:57:46.283Z.
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Executive Summary
This report analyzed 20 completed workflow runs from the last-7d downloaded candidate set, using the latest completed run per workflow to maximize breadth within the 20-run cap. All sampled runs were firewall-enabled and MCP-enabled, so the sample exercises both observability surfaces directly.
Critical coverage is currently complete in the sampled set.
access.logwas present and non-empty in 20/20 firewall-enabled runs, and MCP telemetry was present in 20/20 MCP-enabled runs viarpc-messages.jsonl. Agent logs and workflow metadata were also present in 20/20 and 20/20 runs respectively.The main non-critical gap is telemetry richness, not telemetry presence. All sampled MCP-enabled runs relied on the canonical
rpc-messages.jsonlfallback rather thangateway.jsonl, which means telemetry coverage is healthy but structured duration fields were unavailable.safeoutputs.jsonlwas also absent in 3 sampled runs, which reduces end-to-end debugging context for those workflows.Key Alerts and Anomalies
Note
No critical observability failures were detected. No sampled firewall-enabled run was missing
access.log, and no sampled MCP-enabled run was missing bothgateway.jsonlandrpc-messages.jsonl.Warning
All 20 sampled MCP-enabled runs emitted
rpc-messages.jsonland none emittedgateway.jsonl. Coverage is still healthy because the fallback file is canonical, but per-request duration metrics were not available from structured gateway events.safeoutputs.jsonlwas missing in 3 sampled runs: §32186551970, §32191955239, and §32192747973.Coverage Summary
access.log)gateway.jsonlorrpc-messages.jsonl)Note
Additional telemetry coverage in the sample:
agent-stdio.log20/20,agent_output.json20/20,awf-config.json20/20,safeoutputs.jsonl17/20, and full critical-plus-secondary coverage in 17/20 runs.Detailed Run Analysis
Firewall-Enabled Runs
Missing Firewall Logs (
access.log)None.
MCP-Enabled Runs
rpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlMissing MCP Telemetry (no
gateway.jsonlorrpc-messages.jsonl)None.
Telemetry Quality Analysis
Firewall Log Quality
access.logentries analyzed: 4126MCP Log Quality
rpc-messages.jsonlin 20/20 sampled runs,gateway.jsonlin 0/20tools/callrequests: 52gateway.jsonldurations were not availableHealthy Runs Summary
access.logplus MCP telemetry (rpc-messages.jsonlfallback)agent-stdio.log,agent_output.json, andawf-config.jsonsafeoutputs.jsonlRecommended Actions
gateway.jsonlalongside the existingrpc-messages.jsonlfallback so response-time and per-event status metrics are available without extra derivation.safeoutputs.jsonlpublication for workflows that currently omit it, especially Agentic Workflow Audit Agent, Daily AWF Spec Compiler Surfacing Review, and Daily BYOK Ollama Test.TCP_DENIEDentry.Historical Trends
No persistent historical baseline was available in the downloaded artifacts. This report reflects a point-in-time sample of the latest completed run per workflow from the last-7d candidate set.
References: §32186403122, §32192747973, §32186551970
All reactions