[observability] Observability Coverage Report - 2026-04-10 #25723
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 #25860. |
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
Observability coverage is healthy for completed runs in the last 7 days. I analyzed 23 downloaded runs and scoped coverage metrics to 18
completedruns to avoid false positives from active executions.For completed runs, AWF Firewall coverage is 100% (
18/18withaccess.log) and MCP telemetry coverage is 100% (18/18withrpc-messages.jsonland/orgateway.jsonl). There are no critical gaps that would block debugging for completed executions.Key Alerts and Anomalies
No critical issues detected for completed runs.
🔴 Critical Issues:
12/18completed firewall runs had only allowed traffic and no blocked events, which limits deny-path validation.5runs are currentlyin_progress; they were excluded from coverage scoring.Coverage Summary
access.log)gateway.jsonlorrpc-messages.jsonl)📋 Detailed Run Analysis
Firewall-Enabled Runs
Missing Firewall Logs (access.log)
None in completed runs.
MCP-Enabled Runs
Missing MCP Telemetry (no gateway.jsonl or rpc-messages.jsonl)
None in completed runs.
🔍 Telemetry Quality Analysis
Firewall Log Quality
access.logentries analyzed:3,8357unique12(0.31%)github.com,api.githubcopilot.com,api.anthropic.comGateway Log Quality
rpc-messages.jsonlon all completed MCP-enabled runs;gateway.jsonlnot observed in this sample window78github(50calls),safeoutputs(28calls)0%in parsed MCP failure metricsN/A(duration not derivable from this parsed rpc summary)Healthy Runs Summary
18/18agent-stdio.log,agent_output.json, safe output JSONL):18/18Recommended Actions
entries > 0when MCP is configured) to catch no-op telemetry cases like §24268687288.gateway.jsonladoption as a separate metric while continuing to treatrpc-messages.jsonlas valid fallback coverage.📊 Historical Trends
Historical trend comparison was not computed in this run because prior-day observability snapshots were not loaded in this analysis context.References:
Beta Was this translation helpful? Give feedback.
All reactions