[observability] Observability Coverage Report - 2026-09-04 #58637
Replies: 1 comment
|
Ook ook! Caveman bot say hello. Me run smoke test, all fire and rock solid. Good discussion, me like. Warning Firewall blocked 7 domainsThe following domains were blocked by the firewall during workflow execution:
To allow these domains, add them to the network:
allowed:
- defaults
- "accounts.google.com"
- "android.clients.google.com"
- "clients2.google.com"
- "contentautofill.googleapis.com"
- "host.docker.internal"
- "www.google.com"
- "www.gstatic.com"See Network Configuration for more information.
|
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
20recent workflow runs downloaded from the last 7-day window, capped per the workflow guidance and limited to at most two runs per workflow. The fetched sample was recent-heavy: the initial repository-widelogscall returned 30 runs spanning roughly one hour on 2026-09-04, so this report is a representative capped slice rather than full-week census coverage.AWF Firewall coverage was
65.0%across20firewall-enabled runs, and MCP telemetry coverage was65.0%across20MCP-enabled runs.7runs had critical observability gaps, all caused by missing runtime artifacts on workflows whose compiled definitions include both firewall and MCP Gateway steps.Where logs were present, the firewall and MCP story was consistent:
access.logexisted undersandbox/firewall/logs/, and MCP telemetry was recorded via the canonical fallbackmcp-logs/rpc-messages.jsonl. No analyzed run exposedgateway.jsonl; current healthy coverage relies entirely on the RPC fallback path.Key Alerts and Anomalies
🔴 Critical Issues:
33927409720is firewall-enabled but missingaccess.log.33927409720is MCP-enabled but missing bothgateway.jsonlandrpc-messages.jsonl.33927409806is firewall-enabled but missingaccess.log.33927409806is MCP-enabled but missing bothgateway.jsonlandrpc-messages.jsonl.33927409809is firewall-enabled but missingaccess.log.33927409809is MCP-enabled but missing bothgateway.jsonlandrpc-messages.jsonl.33927409826is firewall-enabled but missingaccess.log.33927409826is MCP-enabled but missing bothgateway.jsonlandrpc-messages.jsonl.33927409837is firewall-enabled but missingaccess.log.33927409837is MCP-enabled but missing bothgateway.jsonlandrpc-messages.jsonl.33927409908is firewall-enabled but missingaccess.log.33927409908is MCP-enabled but missing bothgateway.jsonlandrpc-messages.jsonl.33927325443is firewall-enabled but missingaccess.log.33927325443is MCP-enabled but missing bothgateway.jsonlandrpc-messages.jsonl.33930351076: firewall log present with 22 entries, allowed=4, blocked=033927521651: firewall log present with 704 entries, allowed=259, blocked=033927521662: firewall log present with 593 entries, allowed=148, blocked=033927521473: firewall log present with 25 entries, allowed=14, blocked=033927521595: firewall log present with 64 entries, allowed=18, blocked=033927293402: firewall log present with 893 entries, allowed=5, blocked=033925327513: firewall log present with 6 entries, allowed=2, blocked=033925033555: firewall log present with 22 entries, allowed=4, blocked=033923711273: firewall log present with 10 entries, allowed=2, blocked=033923268323: firewall log present with 97 entries, allowed=58, blocked=0Coverage Summary
access.log)gateway.jsonlorrpc-messages.jsonl)📋 Detailed Run Analysis
Firewall-Enabled Runs
Missing Firewall Logs (
access.log)MCP-Enabled Runs
Missing MCP Telemetry (no
gateway.jsonlorrpc-messages.jsonl)🔍 Telemetry Quality Analysis
Firewall Log Quality
access.logentries analyzed: 2724Gateway Log Quality
rpc-messages.jsonl(canonical fallback) on all healthy MCP runs;gateway.jsonlabsent in this samplerpc-messages.jsonlwithout request/response pairingHealthy Runs Summary
3 analyzed runs had both firewall and MCP telemetry present. Representative healthy examples:
PR Sous Chef§33930375719,Ponytail Reviewer§33927521624,Issue Monster§33924924030.Recommended Actions
Start MCP GatewayandPrint firewall logs; missing artifacts are the direct cause of all critical findings./tmp/gh-aw/sandbox/firewall/logs/and/tmp/gh-aw/mcp-logs/so failed agent jobs still emit debugging telemetry.gateway.jsonlgeneration alongside the existing RPC fallback, since the current healthy runs depend entirely onrpc-messages.jsonlfor MCP observability.📊 Historical Trends
Historical trend analysis is not included in this single-sample daily report. The current run provides a point-in-time coverage slice from the last 7 days.
Report generated automatically by the Daily Observability Report workflow
Analysis window: Last 7 days | Runs analyzed: 20
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
ab.chatgpt.comTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.
All reactions