Skip to content

Product Update - Tracing and metrics in Hive Router #90

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dotansimha merged 1 commit into from
Apr 15, 2026
+38 −0
Merged

Product Update - Tracing and metrics in Hive Router #90

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 38 additions & 0 deletions .../product-updates/2026-04-15-hive-router-opentelemetry-tracing-metrics/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
---
title: OpenTelemetry Tracing and Prometheus Metrics in Hive Router
description:
Hive Router now supports production-ready OpenTelemetry tracing and metrics, including OTLP
export and Prometheus scraping.
date: 2026-04-15
authors: [kamil]
---

[Hive Router](/docs/router) now includes first-class observability with OpenTelemetry: distributed
tracing, configurable metrics, OTLP exporters, and a Prometheus scrape endpoint.

## Tracing with OpenTelemetry

Hive Router can emit traces to [Hive Console Tracing](/docs/router/observability/tracing#send-traces-to-hive-console) and any OTLP-compatible backend over HTTP or gRPC.

Tracing includes GraphQL-specific spans as well as router and subgraph lifecycle spans, with configurable propagation for `trace_context`, `baggage`, `b3`, and `jaeger`.

## Metrics with OTLP and Prometheus

Hive Router emits OpenTelemetry metrics covering inbound and outbound HTTP traffic, GraphQL errors and execution, supergraph polling and processing, and internal cache activity.

Metrics can be exported to OTLP-compatible backends, exposed for Prometheus scraping, or both. For Prometheus, you can expose metrics on the router's HTTP server or a dedicated port, with a configurable path (default `/metrics`).

## Highly customizable

Tracing and metrics can be dialed in to balance cost and throughput:

- **Sampling and batching** - supports head-based and parent-based sampling, with configurable batch processing and export settings
- **Metric instrument overrides** - disable selected instruments or drop high-cardinality labels
- **Histogram aggregation controls** - supports `explicit` and `exponential` aggregations, with dedicated buckets for time and size units

This gives you the flexibility to keep observability lightweight at the start, and scale it up as your traffic and requirements evolve.

---

- [OpenTelemetry Tracing](/docs/router/observability/tracing)
- [OpenTelemetry Metrics](/docs/router/observability/metrics)
Loading