[observability] Observability Coverage Report - 2026-08-16 #53243
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 #53529. |
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 20 representative workflow runs from the last 7 days, capped at one run per workflow and prioritizing failed runs where available. Both core observability surfaces met basic coverage expectations: all 20 firewall-enabled runs contained a discovered
access.log, and all 20 MCP-enabled runs contained discovered MCP telemetry undermcp-logs/rpc-messages.jsonl.No critical missing-log condition was found. The main issues are quality-related rather than absence-related. Firewall coverage is weakened because only 2 of 20 analyzed runs recorded any blocked egress, which means 18 runs do not demonstrate deny-path logging. MCP coverage relies entirely on the raw JSON-RPC fallback log; all 202 selected telemetry entries were parseable JSONL, but none included the explicit top-level
typefield required by this audit rubric, so every MCP-enabled run is a schema-quality warning rather than a telemetry absence failure.Key Alerts and Anomalies
No critical issues detected.
🔴 Critical Issues:
access.log, and no MCP-enabled run was missing bothgateway.jsonlandrpc-messages.jsonl.access.log.rpc-messages.jsonlfallback: 20 of 20 analyzed runs had parseable JSONL, but 0 of 202 entries exposed the rubric's required top-leveltypefield.safeoutputs.jsonlwas absent in 4 runs (AI Moderator,Avenger,Daily AWF Spec Compiler Surfacing Review,Smoke Gemini), reducing secondary output-tracing coverage.Coverage Summary
access.log)gateway.jsonlorrpc-messages.jsonl)📋 Detailed Run Analysis
Discovery Notes
sandbox/firewall/logs/access.log.mcp-logs/rpc-messages.jsonl.gateway.jsonl; all MCP coverage came from the canonical fallback file.Firewall-Enabled Runs
Missing Firewall Logs (
access.log)None.
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.jsonlMissing MCP Telemetry (no
gateway.jsonlorrpc-messages.jsonl)None.
🔍 Telemetry Quality Analysis
Firewall Log Quality
access.logentries analyzed: 2,813api.anthropic.com:443(375),api.githubcopilot.com:443(296),o205451.ingest.us.sentry.io:443(235)Gateway Log Quality
rpc-messages.jsonlfallback in all 20 runs;gateway.jsonlwas not present in the selected settypefield present: 0 of 202 entriessafeoutputs,serena,github,sentry,agenticworkflows,grafana,mcpscriptstools/callrequests: 59rpc-messages.jsonlwithout request/response duration pairingHealthy Runs Summary
Ponytail Reviewer,Smoke GeminiAvengerandSmoke Geminiboth hadaccess.log, MCP telemetry,agent-stdio.log, and AWF config metadataagent-stdio.log20/20, AWF config metadata 20/20,safeoutputs.jsonl16/20Recommended Actions
access.logconsistently captures both allow and deny paths.gateway.jsonlin more runs, or extendrpc-messages.jsonlso every entry includes an explicit top-leveltypefield compatible with the audit rubric.safeoutputs.jsonlemission even for noop-only or no-write runs so downstream debugging can correlate the decision path reliably.📊 Historical Trends
No retained baseline was available inside this run for day-over-day comparison. This report is a current 7-day-window snapshot using the most recent representative 20-run sample.
References: §31976674745, §31974687297, §31978446846
All reactions