[observability] Observability Coverage Report - 2026-08-04 #50118
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 #50424. |
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 sampled 20 workflow runs from the last 7 days. The observability paths we care about are covered in the sample: both firewall-enabled runs preserved access.log, and all five MCP-enabled runs preserved rpc-messages.jsonl fallback telemetry.
The gap is quality, not loss. The firewall sample is allow-only, so there is no blocked egress example to debug against. MCP telemetry is present, but all sampled MCP runs use rpc-messages.jsonl instead of gateway.jsonl, so structured per-event gateway metrics are unavailable.
Key Alerts and Anomalies
No critical issues detected.
🔴 Critical Issues:
Coverage Summary
📋 Detailed Run Analysis
Sampled Runs
Firewall-Enabled Runs
Missing Firewall Logs (access.log)
None in the sampled firewall-enabled runs.
MCP-Enabled Runs
Missing MCP Telemetry (no gateway.jsonl or rpc-messages.jsonl)
None in the sampled MCP-enabled runs.
🔍 Telemetry Quality Analysis
Firewall Log Quality
Gateway Log Quality
Healthy Runs Summary
Recommended Actions
References:
Report generated automatically by the Daily Observability Report workflow
Analysis window: Last 7 days | Runs analyzed: 20
All reactions