You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I reviewed a capped sample of 20 workflow runs from the last 7 days. Coverage is complete for the one firewall-enabled run and the one MCP-enabled run in the sample, so there are no critical missing-log gaps.
The main issue is log quality, not absence: the firewall run has a usable access.log, but it only shows allowed traffic and proxy noise, with no blocked sample to validate denial-path observability. The MCP run has valid telemetry via the canonical fallback rpc-messages.jsonl and shows healthy JSON-RPC traffic.
Key Alerts and Anomalies
No critical issues detected.
🔴 Critical Issues:
None.
⚠️Warnings:
run-30724324732 (Daily Documentation Healer) has firewall telemetry, but access.log contains 179 lines with 90 allowed tunnels, 0 blocked requests, and 89 NONE_NONE:HIER_NONE noise entries. That is usable, but it does not exercise the blocked-request path.
Daily Documentation Healer had the only firewall-enabled and MCP-enabled run in the sample, and both telemetry sources were present.
The firewall log is the only coverage concern, because it lacks any blocked-request example.
Recommended Actions
Keep access.log collection enabled for every firewall-backed run, and ensure at least one blocked request is generated in test coverage so denial-path debugging is observable.
Prefer gateway.jsonl for MCP telemetry when available, but keep rpc-messages.jsonl as a valid fallback and ensure it remains written on every MCP-enabled run.
Add a lightweight quality check for firewall runs that flags logs containing only allowed traffic, so the blocked-path gap is visible before incidents.
📊 Historical Trends
No multi-day trend comparison was derived from this sample.
Report generated automatically by the Daily Observability Report workflow Analysis window: Last 7 days | Runs analyzed: 20
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Executive Summary
I reviewed a capped sample of 20 workflow runs from the last 7 days. Coverage is complete for the one firewall-enabled run and the one MCP-enabled run in the sample, so there are no critical missing-log gaps.
The main issue is log quality, not absence: the firewall run has a usable
access.log, but it only shows allowed traffic and proxy noise, with no blocked sample to validate denial-path observability. The MCP run has valid telemetry via the canonical fallbackrpc-messages.jsonland shows healthy JSON-RPC traffic.Key Alerts and Anomalies
No critical issues detected.
🔴 Critical Issues:
run-30724324732(Daily Documentation Healer) has firewall telemetry, butaccess.logcontains 179 lines with 90 allowed tunnels, 0 blocked requests, and 89NONE_NONE:HIER_NONEnoise entries. That is usable, but it does not exercise the blocked-request path.Coverage Summary
access.log)gateway.jsonlorrpc-messages.jsonl)📋 Detailed Run Analysis
Sample Run Status
Firewall-Enabled Runs
Missing Firewall Logs (
access.log)MCP-Enabled Runs
rpc-messages.jsonlMissing MCP Telemetry
🔍 Telemetry Quality Analysis
Firewall Log Quality
/tmp/gh-aw/aw-mcp/logs/run-30724324732/sandbox/firewall/logs/access.logaccess.loglines analyzed: 179api.anthropic.com:443,o205451.ingest.us.sentry.io:443,otlp-gateway-prod-eu-west-2.grafana.net:443Gateway Log Quality
rpc-messages.jsonlfallback/tmp/gh-aw/aw-mcp/logs/run-30724324732/mcp-logs/rpc-messages.jsonlsafeoutputsrpc-messages.jsonlHealthy Runs Summary
Daily Documentation Healerhad the only firewall-enabled and MCP-enabled run in the sample, and both telemetry sources were present.Recommended Actions
access.logcollection enabled for every firewall-backed run, and ensure at least one blocked request is generated in test coverage so denial-path debugging is observable.gateway.jsonlfor MCP telemetry when available, but keeprpc-messages.jsonlas a valid fallback and ensure it remains written on every MCP-enabled run.📊 Historical Trends
No multi-day trend comparison was derived from this sample.
Report generated automatically by the Daily Observability Report workflow
Analysis window: Last 7 days | Runs analyzed: 20
All reactions