[observability] Observability Coverage Report - 2026-01-23 #11534
Closed
Replies: 2 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
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
Unable to compute observability coverage for the last 7 days because the log download step failed for all workflows in this run. This blocks validation of firewall (Squid access.log) and MCP gateway (gateway.jsonl) coverage, so the health signal is currently unknown.
Immediate focus should be on restoring the log collection pipeline; until logs can be fetched, observability gaps (if any) cannot be confirmed or remediated.
Critical Information
agentic_workflows/logsreturned an error)📊 Full Observability Report
Coverage Summary
🔴 Critical Issues
agentic_workflows/statusalso failed, so workflow inventory could not be enumerated.Missing Firewall Logs (access.log)
No runs analyzed due to log collection failure.
Missing Gateway Logs (gateway.jsonl)
No runs analyzed due to log collection failure.
No warnings available; data collection failed.
✅ Healthy Runs
None verified; data collection failed.
📋 Detailed Run Analysis
Firewall-Enabled Runs
No data available.
MCP-Enabled Runs
No data available.
🔍 Telemetry Quality Analysis
Firewall Log Quality
No data available.
Gateway Log Quality
No data available.
📝 Recommendations
agentic_workflows/logsfunctionality so weekly runs can be analyzed.📊 Trends
No trend data available; collection failed.
References: §21293282518
Beta Was this translation helpful? Give feedback.
All reactions