[observability] Observability Coverage Report - 2026-04-28 #29004
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 #29219. |
Beta Was this translation helpful? Give feedback.
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 94 completed workflow runs retrieved from the last-7-days query. The downloaded sample covers the latest available high-activity slice (2026-04-28 to 2026-04-28); 6 in-progress runs were retrieved but excluded from coverage scoring because final artifacts are not available until completion.
AWF Firewall observability is mostly healthy at 98.9% coverage (93/94 completed firewall-enabled runs with
access.log). MCP telemetry coverage is healthy at 100.0% (93/93 MCP-enabled runs with eithergateway.jsonlor the canonicalrpc-messages.jsonlfallback). All observed MCP telemetry came fromrpc-messages.jsonl; no completed run in this sample publishedgateway.jsonl.Key Alerts and Anomalies
🔴 Critical Issues:
access.logbut parsed with zero firewall entries, mostly Smoke CI runs.rpc-messages.jsonlbut had zero derived MCP entries/tool calls in the parsed summary.Coverage 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)No completed MCP-enabled runs were missing both
gateway.jsonlandrpc-messages.jsonl.Deferred In-Progress Runs
Telemetry Quality Analysis
Firewall Log Quality
access.logentries analyzed: 2169Gateway Log Quality
rpc-messages.jsonlcanonical fallback for 93 completed MCP-enabled runs;gateway.jsonlfor 0 runsrpc-messages.jsonland duration pairing was not emitted in the parsed aggregateAdditional Artifacts
agent-stdio.logpresent: 93/94 completed runsagent_output.jsonpresent: 92/94 completed runsaw_info.jsonpresent: 94/94 completed runssafeoutputs.jsonlpresent: 90/94 completed runsRecommended Actions
sandbox/firewall/logs/access.log; this is the only completed firewall-enabled run where the critical Squid log was absent.access.logexists but parsed with zero entries to confirm whether those jobs had no network activity after firewall startup or whether parser/artifact timing missed Squid events.rpc-messages.jsonlas valid MCP telemetry, but consider restoring or documentinggateway.jsonlemission if structured per-event duration/status fields are still expected for dashboards.Historical Trends
No prior local baseline was available in this run. Current completed-run baseline: firewall coverage 98.9%, MCP telemetry coverage 100.0%, blocked firewall request rate 7.7%, MCP error rate 0.0%.
References: §25061830104, §25080677949, §25079988548
Warning
Firewall blocked 4 domains
The following domains were blocked by the firewall during workflow execution:
ab.chatgpt.comapi.github.comchatgpt.comgithub.com💡 Tip:
api.github.comis blocked because GitHub API access uses the built-in GitHub tools by default. Instead of addingapi.github.comtonetwork.allowed, usetools.github.mode: gh-proxyfor direct pre-authenticated GitHub CLI access without requiring network access toapi.github.com:See GitHub Tools for more information on
gh-proxymode.To allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.
Beta Was this translation helpful? Give feedback.
All reactions