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 20 recent agentic workflow runs from the last 7 days. Among completed runs with final artifacts, AWF Firewall coverage is 100% (5/5) and MCP telemetry coverage is 100% (5/5).
No completed firewall-enabled run is missing access.log, and no completed MCP-enabled run is missing both gateway.jsonl and rpc-messages.jsonl. Two downloaded runs are still in progress and should be re-evaluated after artifacts are uploaded.
Key Alerts and Anomalies
🔴 Critical Issues:
No critical issues detected for completed MCP-enabled or firewall-enabled runs.
⚠️Warnings:
Daily Observability Report for AWF Firewall and MCP Gateway §25139748302: firewall telemetry run still in progress; artifacts not final.
GitHub API Consumption Report Agent §25139474023: firewall telemetry run still in progress; artifacts not final.
17 completed runs had all applicable observability artifacts available. Skipped/non-agent runs are counted as not applicable for firewall and MCP coverage.
Recommended Actions
Keep rpc-messages.jsonl collection enabled as the canonical fallback; it provided 100% MCP telemetry coverage for completed MCP-enabled runs in this sample.
Re-check in-progress runs after completion before treating missing access.log or MCP artifacts as incidents.
Consider restoring or adding gateway.jsonl alongside rpc-messages.jsonl for richer duration and status metrics without protocol-level pairing.
📊 Historical Trends
No historical baseline was available in the downloaded dataset. This report should be compared with the next daily report to track coverage drift.
Analysis window: Last 7 days | Runs analyzed: 20 | Generated: 2026-04-29
Warning
Firewall blocked 4 domains
The following domains were blocked by the firewall during workflow execution:
ab.chatgpt.com
api.github.com
chatgpt.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 20 recent agentic workflow runs from the last 7 days. Among completed runs with final artifacts, AWF Firewall coverage is 100% (5/5) and MCP telemetry coverage is 100% (5/5).
No completed firewall-enabled run is missing
access.log, and no completed MCP-enabled run is missing bothgateway.jsonlandrpc-messages.jsonl. Two downloaded runs are still in progress and should be re-evaluated after artifacts are uploaded.Key Alerts and Anomalies
🔴 Critical Issues:
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)🔍 Telemetry Quality Analysis
Firewall Log Quality
access.logentries analyzed: 174Gateway Log Quality
rpc-messages.jsonlcanonical fallback for all runs with MCP telemetry in this sampleAdditional Artifacts
aw_info.json: 8/20agent-stdio.log: 6/20agent_output.json: 6/20safeoutputs.jsonl: 6/20Healthy Runs Summary
17 completed runs had all applicable observability artifacts available. Skipped/non-agent runs are counted as not applicable for firewall and MCP coverage.
Recommended Actions
rpc-messages.jsonlcollection enabled as the canonical fallback; it provided 100% MCP telemetry coverage for completed MCP-enabled runs in this sample.access.logor MCP artifacts as incidents.gateway.jsonlalongsiderpc-messages.jsonlfor richer duration and status metrics without protocol-level pairing.📊 Historical Trends
No historical baseline was available in the downloaded dataset. This report should be compared with the next daily report to track coverage drift.
References: §25139748302, §25139712382, §25139296264
Analysis window: Last 7 days | Runs analyzed: 20 | Generated: 2026-04-29
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