[observability] Observability Coverage Report - 2026-07-22 #47162
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 #47432. |
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.
Caution
agentic threat detected
Threat detection flagged this output in warn mode. Manual review is REQUIRED before any follow-up automation.
Details
The threat detection engine failed to produce results.
Review the workflow run logs for details.
Executive Summary
Recent sampled runs do not expose the telemetry blocks needed for debugging firewall and MCP issues. The dedicated firewall test run failed, and the MCP-heavy successful runs did not surface usable firewall or gateway telemetry in their cached summaries. Debugging coverage is therefore incomplete.
Key Alerts and Anomalies
CRITICAL:
Firewall Test Agentrun29259440955failed, and the audit summary did not surfaceaccess_analysisorfirewall_analysis.Copilot Agent PR Analysisrun29858113306,Smoke Copilotrun29812420778, andMCP Inspector Agentrun29276873376did not surface MCP telemetry blocks in their cached summaries, so no gateway or rpc-message evidence was available for root-cause work.WARNING:
Coverage Summary
Detailed Run Analysis
Firewall-Enabled Runs
2925944095529858113306MCP-Enabled Runs
298581133062981242077829276873376Telemetry Quality Analysis
Recommended Actions
access.loginto the downloadable audit artifacts and fail the run when it is absent.mcp-logs/gateway.jsonlormcp-logs/rpc-messages.jsonlin the audit cache.References
Report generated automatically by the Daily Observability Report workflow
Analysis window: Last 7 days | Runs analyzed: 4
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
proxy.golang.orgSee Network Configuration for more information.
All reactions