[observability] Observability Coverage Report - 2026-08-07 #50953
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 #51237. |
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
Analyzed 14 recent workflow runs from the last 7 days, capped for breadth across workflows and weighted toward failed runs. The sampled set contained 4 failed runs, 9 successful runs, and 1 in-progress run. AWF firewall and MCP runtime evidence appeared in all 14 runs, but only one run, §31135930383, retained the critical observability artifacts needed for debugging.
Firewall coverage was 7.1% (1 of 14 firewall-enabled runs with
access.log), and MCP telemetry coverage was 7.1% (1 of 14 MCP-enabled runs with eithergateway.jsonlorrpc-messages.jsonl). That leaves 13 sampled runs missing both network egress audit logs and MCP JSONL telemetry. This is a critical observability gap because runtime logs show the AWF topology and MCP gateway path were active even when the artifacts were not retained.Key Alerts and Anomalies
Critical Issues:
access.log, so egress behavior could not be audited after the run.gateway.jsonlandrpc-messages.jsonl, so tool-call traces could not be reconstructed.WARNING: Squid access.log not found under /tmp/gh-aw/sandbox/firewall/logsandNo gateway.jsonl or rpc-messages.jsonl found for steering or DIFC_FILTERED scanning.Warnings:
rpc-messages.jsonl; nogateway.jsonlfile was discovered in any analyzed run.all_aw_info.jsonandsafeoutputs.jsonlwere present in only 1 of 14 runs.Coverage Summary
access.log)gateway.jsonlorrpc-messages.jsonl)Detailed Run Analysis
Firewall-Enabled Runs
Missing Firewall Logs (
access.log)MCP-Enabled Runs
rpc-messages.jsonlMissing MCP Telemetry (no
gateway.jsonlorrpc-messages.jsonl)Telemetry Quality Analysis
Firewall Log Quality
access.log:run-31135930383/sandbox/firewall/logs/access.logaccess.loglines analyzed: 531api.anthropic.com:443(119),o205451.ingest.us.sentry.io:443(35),otlp-gateway-prod-eu-west-2.grafana.net:443(35)Gateway Log Quality
run-31135930383/mcp-logs/rpc-messages.jsonlrpc-messages.jsonl(canonical fallback)agenticworkflows,github,safeoutputstools/callrequestsAdditional Telemetry Coverage
agent-stdio.logpresent: 13 of 14 runsrun_summary.jsonpresent: 14 of 14 runsall_aw_info.jsonpresent: 1 of 14 runssafeoutputs.jsonlorsafe_output.jsonlpresent: 1 of 14 runsHealthy Runs Summary
rpc-messages.jsonlrather than preferredgateway.jsonl, and the firewall sample did not exercise any deny-path logging.Recommended Actions
sandbox/firewall/logs/access.log.mcp-logs/gateway.jsonlnormcp-logs/rpc-messages.jsonlis present for an MCP-enabled run, including early-exit failures.all_aw_info.jsonand structured safe-output JSONL into the always-uploaded baseline artifact set so failed runs keep enough metadata to explain what was enabled.Historical Trends
This run analyzed a capped 14-run sample from the last 7 days. No prior daily observability report baseline was compared in this execution, so trend conclusions are intentionally deferred.
References:
All reactions