[observability] Observability Coverage Report - 2026-04-27 #28821
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 #29004. |
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 35 downloaded workflow runs from the last 7 days window. Of those, 33 had parsed summaries and 30 completed firewall-enabled runs could be evaluated for AWF firewall log coverage. Firewall observability is mostly present: 29 of 30 completed firewall-enabled runs included
sandbox/firewall/logs/access.logfor 96.7% coverage.MCP telemetry coverage is healthy for completed MCP-enabled runs. All 29 MCP-enabled completed runs had
mcp-logs/rpc-messages.jsonl, which is the canonical fallback whengateway.jsonlis absent. No completed MCP-enabled run was missing both telemetry formats.One completed firewall-enabled run is missing the critical Squid
access.logartifact. This is the only critical observability gap found in this report window.Key Alerts and Anomalies
🔴 Critical Issues:
firewall_enabled: true, but its artifact list does not includesandbox/firewall/logs/access.log. This prevents egress debugging for that run.access.logartifact but had 0 parsed firewall entries.run_summary.jsonandaw_info.json, so firewall and MCP coverage could not be classified from parsed metadata.Coverage Summary
access.log)gateway.jsonlorrpc-messages.jsonl)Detailed Run Analysis
Firewall-Enabled Runs
Missing Firewall Logs (
access.log)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.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlMissing MCP Telemetry
No completed MCP-enabled run was missing both
gateway.jsonlandrpc-messages.jsonl.Telemetry Quality Analysis
Firewall Log Quality
(unknown)in the parsed cache, so domain-level blocked analysis is limited.Gateway Log Quality
gateway.jsonl: 0 parsed completed runsrpc-messages.jsonl: 29 parsed completed runsagenticworkflows,github,mcpscripts,safeoutputs,semgrep,serena0ns, so latency quality should be treated as unavailable from this cache.Additional Telemetry
run_summary.jsonmetadata.aw_info.jsonmetadata.Recommended Actions
sandbox/firewall/logs/access.logis uploaded even when the agent job exits early or fails, using §25021569113 as the reproduction case.firewall_enabled: truebutaccess.logis absent fromartifacts_list.rpc-messages.jsonlas the required fallback MCP telemetry artifact, and consider restoring or addinggateway.jsonlwhere supported so duration and status metrics are available without relying on raw JSON-RPC reconstruction.run_summary.jsonandaw_info.json; if those failures occurred before agent setup, add a minimal pre-agent summary artifact for classification.Historical Trends
Historical comparison was not available from the current downloaded cache. This report should be compared with the next daily run to confirm whether the Design Decision Gate missing
access.logcase is isolated or recurring.Context
agenticworkflows logs --count 100 --start_date -7dReferences: §25021569113, §25025628914, §25025676227
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