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
Observability coverage was analyzed for the requested 7-day window using downloaded run artifacts. The available dataset in this window contained 37 agentic runs (all firewall-enabled), with 29 runs containing MCP artifacts.
Firewall observability is below target: access.log coverage is 78.38% (29/37). MCP telemetry coverage is healthy: 100% (29/29 MCP-enabled runs) had telemetry via rpc-messages.jsonl (canonical fallback). No MCP-enabled run was missing both gateway.jsonl and rpc-messages.jsonl.
Key Alerts and Anomalies
🔴 Critical Issues:
8 firewall-enabled runs are missing sandbox/firewall/logs/access.log.
This creates a direct debugging blind spot for network egress incidents in those runs.
⚠️Warnings:
No MCP telemetry absence warnings.
gateway.jsonl was not present in analyzed runs; telemetry relied on rpc-messages.jsonl.
Coverage Summary
Component
Runs Analyzed
Logs Present
Coverage
Status
AWF Firewall (access.log)
37 (firewall_enabled_workflows)
29
78.38%
🔴
MCP Gateway (gateway.jsonl or rpc-messages.jsonl)
29 (mcp_enabled_workflows)
29
100.00%
✅
📋 Detailed Run Analysis
Firewall-Enabled Runs (By Workflow)
Workflow
Runs
access.log Present
Missing
access.log Entries
AI Moderator
2
2
0
25
Agent Container Smoke Test
7
5
2
49
Auto-Triage Issues
2
2
0
23
Changeset Generator
7
5
2
235
Contribution Check
1
1
0
12
Copilot PR Prompt Pattern Analysis
1
1
0
47
Daily Documentation Updater
1
1
0
13
Daily Observability Report for AWF Firewall and MCP Gateway
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
Observability coverage was analyzed for the requested 7-day window using downloaded run artifacts. The available dataset in this window contained 37 agentic runs (all firewall-enabled), with 29 runs containing MCP artifacts.
Firewall observability is below target:
access.logcoverage is 78.38% (29/37). MCP telemetry coverage is healthy: 100% (29/29 MCP-enabled runs) had telemetry viarpc-messages.jsonl(canonical fallback). No MCP-enabled run was missing bothgateway.jsonlandrpc-messages.jsonl.Key Alerts and Anomalies
🔴 Critical Issues:
sandbox/firewall/logs/access.log.gateway.jsonlwas not present in analyzed runs; telemetry relied onrpc-messages.jsonl.Coverage Summary
firewall_enabled_workflows)mcp_enabled_workflows)📋 Detailed Run Analysis
Firewall-Enabled Runs (By Workflow)
Missing Firewall Logs (access.log)
MCP-Enabled Runs (By Workflow)
Missing MCP Telemetry (no gateway.jsonl or rpc-messages.jsonl)
No missing MCP telemetry runs detected.
🔍 Telemetry Quality Analysis
Firewall Log Quality
api.githubcopilot.com:443,api.openai.com:443,api.anthropic.com:443Gateway Log Quality
rpc-messages.jsonl(canonical fallback) in all MCP-enabled runsgateway.jsonlpresence: 0 runs in analyzed datasetsafeoutputs,github,playwright,serena,web-fetchHealthy Runs Summary
Recommended Actions
sandbox/firewall/logs/access.logis absent.gateway.jsonlalongside RPC logs where supported to improve response-time and field-level analysis.📊 Historical Trends
2026-03-17T02:29:40Zand2026-03-17T07:53:53Z.References:
Beta Was this translation helpful? Give feedback.
All reactions