[observability] Observability Coverage Report - 2026-08-15 #52989
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 #53243. |
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.
Executive Summary
I analyzed 19 representative workflow runs from the last 7 days, drawn from a 30-run repository-wide log fetch and capped at 2 runs per workflow. One failed run (
Design Decision Gate 🏗️§31915362579) never progressed into turn-bearing agent execution, so it is treated as observability N/A rather than a missing-log failure.Presence coverage is strong in the sampled runtime-bearing runs: firewall
access.logwas present in 18/18 firewall-enabled runs and MCP telemetry was present in 18/18 MCP-enabled runs. The main gaps are quality-related rather than presence-related: all sampled MCP telemetry came from therpc-messages.jsonlfallback rather thangateway.jsonl, and every sampled RPC log was missing the expectedtypefield from the audit rubric.Firewall logging also needs stronger blocked-path visibility.
access.logexisted for every sampled firewall-enabled run, but the 18 sampled firewall logs showed 1,877 entries with zeroTCP_DENIEDevents, so the logs demonstrate allowed traffic but do not confirm blocked-request observability in this capped sample. Common destinations wereapi.githubcopilot.com:443(316),api.anthropic.com:443(207),o205451.ingest.us.sentry.io:443(158),otlp-gateway-prod-eu-west-2.grafana.net:443(142),registry.npmjs.org:443(111).Key Alerts and Anomalies
No critical issues detected in the analyzed runtime-bearing sample.
Warning
Firewall log presence is healthy, but blocked-request visibility was absent in the 18 firewall-enabled runs included in this sample.
Warning
MCP telemetry presence is healthy, but all 18 MCP-enabled runs relied on
rpc-messages.jsonlfallback logs, and every sampled RPC log omitted the expectedtypefield.Coverage Summary
access.log)gateway.jsonlorrpc-messages.jsonl)📋 Detailed Run Analysis
Firewall-Enabled Runs
Missing Firewall Logs (
access.log)None in the analyzed sample.
MCP-Enabled Runs
Missing MCP Telemetry (no
gateway.jsonlorrpc-messages.jsonl)None in the analyzed sample.
Runs Classified as N/A
🔍 Telemetry Quality Analysis
Firewall Log Quality
access.logentries analyzed: 1877api.githubcopilot.com:443(316),api.anthropic.com:443(207),o205451.ingest.us.sentry.io:443(158),otlp-gateway-prod-eu-west-2.grafana.net:443(142),registry.npmjs.org:443(111)TCP_TUNNEL:HIER_DIRECTandNONE_NONE:HIER_NONE error:transaction-end-before-headersdecisions.Gateway Log Quality
rpc-messages.jsonl(18)safeoutputs(18),github(4),agenticworkflows(2)gateway.jsonlfiles were present and the RPC records did not provide a directly pairable duration field for this audit.rpc-messages.jsonlfile was valid JSONL, but each sample omitted the expected top-leveltypefield from the audit rubric.Healthy Runs Summary
access.logand MCP telemetry.Recommended Actions
gateway.jsonlin addition to the raw fallback RPC log so response-time and status metrics are directly available without inference.rpc-messages.jsonlto include the expected top-leveltypefield, or update the rubric and downstream parsers ifeventis now the canonical replacement.TCP_DENIEDobservability.📊 Historical Trends
Historical trend data was not computed in this run. This report is a point-in-time audit over the last 7 days using a representative 19-run capped sample.
References: §31915362579, §31915364795, §31915363728
Analysis window: Last 7 days | Runs analyzed: 19
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
raw.githubusercontent.comTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.
All reactions