[observability] Observability Coverage Report - 2026-03-22 #22243
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 #22394. |
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 workflow logs from the last 7 days for
github/gh-awto assess observability coverage for AWF Firewall and MCP Gateway telemetry.A total of 398 runs were downloaded. Of these, 60 were active agent runs (
agent-stdio.logpresent) and used as the observability denominator. The remaining 338 runs were mostly skipped/non-agent runs and are treated as N/A for firewall/MCP telemetry checks.Key Alerts and Anomalies
🔴 Critical Issues:
rpc-messages.jsonlpresent but zero parsed MCP tool-call events (§23394595343).Coverage Summary
firewall_enabled_workflows)mcp_enabled_workflows)📋 Detailed Run Analysis
Firewall-Enabled Runs (status breakdown)
Missing Firewall Logs (access.log)
MCP-Enabled Runs (status breakdown)
Missing MCP Telemetry (no gateway.jsonl or rpc-messages.jsonl)
🔍 Telemetry Quality Analysis
Firewall Log Quality
api.githubcopilot.com:443(1098),api.anthropic.com:443(323),api.openai.com:443(142)Gateway Log Quality
gateway.jsonl0 runs,rpc-messages.jsonl60 runsRecommended Actions
📊 Historical Trends
Historical trend series was not computed in this run. Snapshot baselines:
Context
References:
Beta Was this translation helpful? Give feedback.
All reactions