[observability] Observability Coverage Report - 2026-04-25 #28525
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 #28645. |
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 the latest 50 agentic workflow runs returned by the completed
agenticworkflows logs --count 50 --start_date -7dcall. Coverage percentages below use the 46 completed runs as the denominator; 4 in-progress runs are noted separately because their final artifacts may not have been uploaded yet.Overall observability needs attention: firewall access logging coverage is 93%, and MCP telemetry coverage is 100%. Critical gaps are listed below with run links.
Key Alerts and Anomalies
🔴 Critical Issues:
access.logartifact was not found.access.logpresent but contains 0 parsed Squid entries.access.logpresent but contains 0 parsed Squid entries.in_progress, so final artifact coverage is not evaluated yet.in_progress, so final artifact coverage is not evaluated yet.in_progress, so final artifact coverage is not evaluated yet.in_progress, so final artifact coverage is not evaluated yet.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 Excluded From Coverage Denominators
🔍 Telemetry Quality Analysis
Firewall Log Quality
access.logentries analyzed: 167api.githubcopilot.com:443(74),(unknown)(46),api.anthropic.com:443(37),151.101.64.223:443(5),151.101.128.223:443(2)Gateway Log Quality
rpc-messages.jsonlcanonical fallback for completed MCP-enabled runs; preferredgateway.jsonlwas not observed in this sample.safeoutputs,githubAdditional Telemetry Artifacts
aw_info.jsonagent-stdio.logagent_output/agent_output.jsonHealthy Runs Summary
access.log: 14 of 15gateway.jsonlorrpc-messages.jsonl: 14 of 14Recommended Actions
mcp-logs/gateway.jsonlalongsiderpc-messages.jsonlso preferred structured gateway metrics are available without reconstructing JSON-RPC exchanges.📊 Historical Trends
Historical trend data was not available in the downloaded log cache. This report should be compared with prior
[observability]discussions for week-over-week movement.References:
Analysis window: Last 7 days | Runs analyzed: 50 | Completed runs evaluated: 46
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