You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Analyzed 76 artifact-rich workflow runs downloaded for the last 7 days. The MCP Gateway telemetry path is broadly healthy: 70/70 MCP-enabled runs (100.0%) included either gateway.jsonl or the canonical rpc-messages.jsonl fallback.
Firewall observability needs attention. 70/76 firewall-enabled runs (92.1%) included an extracted Squid access.log; 6 firewall-enabled runs were missing that critical artifact in the downloaded logs. The all-runs fetch hit the bridge timeout twice, so this report is based on the completed partial artifact corpus saved under /tmp/gh-aw/aw-mcp/logs/.
Key Alerts and Anomalies
🔴 Critical Issues:
Firewall access log missing: Daily Observability Report for AWF Firewall and MCP Gateway run §25528766474 (2026-05-08T00:01:01Z)
Firewall access log missing: Semantic Function Refactoring run §25528751299 (2026-05-08T00:00:32Z)
Firewall access log missing: Daily Documentation Healer run §25528717446 (2026-05-07T23:59:33Z)
Firewall access log missing: Smoke CI run §25521394926 (2026-05-07T20:51:35Z)
Firewall access log missing: Documentation Unbloat run §25510316635 (2026-05-07T17:01:42Z)
Firewall access log missing: Go Pattern Detector run §25504975077 (2026-05-07T15:19:45Z)
⚠️Warnings:
MCP telemetry file present but empty or incomplete: Contribution Check run §25522374874 using rpc-messages.jsonl
MCP telemetry file present but empty or incomplete: Auto-Triage Issues run §25516212977 using rpc-messages.jsonl
MCP telemetry file present but empty or incomplete: Contribution Check run §25511415054 using rpc-messages.jsonl
MCP telemetry file present but empty or incomplete: Daily Issues Report Generator run §25504870703 using rpc-messages.jsonl
Coverage Summary
Component
Runs Analyzed
Logs Present
Coverage
Status
AWF Firewall (access.log)
76
70
92.1%
⚠️
MCP Gateway (gateway.jsonl or rpc-messages.jsonl)
70
70
100.0%
⚠️
📋 Detailed Run Analysis
Firewall-Enabled Runs
Workflow
Run ID
access.log
Entries
Allowed
Blocked
Status
Daily Observability Report for AWF Firewall and MCP Gateway
Runs with complete required observability for enabled components: 66/76
Agent stdio logs present: 70 runs
Agent output artifacts present: 72 runs
Safe output artifacts present: 67 runs
Recommended Actions
Investigate the six firewall-enabled runs missing extracted access.log artifacts and confirm whether upload, artifact selection, or post-run extraction skipped the Squid logs.
Keep treating rpc-messages.jsonl as valid MCP telemetry, but add a quality check for empty files so warnings surface before debugging data is needed.
Tune the observability report fetch path to avoid the 120-second bridge timeout, likely by paginating or requesting only metadata plus firewall/MCP artifacts in smaller batches.
📊 Historical Trends
Historical comparison data was not present in the downloaded artifact corpus for this run. Store daily coverage percentages as a small JSON artifact to make week-over-week trend reporting deterministic.
Context: Analysis window: last 7 days | Runs analyzed: 76 | Generated: 2026-05-08
The following domains were blocked by the firewall during workflow execution:
api.github.com
github.com
💡 Tip:api.github.com is blocked because GitHub API access uses the built-in GitHub tools by default. Instead of adding api.github.com to network.allowed, use tools.github.mode: gh-proxy for direct pre-authenticated GitHub CLI access without requiring network access to api.github.com:
tools:
github:
mode: gh-proxy
See GitHub Tools for more information on gh-proxy mode.
To allow these domains, add them to the network.allowed list in your workflow frontmatter:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Executive Summary
Analyzed 76 artifact-rich workflow runs downloaded for the last 7 days. The MCP Gateway telemetry path is broadly healthy: 70/70 MCP-enabled runs (100.0%) included either
gateway.jsonlor the canonicalrpc-messages.jsonlfallback.Firewall observability needs attention. 70/76 firewall-enabled runs (92.1%) included an extracted Squid
access.log; 6 firewall-enabled runs were missing that critical artifact in the downloaded logs. The all-runs fetch hit the bridge timeout twice, so this report is based on the completed partial artifact corpus saved under/tmp/gh-aw/aw-mcp/logs/.Key Alerts and Anomalies
🔴 Critical Issues:
rpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlCoverage 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.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.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
🔍 Telemetry Quality Analysis
Firewall Log Quality
access.logentries analyzed: 16307Gateway Log Quality
rpc-messages.jsonlcanonical fallback; nogateway.jsonlfiles were present in this corpusHealthy Runs Summary
Recommended Actions
access.logartifacts and confirm whether upload, artifact selection, or post-run extraction skipped the Squid logs.rpc-messages.jsonlas valid MCP telemetry, but add a quality check for empty files so warnings surface before debugging data is needed.📊 Historical Trends
Historical comparison data was not present in the downloaded artifact corpus for this run. Store daily coverage percentages as a small JSON artifact to make week-over-week trend reporting deterministic.
Context: Analysis window: last 7 days | Runs analyzed: 76 | Generated: 2026-05-08
References: §25528766474, §25528751299, §25528717446
Warning
Firewall blocked 2 domains
The following domains were blocked by the firewall during workflow execution:
api.github.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