Understanding OpenTelemetry Support in kgateway
Blog post from Dash0
kgateway is a Kubernetes Gateway API implementation that utilizes Envoy to manage traffic at the edge of a cluster, making it an essential component for observability in cloud-native architectures. It supports OpenTelemetry for tracing and logging natively via OTLP/gRPC, allowing for seamless integration with observability pipelines, but retains a Prometheus-first approach for metrics collection. This mixed delivery model highlights the complexity of achieving multi-signal observability, where traces and logs are push-based and metrics remain pull-based. By applying a proposed OpenTelemetry Support Maturity Model, which is not an official standard but a community-driven framework, the strengths and gaps in kgateway's OpenTelemetry integration become apparent. The model evaluates dimensions such as integration surface, semantic conventions, and resource identity, aiming to provide a nuanced understanding of where the project excels and where it needs improvement. While kgateway demonstrates robust tracing and logging capabilities, its reliance on Prometheus for metrics and the need for downstream enrichment for resource attributes indicate areas for further development. The analysis underscores the evolving nature of OpenTelemetry support in gateway architectures and suggests that a dimensional maturity model can offer valuable insights into integration challenges and opportunities.