[observability] Observability Coverage Report - 2026-05-07 #30712
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 #30912. |
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 170 downloaded workflow runs for observability coverage. The requested window was the last 7 days; the MCP log fetch completed for parsed artifacts from 2026-05-06 13:46 UTC through 2026-05-06 23:59 UTC. A 100-run all-workflows fetch timed out after partial artifact download, then a 75-run fetch completed and supplied the dataset used here.
AWF Firewall coverage is 91.5%: 75 of 82 firewall-enabled runs had
access.logartifacts. MCP Gateway telemetry coverage is 100.0%: all 75 MCP-enabled runs hadrpc-messages.jsonl; nogateway.jsonlfiles were present in this sample, so the canonical JSON-RPC fallback was used throughout.Key Alerts and Anomalies
🔴 Critical Issues:
access.log: Super Linter Report §25442628138 (failure, 2026-05-06T14:48:03Z)access.log: Go Pattern Detector §25444290134 (success, 2026-05-06T15:18:20Z)access.log: Smoke CI §25444553809 (cancelled, 2026-05-06T15:23:14Z)access.log: Documentation Unbloat §25449195821 (failure, 2026-05-06T16:56:23Z)rpc-messages.jsonl)rpc-messages.jsonl)rpc-messages.jsonl)rpc-messages.jsonl)rpc-messages.jsonl)rpc-messages.jsonl)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.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.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.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.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlMissing MCP Telemetry (no
gateway.jsonlorrpc-messages.jsonl)No MCP-enabled runs were missing both telemetry files.
Telemetry Quality Analysis
Firewall Log Quality
access.logentries analyzed: 18936Gateway Log Quality
rpc-messages.jsonlcanonical fallback for all MCP-enabled runs in this sample;gateway.jsonlwas not present.Healthy Runs Summary
157 of 170 analyzed runs had complete required observability for the components they used.
Recommended Actions
access.log, prioritizing failed runs because network telemetry is most useful there.rpc-messages.jsonlas valid MCP telemetry; no MCP-enabled run in this sample lacked both gateway and JSON-RPC logs.gateway.jsonlartifact where possible so duration and status metrics are available without JSON-RPC pairing.Historical Trends
No previous trend dataset was available in the downloaded artifacts. This report can serve as the baseline for future daily comparisons.
References:
Analysis window: Last 7 days requested | Parsed artifact window: 2026-05-06 13:46 UTC to 2026-05-06 23:59 UTC | Runs analyzed: 170
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