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

[github-actions[bot]]

Executive Summary

I analyzed 4 representative runs from the last 7 days. The sampled firewall-enabled run has access.log in the expected layout and the sampled MCP-enabled runs all have telemetry, but the firewall log never observed a blocked request. That means coverage is present, yet firewall debugging completeness is only partial because TCP_DENIED behavior was not exercised in this sample.

MCP observability is healthy across the sample. All 4 MCP-enabled runs produced valid rpc-messages.jsonl telemetry, no parse errors, and no response failures. I did not find any run in the sample that lacked both gateway.jsonl and rpc-messages.jsonl.

Key Alerts and Anomalies

No critical issues detected.

🔴 Critical Issues:

• None.

⚠️ Warnings:

• Run 30961783636 has a populated firewall access.log, but no TCP_DENIED entries were observed, so blocked-egress debugging coverage is unverified in this sample.

Coverage Summary

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

📋 Detailed Run Analysis

Firewall-Enabled Runs

Workflow	Run ID	access.log	Entries	Allowed	Blocked	Status
Daily Documentation Healer	30961783636	✅	222	115	0	⚠️

Missing Firewall Logs (access.log)

None in the analyzed sample.

MCP-Enabled Runs

Workflow	Run ID	Telemetry Source	Entries	Servers	Tool Calls	Errors	Status
Daily Documentation Healer	30961783636	rpc-messages.jsonl	4	1	1	0	⚠️
Avenger	30954035224	rpc-messages.jsonl	4	1	1	0	✅
Avenger	30957584550	rpc-messages.jsonl	4	1	1	0	✅
Release	30960349548	rpc-messages.jsonl	8	2	1	0	✅

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

None in the analyzed sample.

🔍 Telemetry Quality Analysis

Firewall Log Quality

• Total access.log entries analyzed: 222
• Unique real domains: 3
• Blocked requests: 0 (0%)
• Top domains: api.anthropic.com:443, otlp-gateway-prod-eu-west-2.grafana.net:443, o205451.ingest.us.sentry.io:443
• The log format matched the expected AWF proxy shape, and the file was present at the canonical firewall path.

Gateway Log Quality

• Telemetry source: rpc-messages.jsonl (canonical fallback in all sampled MCP runs)
• Total entries analyzed: 20
• MCP servers used: safeoutputs, github
• Total tool calls: 4
• Error rate: 0%
• Average response time: N/A from rpc-messages.jsonl alone

Healthy Runs Summary

• 30954035224 Avenger: MCP telemetry present, no errors.
• 30957584550 Avenger: MCP telemetry present, no errors.
• 30960349548 Release: MCP telemetry present, no errors.

Recommended Actions

1. Add or exercise a blocked-egress path in a daily run so TCP_DENIED entries are captured alongside allowed traffic.
2. Keep emitting rpc-messages.jsonl until gateway.jsonl is consistently available for MCP runs.
3. Preserve this level of telemetry on future workflow templates so failed runs still have usable debugging signals.

📊 Historical Trends

Not enough recent history was analyzed in this capped sample to establish a trend line.

---

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

Generated by 📊 Daily Observability Report for AWF Firewall and MCP Gateway · gpt54 · 18.4 AIC · ⌖ 14 AIC · ⊞ 13.8K · ◷

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

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-08-06T00:10:00.600Z.

Closed by Workflow