[observability] Observability Coverage Report - 2026-04-24 #28375
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 #28525. |
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 36 unique workflow runs from the last 7 days after deduplicating one duplicate entry in the MCP logs index. Coverage metrics below are calculated from 32 completed runs with
run_summary.json, while 4 in-progress runs are tracked separately because their final artifacts have not been uploaded yet.AWF Firewall coverage was 96.4% across 28 completed firewall-enabled runs, with 1 confirmed missing
access.logartifact. MCP telemetry coverage was 93.8% across 32 completed agent runs, with 2 runs missing all MCP telemetry. Nogateway.jsonlartifacts were observed; healthy MCP coverage in this window came entirely from the canonical fallbackmcp-logs/rpc-messages.jsonl.Overall completed-run observability coverage was 93.8% (30/32 runs meeting all applicable artifact checks). Additional telemetry was present in 30/32 completed runs for
agent-stdio.logand 26/32 completed runs forsafeoutputs.jsonl.Key Alerts and Anomalies
🔴 Critical Issues:
sandbox/firewall/logs/access.log.gateway.jsonlandrpc-messages.jsonl.gateway.jsonlandrpc-messages.jsonl.aw_info.json; firewall enablement could not be confirmed from artifacts.run_summary.json.Coverage Summary
access.log)firewall_enabled_workflows)gateway.jsonlorrpc-messages.jsonl)mcp_enabled_workflows)Detailed Run Analysis
Firewall-Enabled Runs
Missing Firewall Logs (access.log)
MCP-Enabled Runs
Missing MCP Telemetry (no gateway.jsonl or rpc-messages.jsonl)
In-Progress Runs
Telemetry Quality Analysis
Firewall Log Quality
access.logrequests summarized: 1225MCP Log Quality
rpc-messages.jsonlonlygateway.jsonlruns observed: 0rpc-messages.jsonlruns observed: 30timestamp,direction,type,server_id,payload)24913567782: 70 events, 33 outgoingtools/callrequests, serversgithub,safeoutputs24913976844: 80 events, 33 outgoingtools/callrequests, serversagenticworkflows,github,mcpscripts,playwright,safeoutputs,serena,tavily24913976862: 74 events, 31 outgoingtools/callrequests, serversagenticworkflows,github,mcpscripts,playwright,safeoutputs,serenaagenticworkflows,github,mcpscripts,playwright,safeoutputs,serena,tavily)safeoutputs62,github55,serena20,mcpscripts7,playwright5,agenticworkflows1,tavily1Healthy Runs Summary
rpc-messages.jsonlfallback rather thangateway.jsonlCONNECT 200 TCP_TUNNELentries and proxy noise such asNONE_NONE:HIER_NONE error:transaction-end-before-headers; the summarized firewall counters remain the more reliable source for allow/block totalsRecommended Actions
Smoke CIruns §24913094891 and §24914380736 exited after the agent job started but before MCP telemetry was uploaded.access.logand MCP JSONL artifacts.rpc-messages.jsonlpresence on every completed agent run, and keepgateway.jsonloptional until that artifact is actually emitted in this repository.Historical Trends
Historical trend comparison was not computed in this run. The current report is a point-in-time 7-day coverage audit based on the latest downloaded run set.
Context
workflow_runs_analyzed: 36 unique runsReferences: §24913094891, §24914380736, §24916931881
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