[observability] Observability Coverage Report - 2026-05-04 #30033
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 #30235. |
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 75 workflow run summaries downloaded for the last 7 days. Coverage metrics below use the 72 completed runs as the denominator; 3 in-progress runs were captured before final artifacts were uploaded and are listed as partial data.
Completed runs have strong MCP telemetry coverage through the canonical
rpc-messages.jsonlfallback. Firewall coverage is nearly complete, with one failed completed run missing the Squidaccess.logartifact needed for network debugging.Key Alerts and Anomalies
🔴 Critical Issues:
Coverage Summary
firewall_enabled_workflows)mcp_enabled_workflows)observability_coverage_percentage)📋 Detailed Run Analysis
Firewall-Enabled Runs
Missing Firewall Logs (access.log)
MCP-Enabled Runs
Missing MCP Telemetry (no gateway.jsonl or rpc-messages.jsonl)
Partial In-Progress Runs
🔍 Telemetry Quality Analysis
Firewall Log Quality
Gateway Log Quality
Additional Artifacts
Healthy Runs Summary
Recommended Actions
access.logartifact, since that prevents network-level debugging for the failure.gateway.jsonlalongsiderpc-messages.jsonlwhere possible so response-time and status metrics are available without relying on summarized fallback data.📊 Historical Trends
No historical trend store was available in the downloaded artifact set. This report records the current 7-day snapshot for comparison by future daily runs.
References: §25294543771, §25289990921, §25294350506
Analysis window: Last 7 days | Runs analyzed: 75 (completed coverage denominator: 72)
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