[observability] Observability Coverage Report - 2026-08-09 #51654
Closed
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-08-11T00:01:14.670Z.
|
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
A 30-run repository-wide fetch from the last 7 days produced an 18-run analysis set after enforcing the breadth cap and per-workflow limits. Within that sample, 15 runs showed firewall activity and 2 runs showed MCP session activity, but none of those runs contained the canonical raw observability files required for reliable post-incident debugging.
Recursive discovery under each selected
run-<id>/folder found noaccess.logfiles, nogateway.jsonlfiles, and norpc-messages.jsonlfiles. Some runs still exposed derived summaries insummary.jsonandrun_summary.jsonwith firewall request counts and limited session counts, but those summaries are not a replacement for the raw artifacts needed to trace blocked egress decisions or individual MCP tool calls.The most important operational consequence is simple: when a firewall-enabled run fails on network behavior, or when an MCP-enabled run fails inside tool orchestration, the downloaded artifacts currently do not preserve the raw evidence needed for root-cause analysis. This is a repo-wide observability gap, not an isolated workflow regression.
Key Alerts and Anomalies
🔴 Critical Issues:
access.log.access.log.access.log.access.log.access.log.access.log.access.logcondition.gateway.jsonlnorrpc-messages.jsonlwas present.gateway.jsonlnorrpc-messages.jsonlwas present.aw_info.jsonwas absent from all 18 analyzed run folders, so firewall and MCP configuration could not be confirmed from the canonical metadata file.safe_output.jsonlwas absent from all 18 analyzed run folders; only high-level safe-output summaries were available when present.Coverage Summary
access.log)gateway.jsonlorrpc-messages.jsonl)📋 Detailed Run Analysis
Firewall-Enabled Runs
Missing Firewall Logs (
access.log)MCP-Enabled Runs
Missing MCP Telemetry (no
gateway.jsonlorrpc-messages.jsonl)🔍 Telemetry Quality Analysis
Firewall Log Quality
access.logentries analyzed: 0 raw entries across 0 filesGateway Log Quality
gateway.jsonlorrpc-messages.jsonlAdditional Telemetry Artifacts
summary.json/run_summary.json: present in all 18 analyzed runsagent-stdio.log: present in 15/18 analyzed runsaw_info.json: present in 0/18 analyzed runssafe_output.jsonl: present in 0/18 analyzed runsHealthy Runs Summary
No analyzed run had complete raw observability coverage for the required firewall or MCP log artifacts.
Recommended Actions
access.logartifacts for every firewall-enabled run, including workflow-call layouts, and validate the path in CI with a post-run assertion.gateway.jsonlpreferred,rpc-messages.jsonlacceptable fallback) for every run with MCP session activity, and fail the workflow when both files are absent.aw_info.jsonandsafe_output.jsonlin the downloaded artifacts so configuration and actuation can be audited without reconstructing behavior from summaries.📊 Historical Trends
No prior retained observability baseline was available in the downloaded artifacts, so this report only establishes the current daily snapshot.
Report generated automatically by the Daily Observability Report workflow
Analysis window: Last 7 days | Runs analyzed: 18
All reactions