[observability] Observability Coverage Report - 2026-06-02 #36374
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-06-03T00:15:18.276Z.
|
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 20 workflow runs from the last 7 days. Firewall observability is the weak point: 3 firewall-enabled runs are missing
access.log, and those same runs also have no MCP telemetry. Within the analyzed set, that leaves firewall coverage at 12/15 (80.0%).MCP telemetry is mostly healthy. There was no
gateway.jsonlin this sample; every usable MCP trace came fromrpc-messages.jsonl. Of the 17 MCP-enabled runs in the sample, 15 had valid JSONL telemetry and 2 emitted empty placeholder files, so MCP coverage is 15/17 (88.2%) with two warning-level quality issues.Key Alerts and Anomalies
Critical Issues
Semantic Function Refactoring§26789796284Daily Documentation Healer§26789746422Smoke Claude§26789674010All three are firewall-enabled runs with neither
sandbox/firewall/logs/access.lognor MCP telemetry.Warnings
Smoke Pi§26789674018 has an emptyrpc-messages.jsonlplaceholder.Smoke Pi§26788943094 has an emptyrpc-messages.jsonlplaceholder.Coverage Summary
access.log)gateway.jsonlorrpc-messages.jsonl)📋 Detailed Run Analysis
Firewall-Enabled Runs
Missing Firewall Logs (
access.log)MCP-Enabled Runs
rpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonl🔍 Telemetry Quality Analysis
Firewall Log Quality
access.logentries analyzed: 1,612api.githubcopilot.com:443,o205451.ingest.us.sentry.io:443,api.anthropic.com:443,api.openai.com:443,github.githubassets.com:443MCP Log Quality
rpc-messages.jsonl(canonical fallback)safeoutputs,github,serena,tavily,agenticworkflows,mcpscriptsHealthy Runs Summary
Smoke Piruns with empty RPC placeholders should be treated as warning-level quality gaps, not critical telemetry loss.Recommended Actions
sandbox/firewall/logs/access.logemission for firewall-enabled runs so egress debugging does not depend on best-effort artifacts.rpc-messages.jsonlplaceholders with populated RPC logs, or suppress the placeholder file when MCP is unused.gateway.jsonlif you want structured per-call duration metrics; the current fallback is usable, but it limits latency analysis.References:
Warning
Firewall blocked 2 domains
The following domains were blocked by the firewall during workflow execution:
api.github.comgithub.com💡 Tip:
api.github.comis blocked because GitHub API access uses the built-in GitHub tools by default. Instead of addingapi.github.comtonetwork.allowed, usetools.github.mode: gh-proxyfor direct pre-authenticated GitHub CLI access without requiring network access toapi.github.com:See GitHub Tools for more information on
gh-proxymode.To allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.
Beta Was this translation helpful? Give feedback.
All reactions