[observability] Observability Coverage Report - 2026-05-11 #31391
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 #31606. |
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 19 workflow runs downloaded through the agentic-workflows log service for the last 7 days. Fifteen runs were completed and scored for observability coverage; four runs were still in progress and are listed separately so incomplete artifact uploads are not misclassified as missing telemetry.
Completed firewall-enabled runs have full
access.logcoverage: 13 of 13 have Squid access logs. Completed MCP runs also have telemetry coverage: 15 of 15 includerpc-messages.jsonl, the canonical fallback telemetry file. No completed run is missing bothgateway.jsonlandrpc-messages.jsonl.Key Alerts and Anomalies
No critical issues detected.
🔴 Critical Issues:
access.log.gateway.jsonlandrpc-messages.jsonl.Smoke Pi) includesrpc-messages.jsonl, but the file was empty in the downloaded artifacts.rpc-messages.jsonl; nogateway.jsonlfiles were present. This is acceptable fallback coverage, but preferred structured gateway telemetry was not observed.in_progress; their artifact sets may be incomplete and were not scored for missing-log coverage.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 (no
gateway.jsonlorrpc-messages.jsonl)In-Progress Runs Not Scored
🔍 Telemetry Quality Analysis
Firewall Log Quality
access.logentries analyzed: 2,727api.githubcopilot.com:443,api.anthropic.com:443,api.openai.com:443,github.githubassets.com:443,content-autofill.googleapis.com:443Smoke Claude(27),Smoke Copilot(35)Gateway Log Quality
rpc-messages.jsonlcanonical fallbackgateway.jsonlfiles observed: 0agenticworkflows,github,mcpscripts,safeoutputs,serena,tavilytools/callrequests: 93rpc-messages.jsonl; duration metrics require gateway telemetry or reliable request/response timestamp pairing.Healthy Runs Summary
All 13 completed firewall-enabled runs had access logs with entries. All 15 completed runs with MCP telemetry had at least one canonical telemetry artifact, and 14 of 15 had non-empty JSON-RPC message logs.
Recommended Actions
rpc-messages.jsonlfallback in the health criteria; it prevented false critical alerts whengateway.jsonlwas absent.Smoke Piuploaded an emptyrpc-messages.jsonldespite the file being present.gateway.jsonlwhen the gateway supports it, preserving richer duration and status metrics.📊 Historical Trends
No prior trend dataset was available in the downloaded artifacts for this run. This report records the current baseline as 100% completed-run firewall coverage and 100% completed-run MCP telemetry coverage, with one MCP quality warning for an empty fallback log.
References: §25643399750, §25641551127, §25641551150
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