[observability] Observability Coverage Report - 2026-04-09 #25551
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 #25723. |
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
Analyzed 31 workflow runs from the last 7 days. Firewall logging coverage is 67.7% (21/31) and MCP telemetry coverage is 100.0% (22/22).
The primary risk is firewall observability gaps: 10 firewall-enabled runs are missing
access.log, which is a critical debugging artifact. MCP telemetry is present for all MCP-enabled runs viarpc-messages.jsonlfallback, with no runs missing both telemetry files.MCP gateway JSONL was not present in this sample; coverage relies on
rpc-messages.jsonlfallback. Due run-directory permissions onmcp-logs/*, quality checks for MCP used artifact manifests andrun_summary.jsonmetadata rather than raw JSONL parsing.Key Alerts and Anomalies
🔴 Critical Issues:
access.log: Daily Observability Report for AWF Firewall and MCP Gateway §24218897398access.log: Daily Semgrep Scan §24218852202access.log: GitHub API Consumption Report Agent §24218508186access.log: Test Quality Sentinel §24216575962access.log: Design Decision Gate 🏗️ §24216575979access.log: Design Decision Gate 🏗️ §24216473072access.log: Test Quality Sentinel §24216473075access.log: Test Quality Sentinel §24216374758access.log: Design Decision Gate 🏗️ §24216374780access.log: Agentic Workflow Audit Agent §24213291173Coverage Summary
access.log)gateway.jsonlorrpc-messages.jsonl)Overall observability coverage across required artifacts: 81.1%
📋 Detailed Run Analysis
Firewall-Enabled Runs
Missing Firewall Logs (access.log)
MCP-Enabled Runs
Missing MCP Telemetry (no gateway.jsonl or rpc-messages.jsonl)
None.
🔍 Telemetry Quality Analysis
Firewall Log Quality
Gateway Log Quality
Healthy Runs Summary
Recommended Actions
firewall-audit-logs/logs/access.logfor all firewall-enabled runs, including failed/cancelled paths.access.logis missing, or when MCP is enabled but both telemetry files are missing.gateway.jsonlgeneration consistently (while keepingrpc-messages.jsonlfallback) and expose parseable latency/error metrics inrun_summary.json.📊 Historical Trends
References:
Beta Was this translation helpful? Give feedback.
All reactions