[observability] Observability Coverage Report - 2026-04-12 #25952
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 #26110. |
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
Observability artifacts were analyzed for the last 7 days using locally downloaded workflow-run logs under
/tmp/gh-aw/aw-mcp/logsand filtered by run creation time (>= 2026-04-05). A total of 229 runs had readablerun_summary.jsonmetadata in this window.The audit found a major telemetry gap for both target components. For runs flagged as firewall-enabled by
aw_info.json, 0/121 had readableaccess.logartifacts. For runs with MCP log directories, only 24/120 had MCP telemetry (rpc-messages.jsonl), and 0 hadgateway.jsonl.Key Alerts and Anomalies
🔴 Critical Issues:
access.logmissing in 121/121 firewall-enabled runs (100% missing).gateway.jsonlandrpc-messages.jsonlabsent in 96/120 MCP-enabled runs (80% missing).rpc-messages.jsonlpresent but empty in 1 run: §24164515813.Coverage Summary
access.log)gateway.jsonlorrpc-messages.jsonl)Additional context:
📋 Detailed Run Analysis
Firewall-Enabled Runs (Most Recent 20)
Missing Firewall Logs (
access.log) (Most Recent 20)MCP-Enabled Runs (Most Recent 20)
Missing MCP Telemetry (Most Recent 20)
🔍 Telemetry Quality Analysis
Firewall Log Quality
access.logentries analyzed: 0Gateway/MCP Log Quality
gateway.jsonl: 0,rpc-messages.jsonl: 24, none: 96agenticworkflows,github,mcpscripts,playwright,safeoutputs,serena,tavilyHealthy Runs Summary
0entries despite file presence): §24164515813Recommended Actions
access.logartifact upload mandatory for all runs withfirewall_enabled=true, and fail the run if artifact collection is skipped.mcp-logs/exists, require at least one ofgateway.jsonlorrpc-messages.jsonl; fail post-job validation otherwise.📊 Historical Trends
aw_info.Context
run_summary.jsonin local downloaded artifacts)References:
Warning
The following domains were blocked by the firewall during workflow execution:
ab.chatgpt.comapi.github.comchatgpt.comgithub.comTo 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