[observability] Observability Coverage Report - 2026-04-26 #28645
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 #28821. |
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 99 downloaded workflow run summaries from the requested recent log window. The artifact cache covers runs from
2026-04-26T11:56:52Zthrough2026-04-26T23:45:07Z; the initial all-workflows download hit the MCP bridge HTTP timeout, but it left enough run manifests and parsed summaries to compute coverage for the downloaded runs.AWF firewall coverage is 90.9%: 90 of 99 firewall-enabled runs had
sandbox/firewall/logs/access.logor parsed firewall telemetry. MCP telemetry coverage is 100.0%: all 90 MCP-enabled runs hadmcp-logs/rpc-messages.jsonlin the artifact manifest. No MCP-enabled run was missing bothgateway.jsonlandrpc-messages.jsonl.Key Alerts and Anomalies
🔴 Critical Issues:
access.log: Documentation Noob Tester §24957487711 (failure, 2026-04-26)access.log: Smoke CI §24959911553 (cancelled, 2026-04-26)access.log: Smoke CI §24961104346 (cancelled, 2026-04-26)access.log: Smoke CI §24961125853 (cancelled, 2026-04-26)access.log: Smoke CI §24963334613 (cancelled, 2026-04-26)access.log: Smoke CI §24966690457 (cancelled, 2026-04-26)access.logcoverage but zero parsed requests, mostly Smoke CI runs with no observed network traffic.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
Telemetry Quality Analysis
Firewall Log Quality
access.logentries analyzed: 2258api.anthropic.com:443(907),github.com:443(530),api.githubcopilot.com:443(496),(unknown)(175),api.openai.com:443(35)(unknown)(175),ab.chatgpt.com:443(8),chatgpt.com:443(4),api.github.com:443(1),github.com:443(1)Gateway Log Quality
rpc-messages.jsonlcanonical fallback for all MCP-enabled runs; nogateway.jsonlartifacts were observed in this batch.a,e,f,i,l,m,n,n,o,s,t,yHealthy Runs Summary
Recommended Actions
sandbox/firewall/logs/access.log, especially failed or cancelled runs where network telemetry is most useful for postmortems.rpc-messages.jsonlas valid MCP telemetry, but consider fixing extracted artifact permissions so automated quality checks can parse every JSON-RPC file, not just the readable subset.Historical Trends
No historical comparison was computed in this run. The current downloaded cache provides a point-in-time baseline for future observability reports.
References:
Analysis window requested: last 7 days | Downloaded summaries analyzed: 99 | Artifact cache range: 2026-04-26T11:56:52Z to 2026-04-26T23:45:07Z
Warning
Firewall blocked 4 domains
The following domains were blocked by the firewall during workflow execution:
ab.chatgpt.comapi.github.comchatgpt.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