Tracing with OpenTelemetry

Author: kamilkisiela

.changeset/tracing-with-opentelemetry.md

@@ -0,0 +1,18 @@
+---
+internal: minor
+router: minor
+config: minor
+executor: minor
+query-planner: minor
+---
+
+# Tracing with OpenTelemetry
+
+Introducing comprehensive OpenTelemetry-based tracing to the Hive Router, providing deep visibility into the GraphQL request lifecycle and subgraph communications.
+
+- **OpenTelemetry Integration**: Support for OTLP exporters (gRPC and HTTP) and standard propagation formats (Trace Context, Baggage, Jaeger, B3/Zipkin).
+- **GraphQL-Specific Spans**: Detailed spans for every phase of the GraphQL lifecycle
+- **Hive Console Tracing**: Native integration with Hive Console for trace visualization and analysis.
+- **Semantic Conventions**: Support for both stable and deprecated OpenTelemetry HTTP semantic conventions to ensure compatibility with a wide range of observability tools.
+- **Optimized Performance**: Tracing is designed with a "pay only for what you use" approach. Overhead is near-zero when disabled, and allocations/computations are minimized when enabled.
+- **Rich Configuration**: New configuration options for telemetry exporters, batching, and resource attributes.

.changeset/unify-hive-telemetry-config.md

@@ -0,0 +1,40 @@
+---
+config: minor
+router: minor
+internal: minor
+---
+
+# Unified Hive Telemetry Configuration
+
+Refactored the configuration structure to unify Hive-specific telemetry (tracing and usage reporting) and centralize client identification.
+
+- **Unified Hive Config**: Moved `usage_reporting` under `telemetry.hive.usage`. Usage reporting now shares the `token` and `target` configuration with Hive tracing, eliminating redundant settings.
+- **Centralized Client Identification**: Introduced `telemetry.client_identification` to define client name and version headers once. These are now propagated to both OpenTelemetry spans and Hive usage reports.
+- **Enhanced Expression Support**: Both Hive token and target ID now support VRL expressions for usage reporting, matching the existing behavior of tracing.
+
+### Breaking Changes:
+
+The top-level `usage_reporting` block has been moved. 
+
+**Before:**
+```yaml
+usage_reporting:
+  enabled: true
+  access_token: "..."
+  target_id: "..."
+  client_name_header: "..."
+  client_version_header: "..."
+```
+
+**After:**
+```yaml
+telemetry:
+  client_identification:
+    name_header: "..."
+    version_header: "..."
+  hive:
+    token: "..."
+    target: "..."
+    usage:
+      enabled: true
+```