06-tracing

What problem does it solve?

Edgion developers need a fast, reliable way to identify which layer (config sync, controller processing, gateway runtime, routing/plugins, TLS, or statistics) is failing after a code change causes unexpected behavior.

Core Features & Use Cases

• Layered troubleshooting flow: Diagnose issues by following the configuration/sync chain, then routing/plugin runtime, then load-balancing/statistical behavior.
• Three-view localization with Admin APIs: Use controller center/server/client views to narrow down whether validation, parse/requeue, gRPC sync, watch/list flow, or gateway readiness is at fault.
• Evidence-driven inspection: Validate behavior using Gateway Admin API endpoints, Access Log Store trace capture, store-stats, and Prometheus-style metrics.
• Fast local iteration and environment control: Use integration test harness options (keep-alive, skip prepare, or manual start) to preserve the scene and reproduce issues quickly.

Quick Start

Run the integration scene with keep-alive for a single failing case, then inspect controller and gateway readiness using the health and ready endpoints to identify the failing layer.