[observability] Observability Coverage Report - 2026-08-08 #51479
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Daily Observability Report for AWF Firewall and MCP Gateway. A newer discussion is available at Discussion #51654. |
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
I analyzed 19 completed workflow runs from the last 7 days, capped for breadth across 18 workflows. Sixteen of those runs clearly enabled both the AWF firewall and MCP gateway based on recorded agent steps such as
Start MCP Gateway,Parse MCP Gateway logs for step summary, andPrint firewall logs.Observability coverage on the completed sample is critically degraded: 0 of 16 firewall-enabled runs retained
access.log, and 0 of 16 MCP-enabled runs retained eithergateway.jsonlorrpc-messages.jsonl. That leaves only 3 of 19 analyzed runs in a non-critical state, and those 3 were N/A because they did not exercise firewall or MCP execution paths.Two active runs were excluded from the coverage denominator because their artifacts are still live. Both already contain
sandbox/firewall/logs/access.logandmcp-logs/rpc-messages.jsonl, which points to a likely regression in artifact preservation or upload for completed runs rather than log generation itself.Key Alerts and Anomalies
Caution
Critical observability gap: all 16 completed runs that enabled firewall and MCP are missing both
access.logand MCP telemetry artifacts in the downloaded run bundle.Note
No parse-quality warnings were observed on completed runs because the required files were absent rather than malformed.
Critical runs in this sample include §31284413614, §31284289438, and §31283491276. In
PR Sous Chef§31284289438, the recorded agent steps show bothStart MCP GatewayandPrint firewall logs, but the final artifact list contains neither firewall log files nor MCP telemetry files.Coverage Summary
access.log)gateway.jsonlorrpc-messages.jsonl)Overall
observability_coverage_percentageon the analyzed sample is 15.8% (3/19). That percentage is entirely carried by the 3 N/A runs with no firewall or MCP path detected.Detailed Run Analysis
Firewall-Enabled Runs
Missing Firewall Logs (
access.log)MCP-Enabled Runs
Missing MCP Telemetry (
gateway.jsonlandrpc-messages.jsonl)Excluded Active Context
rpc-messages.jsonl(4 entries)rpc-messages.jsonl(4 entries)Telemetry Quality Analysis
Firewall Log Quality
/tmp/gh-aw/aw-mcp/logs/run-31284834381/sandbox/firewall/logs/access.log,/tmp/gh-aw/aw-mcp/logs/run-31284909598/sandbox/firewall/logs/access.logGateway Log Quality
rpc-messages.jsonlonly; nogateway.jsonlobserved/tmp/gh-aw/aw-mcp/logs/run-31284834381/mcp-logs/rpc-messages.jsonl,/tmp/gh-aw/aw-mcp/logs/run-31284909598/mcp-logs/rpc-messages.jsonlAdditional Telemetry Coverage
agent-stdio.logpresent in 16/19 analyzed runsagent_output.jsonpresent in 12/19 analyzed runsawf-config.jsonpresent in 1/19 analyzed runssafeoutputs.jsonlorsafe_output.jsonlpresent in 0/19 analyzed runsHealthy Runs Summary
The only non-critical runs in the capped sample were N/A runs with no firewall or MCP execution path detected: Daily Documentation Healer §31284776788, Daily AWF Spec Compiler Surfacing Review §31281355729, Daily Caveman Optimizer §31277890183.
Recommended Actions
sandbox/firewall/logs/access.logfor completed agent runs. The file is being generated on active runs, but it is absent from completed artifact bundles.mcp-logs/rpc-messages.jsonlormcp-logs/gateway.jsonla required post-run artifact whenever agent steps includeStart MCP GatewayorParse MCP Gateway logs for step summary.Historical Trends
This report did not compute a multi-day baseline beyond the current 7-day sample window. Within today's sampled completed runs, the coverage cliff is abrupt enough to treat as an active regression signal rather than normal variation.
References:
All reactions