[observability] Observability Coverage Report - 2026-02-22 #17673
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-02-23T07:50:06.254Z.
|
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
Across the last 7 days, 25 workflow runs were analyzed (2026-02-22 window). AWF Firewall coverage is partial, while MCP Gateway coverage is missing the expected
gateway.jsonlartifact across all MCP-enabled runs. This leaves a major observability blind spot for MCP tool execution traces.Firewall telemetry is present in 13 of 20 firewall-enabled runs (65%). The remaining 7 runs (mostly Issue Monster plus PR Triage Agent) have no
access.logartifact, which is critical for diagnosing egress issues. MCP telemetry shows 14 MCP-enabled runs but 0 runs withgateway.jsonlpresent, which is a critical gap.Key Alerts and Anomalies
🔴 Critical Issues:
gateway.jsonlin all 14 MCP-enabled runs.access.login 7 firewall-enabled runs.mcp-logs/rpc-messages.jsonlandmcp-logs/mcp-gateway.log, but the canonicalgateway.jsonlartifact is absent, preventing standardized metrics extraction.Coverage Summary
access.log)gateway.jsonl)📋 Detailed Run Analysis
Firewall-Enabled Runs
Missing Firewall Logs (access.log)
MCP-Enabled Runs
Missing Gateway Logs (gateway.jsonl)
🔍 Telemetry Quality Analysis
Firewall Log Quality
-(redacted/unknown) in the firewall summaryGateway Log Quality
gateway.jsonlwas not present in any MCP-enabled runmcp-logs/rpc-messages.jsonlandmcp-logs/mcp-gateway.log, but the canonical JSONL stream required by the report is missingHealthy Runs Summary
access.logartifactsgateway.jsonlartifactsRecommended Actions
gateway.jsonlfor every MCP-enabled run (or update the report pipeline ifrpc-messages.jsonlis the intended canonical log).sandbox/firewall/logs/access.logdespite firewall being enabled.📊 Historical Trends
No historical baseline available in this run’s artifacts; recommend persisting daily coverage metrics to enable week-over-week comparisons.
Report generated automatically by the Daily Observability Report workflow
Analysis window: 2026-02-15 to 2026-02-22 | Runs analyzed: 25
References:
Beta Was this translation helpful? Give feedback.
All reactions