[observability] Observability Coverage Report - 2026-05-31 #36021
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 #36157. |
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
I sampled 6 completed runs from the last 7 days and excluded 6 runs that were still in progress when the bundle was fetched. The completed firewall-enabled runs all had
access.logartifacts, and the completed MCP-enabled runs all had RPC telemetry present.One run,
Smoke Pi(26698359911), produced a zero-byterpc-messages.jsonl, so the telemetry file exists but is not usable for debugging. The rest of the completed sample had readable firewall and RPC logs.Key Alerts and Anomalies
🔴 Critical Issues:
26698359911(Smoke Pi) has an emptymcp-logs/rpc-messages.jsonl.Coverage Summary
access.log)gateway.jsonlorrpc-messages.jsonl)📋 Detailed Run Analysis
Firewall-Enabled Runs
Missing Firewall Logs (access.log)
None in the completed sample.
MCP-Enabled Runs
Missing MCP Telemetry (no gateway.jsonl or rpc-messages.jsonl)
None in the completed sample.
🔍 Telemetry Quality Analysis
Firewall Log Quality
access.logentries analyzed: 354200, 20403, 16400, 1720api.githubcopilot.com:443,o205451.ingest.us.sentry.io:443,generativelanguage.googleapis.com:443,api.openai.com:443,github.com:443Gateway Log Quality
rpc-messages.jsonl(canonical fallback)Healthy Runs Summary
26698359917Changeset Generator26698359939Agent Container Smoke Test26698294921Issue Monster26698359936Smoke Antigravity26698359916Smoke GeminiRecommended Actions
rpc-messages.jsonlis present but empty.access.logand RPC artifacts for completed runs; the current sample is sufficient for debugging.References
Report generated automatically by the Daily Observability Report workflow
Analysis window: Last 7 days | Runs analyzed: 6 completed, 6 in progress excluded
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