[observability] Observability Coverage Report - 2026-06-18 #39928
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 #40172. |
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
This week’s 20-run sample is mostly healthy, but not clean. Every analyzed run was firewall-enabled,
access.logwas retained on 16/20 runs, and MCP telemetry was retained on 17/20 runs. The MCP side is relying entirely onrpc-messages.jsonl; nogateway.jsonlfiles were observed in this sample.The main issue is missing firewall telemetry on four runs, including one completed workflow and three in-progress workflows. The three in-progress runs are also missing MCP telemetry, so they are not debuggable from the downloaded artifacts alone.
Key Alerts and Anomalies
🔴 Critical Issues:
run-27726899573(Changeset Generator) is missingaccess.log.run-27727716397(Daily Documentation Healer) is missingaccess.logand MCP telemetry.run-27727741467(Semantic Function Refactoring) is missingaccess.logand MCP telemetry.run-27727766724(Daily Observability Report for AWF Firewall and MCP Gateway) is missingaccess.logand MCP telemetry.error:transaction-end-before-headers, so the proxy trace is present but noisy.rpc-messages.jsonlonly.Coverage Summary
access.log)gateway.jsonlorrpc-messages.jsonl)📋 Detailed Run Analysis
Run Summary
rpc-messages.jsonl)rpc-messages.jsonl)rpc-messages.jsonl)rpc-messages.jsonl)rpc-messages.jsonl)rpc-messages.jsonl)rpc-messages.jsonl)rpc-messages.jsonl)rpc-messages.jsonl)rpc-messages.jsonl)rpc-messages.jsonl)rpc-messages.jsonl)rpc-messages.jsonl)rpc-messages.jsonl)rpc-messages.jsonl)rpc-messages.jsonl)rpc-messages.jsonl)Missing Firewall Logs (
access.log)Missing MCP Telemetry
🔍 Telemetry Quality Analysis
Firewall Log Quality
access.logentries analyzed: 1,816api.anthropic.com,api.githubcopilot.com,gh-aw-foundry.openai.azure.com,github.githubassets.com,generativelanguage.googleapis.comwww.google.com,content-autofill.googleapis.com,localhost:8080,accounts.google.comMCP Gateway Log Quality
rpc-messages.jsonl(canonical fallback)sentry,safeoutputs,serena,mcpscripts,tavily,agenticworkflowsHealthy Runs Summary
Recommended Actions
sandbox/firewall/logs/access.logfor every firewall-enabled run, including in-progress daily jobs, so the proxy trace survives long enough for debugging.rpc-messages.jsonlas the minimum MCP fallback, but restoregateway.jsonlwhere possible to recover per-call timing and error attribution.transaction-end-before-headersnoise in summaries so small firewall logs stay readable when a real deny event appears.References:
Report generated automatically by the Daily Observability Report workflow
Analysis window: Last 7 days | Runs analyzed: 20
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