[observability] Observability Coverage Report - 2026-08-01

[github-actions[bot]]

Executive Summary

I analyzed 30 workflow runs from the last 7 days and found 3 unique runs with the observability surfaces relevant to this report. Firewall coverage is complete for the one firewall-enabled run, and MCP telemetry is present for all MCP-enabled runs through the canonical rpc-messages.jsonl fallback.

The main gap is log quality rather than missing telemetry: the MCP fallback files are valid JSONL, but they do not include the preferred type field from the report schema. That makes the traces usable for debugging, but weaker than the preferred gateway.jsonl format.

Key Alerts and Anomalies

No critical issues detected.

🔴 Critical Issues:

• None.

⚠️ Warnings:

• run-30669467598, run-30673324195, and run-30674309618 use mcp-logs/rpc-messages.jsonl as the telemetry source. That fallback is acceptable, but each file is missing the type field expected by the preferred schema.
• run-30674309618 is still in_progress, so the firewall trace may still be incomplete.

Coverage Summary

Component	Runs Analyzed	Logs Present	Coverage	Status
AWF Firewall (access.log)	1	1	100%	✅
MCP Gateway (gateway.jsonl or rpc-messages.jsonl)	3	3	100%	⚠️

📋 Detailed Run Analysis

Firewall-Enabled Runs

Workflow	Run ID	access.log	Entries	Allowed	Blocked	Status
Daily Documentation Healer	30674309618	✅	217	95	122	✅

Missing Firewall Logs (access.log)

Workflow	Run ID	Date	Link
None	-	-	-

MCP-Enabled Runs

Workflow	Run ID	Telemetry Source	Entries	Servers	Tool Calls	Errors	Status
AI Moderator	30669467598	rpc-messages.jsonl	4	1	1	0	⚠️
AI Moderator	30673324195	rpc-messages.jsonl	4	1	1	0	⚠️
Daily Documentation Healer	30674309618	rpc-messages.jsonl	4	1	1	0	⚠️

Missing MCP Telemetry (gateway.jsonl or rpc-messages.jsonl)

Workflow	Run ID	Date	Link
None	-	-	-

🔍 Telemetry Quality Analysis

Firewall Log Quality

• Total access.log entries analyzed: 217
• Unique external domains: 1
• Allowed requests: 95
• Blocked/failed requests: 122
• Most visible destination: api.anthropic.com

Gateway Log Quality

• Telemetry source: rpc-messages.jsonl fallback
• Total entries analyzed: 12
• MCP servers used: safeoutputs
• Total tool calls: 3
• Error rate: 0%
• Average response time: N/A from rpc-messages.jsonl

Healthy Runs Summary

• run-30674309618 has complete firewall and MCP telemetry, with the MCP side using the fallback JSON-RPC trace.
• Both AI Moderator runs have complete MCP telemetry and no response errors.

Recommended Actions

1. Prefer gateway.jsonl where possible so MCP traces include the richer per-event schema and duration data.
2. Keep exporting rpc-messages.jsonl as a fallback, since it preserves usable MCP telemetry when the gateway log is absent.
3. Keep firewall traces enabled and retained; the current access.log is detailed enough to separate allowed traffic from failed/blocked transactions.

📊 Historical Trends

No historical trend series was computed from this one-day sample.

---

Report generated automatically by the Daily Observability Report workflow
Analysis window: Last 7 days | Runs analyzed: 3 unique runs

References:

• §30674309618
• §30673324195
• §30669467598

Generated by 📊 Daily Observability Report for AWF Firewall and MCP Gateway · gpt54 · 14.9 AIC · ⌖ 4 AIC · ⊞ 13.6K · ◷

• expires on Aug 1, 2026, 4:10 PM UTC-08:00

[github-actions[bot]]

This discussion has been marked as outdated by Daily Observability Report for AWF Firewall and MCP Gateway.

A newer discussion is available at Discussion #49681.