[observability] Observability Coverage Report - 2026-07-19 #46495
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 #46689. |
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.
-
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. Firewall observability is not usable in the current sample: every firewall-enabled run was missing the Squid
access.logartifact, so we have 0% firewall log coverage and no way to inspect allowed vs. blocked egress.MCP telemetry is better but still incomplete. Two runs have valid
rpc-messages.jsonlfallback telemetry, while one MCP-enabled workflow has neithergateway.jsonlnorrpc-messages.jsonl, which is a critical gap. One of the telemetry-bearing runs also recorded a single RPC error response, but the log file itself is valid.Key Alerts and Anomalies
🔴 Critical Issues:
access.logmissing from all 5 sampled firewall-enabled runs, includingPR Sous Chef(#29660064261),Daily Project Performance Summary Generator (Using MCP Scripts)(#29660744841),Agentic Workflow Audit Agent(#29661572874),Daily Documentation Healer(#29666110853), andPR Sous Chef(#29666124378).Daily Project Performance Summary Generator (Using MCP Scripts)(#29660744841) has neithergateway.jsonlnorrpc-messages.jsonl, so its MCP execution is not observable.PR Sous Chef(#29666124378) has complete MCP telemetry viarpc-messages.jsonl, but one RPC response in the file is an error response.Coverage Summary
access.log)gateway.jsonlorrpc-messages.jsonl)📋 Detailed Run Analysis
Firewall-Enabled Runs
Missing Firewall Logs (
access.log)MCP-Enabled Runs
rpc-messages.jsonlrpc-messages.jsonlMissing MCP Telemetry (
gateway.jsonlandrpc-messages.jsonl)🔍 Telemetry Quality Analysis
access.logis missing in every firewall-enabled run.tools/callrequests, 1 error response, and 1 unique server (safeoutputs).gateway.jsonlwas absent in the telemetry-bearing runs, sorpc-messages.jsonlserved as the canonical fallback.Daily Documentation HealerandPR Sous Chefboth have usable MCP telemetry; firewall observability remains the blocking issue across the sample.Recommended Actions
access.logan always-uploaded artifact for firewall-enabled runs, and fail the run or emit a visible warning when it is absent.gateway.jsonlorrpc-messages.jsonlon every run so telemetry is preserved even when the workflow exits early.References
Report generated automatically by the Daily Observability Report workflow
Analysis window: Last 7 days | Runs analyzed: 5
Beta Was this translation helpful? Give feedback.
All reactions