[observability] Observability Coverage Report - 2026-08-13 #52388
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 #52597. |
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
I analyzed 18 completed workflow runs from the last 7 days, selected from a 30-run repository-wide fetch and capped for breadth across workflows. 15 runs entered the firewall-enabled agent runtime and 15 runs used the MCP gateway; all of those runs had the required primary observability artifacts present.
No critical observability gaps were found in the sampled agent-started runs: every firewall-enabled run had a discoverable
access.log, and every MCP-enabled run had MCP telemetry viarpc-messages.jsonl. The main issues are quality-related rather than missing-data related: the sample did not exercise any denied firewall requests, and all MCP telemetry came from the JSON-RPC fallback rather than the richergateway.jsonlformat, which limits latency analysis.Three failed runs never entered the agent runtime (
Turns=0, noawf-config.json, no firewall or MCP artifacts), so they are classified asN/Arather than missing observability. Additional telemetry coverage was otherwise strong:agent-stdio.logwas present in 15/18 analyzed runs,safeoutputs.jsonlin 14/18, andawf-config.jsonin 15/18.Key Alerts and Anomalies
No critical issues detected.
Warning
The firewall sample captured 3188 allowed requests and 0 denied requests across 3188
access.logentries. Coverage for allow-path debugging is complete, but deny-path observability was not exercised in this sample.Warning
All MCP-enabled runs relied on
rpc-messages.jsonl; no sampled run emittedgateway.jsonl. The fallback logs were parseable and sufficient for server/tool/error counts, but they did not support reliable response-time pairing in this sample.Coverage Summary
access.log)firewall_enabled_workflows)gateway.jsonlorrpc-messages.jsonl)mcp_enabled_workflows)📋 Detailed Run Analysis
Run Scope
Firewall-Enabled Runs
run-31647146503/sandbox/firewall/logs/access.logrun-31644531765/sandbox/firewall/logs/access.logrun-31643652320/sandbox/firewall/logs/access.logrun-31643436414/sandbox/firewall/logs/access.logrun-31643310022/sandbox/firewall/logs/access.logrun-31643310020/sandbox/firewall/logs/access.logrun-31651782846/sandbox/firewall/logs/access.logrun-31650802957/sandbox/firewall/logs/access.logrun-31650574304/sandbox/firewall/logs/access.logrun-31650511800/sandbox/firewall/logs/access.logrun-31649732812/sandbox/firewall/logs/access.logrun-31645591353/sandbox/firewall/logs/access.logrun-31643652269/sandbox/firewall/logs/access.logrun-31643652380/sandbox/firewall/logs/access.logrun-31643436571/sandbox/firewall/logs/access.logMissing Firewall Logs (
access.log)None in the analyzed firewall-enabled run set.
MCP-Enabled Runs
rpc-messages.jsonl(run-31647146503/mcp-logs/rpc-messages.jsonl)rpc-messages.jsonl(run-31644531765/mcp-logs/rpc-messages.jsonl)rpc-messages.jsonl(run-31643652320/mcp-logs/rpc-messages.jsonl)rpc-messages.jsonl(run-31643436414/mcp-logs/rpc-messages.jsonl)rpc-messages.jsonl(run-31643310022/mcp-logs/rpc-messages.jsonl)rpc-messages.jsonl(run-31643310020/mcp-logs/rpc-messages.jsonl)rpc-messages.jsonl(run-31651782846/mcp-logs/rpc-messages.jsonl)rpc-messages.jsonl(run-31650802957/mcp-logs/rpc-messages.jsonl)rpc-messages.jsonl(run-31650574304/mcp-logs/rpc-messages.jsonl)rpc-messages.jsonl(run-31650511800/mcp-logs/rpc-messages.jsonl)rpc-messages.jsonl(run-31649732812/mcp-logs/rpc-messages.jsonl)rpc-messages.jsonl(run-31645591353/mcp-logs/rpc-messages.jsonl)rpc-messages.jsonl(run-31643652269/mcp-logs/rpc-messages.jsonl)rpc-messages.jsonl(run-31643652380/mcp-logs/rpc-messages.jsonl)rpc-messages.jsonl(run-31643436571/mcp-logs/rpc-messages.jsonl)Missing MCP Telemetry (no
gateway.jsonlorrpc-messages.jsonl)None in the analyzed MCP-enabled run set.
🔍 Telemetry Quality Analysis
Firewall Log Quality
access.logentries analyzed: 3188Gateway Log Quality
rpc-messages.jsonlin all MCP-enabled sampled runs;gateway.jsonlwas not observedAdditional Telemetry
agent-stdio.log: present in 15/18 analyzed runs, matching every agent-started runsafeoutputs.jsonl: present in 14/18 analyzed runs; absent in one agent-started failed run and in the three zero-turn failuresawf-config.json: present in 15/18 analyzed runs, and absent only in the three zero-turn failuresHealthy Runs Summary
Recommended Actions
gateway.jsonlalongside the JSON-RPC fallback so per-server latency and status metrics are available without request/response reconstruction.TCP_DENIEDlogging is continuously verified.safeoutputs.jsonland minimal runtime metadata when the agent starts but exits before completion.📊 Historical Trends
This run analyzed a single 7-day sample window and did not load prior daily observability reports, so no longitudinal trendline is included here.
References: §31647146503, §31650511800, §31644531765
Analysis window: Last 7 days | Runs analyzed: 18
All reactions