[observability] Observability Coverage Report - 2026-02-20 #17108
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-02-21T07:56:04.192Z.
|
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
Over the last 7 days, the log download step returned 10 workflow runs (partial window due to MCP logs tool timeout/limit). Within that sample, 6 runs had
firewall_enabled: trueand only 3 exposedsandbox/firewall/logs/access.login artifacts, leaving 3 firewall-enabled runs without the critical access log artifact.For MCP observability, 4 runs produced MCP artifacts (
mcp-logs/*), but none exposedgateway.jsonl(onlymcp-logs/rpc-messages.jsonlandmcp-logs/mcp-gateway.log). This means MCP telemetry exists, but not in the expectedgateway.jsonlformat required by the report criteria.Key Alerts and Anomalies
🔴 Critical Issues:
access.logartifacts for 3 firewall-enabled runs (allIssue Monster).gateway.jsonlfor all 4 MCP-enabled runs (onlyrpc-messages.jsonlpresent).Daily Observability Report for AWF Firewall and MCP Gateway,Issue Monster).sandbox/andmcp-logs/directories are permission-restricted in this environment, so content quality checks are based onrun_summary.jsonartifact lists rather than direct file reads.Coverage Summary
Note: MCP-enabled runs do include
mcp-logs/rpc-messages.jsonlandmcp-logs/mcp-gateway.log, but not the requiredgateway.jsonlartifact.📋 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
api.anthropic.com:443,api.githubcopilot.com:443-) in this datasetGateway Log Quality
gateway.jsonlnot present in any MCP-enabled run artifactsmcp-logs/rpc-messages.jsonl,mcp-logs/mcp-gateway.log) exist but were not parsed for structured metrics due to format mismatch with expectedgateway.jsonlHealthy Runs Summary
Workflow Health Manager - Meta-Orchestrator,Go Fan,Auto-Triage Issuesgateway.jsonl:Workflow Health Manager - Meta-Orchestrator,Go Fan,Auto-Triage Issues,Static Analysis ReportRecommended Actions
Issue Monsterruns withfirewall_enabled: truealways uploadsandbox/firewall/logs/access.log.gateway.jsonl(or update the report criteria ifrpc-messages.jsonlis the new canonical source).countor pagination once the MCP logs tool timeout is resolved to cover the full 7-day window.📊 Historical Trends
Report generated automatically by the Daily Observability Report workflow
Analysis window: Last 7 days | Runs analyzed: 10 (partial due to logs tool timeout/limit)
References: §22215346914 §22215120324 §22214019366
Beta Was this translation helpful? Give feedback.
All reactions