[observability] Observability Coverage Report - 2026-07-02 #42850
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 #43059. |
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
I sampled 5 recent workflow runs from the last 7 days. No firewall-enabled workflow runs were present in the downloaded sample, so AWF Firewall coverage is N/A for this report window. Two runs did expose MCP telemetry via
rpc-messages.jsonl, which is the accepted fallback whengateway.jsonlis absent, and both were healthy.Key Alerts and Anomalies
No critical issues detected in the sampled MCP runs. The only coverage gap is firewall visibility: no firewall-enabled runs were found in the sampled week, so there was no
access.logdata to validate.Coverage Summary
access.log)gateway.jsonlorrpc-messages.jsonl)Detailed Run Analysis
MCP-Enabled Runs
rpc-messages.jsonlrpc-messages.jsonlFirewall-Enabled Runs
No firewall-enabled workflow runs were found in the past 7 days.
Telemetry Quality
rpc-messages.jsonlwas present for both MCP-enabled runs and parsed cleanly.gateway.jsonlfiles were present in the sampled MCP runs, so the canonical fallback path was used.Recommended Actions
rpc-messages.jsonlas the fallback telemetry source for MCP runs untilgateway.jsonlis emitted consistently.access.logwithin the 7-day window.access.logas critical.References:
Report generated automatically by the Daily Observability Report workflow
Analysis window: Last 7 days | Runs sampled: 5
All reactions