[observability] Observability Coverage Report - 2026-01-21 #11057
Closed
Replies: 4 comments
-
|
This report has been superseded by a newer observability report. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
This report has been superseded by a newer observability report. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
This report has been superseded by a newer observability report. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
This report has been superseded by a newer observability report. |
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.
-
Overview
Log collection for the last 7 days did not complete. The GitHub CLI is not authenticated in this environment, and the agentic-workflows log download tool returned a failure, so no workflow run logs were available to analyze.
Because logs were unavailable, coverage metrics for AWF Firewall and MCP Gateway are reported as N/A. This report focuses on the data gap and the remediation steps needed to restore observability reporting.
Critical Issues
📊 Full Observability Report
Coverage Summary
🔴 Critical Issues
✅ Healthy Runs
📋 Detailed Run Analysis
Firewall-Enabled Runs
MCP-Enabled Runs
🔍 Telemetry Quality Analysis
Firewall Log Quality
Gateway Log Quality
📝 Recommendations
ghor fixagentic-workflowslog download failures).📊 Trends
Report generated automatically by the Daily Observability Report workflow
Analysis window: Last 7 days | Runs analyzed: 0
References:
Beta Was this translation helpful? Give feedback.
All reactions