otel_serverpod 0.1.0-beta.1

OpenTelemetry instrumentation for Serverpod. One call opens http.server semconv spans per endpoint method call (route = endpoint.method), db.* client spans for the database layer, and the standard htt [...]

Changelog

0.1.0-beta.1 - 2026-08-04

Added

• OtelServerpod.install(pod) — one call installs, on the Serverpod 4.0 line:
  • W3C context extraction (traceparent/tracestate/baggage) and one http.server span per endpoint method call, named POST endpoint.method with http.route = endpoint.method and the rpc.system.name/rpc.method registry attributes;
  • http.server.request.duration (registry bucket advice) and http.server.active_requests metrics.
• OtelServerpod.databaseInterceptor — pass to the Serverpod(databaseInterceptor:) constructor parameter for db.* client spans (find person, insert order, ...) and db.client.operation.duration per typed database operation. db.query.text only on unsafe* raw-SQL operations and only with captureDbStatements: true (privacy default OFF).
• OtelFutureCall — one-line-per-call traced FutureCall base class (extends OtelFutureCall, override run instead of invoke).
• OtelServerpodSemantics — exported consts for every emitted name not in the rc.1 semconv enums.

Known limitations

• MethodStreamConnector (websocket method streams) passes through unwrapped — streaming works, stream spans are a tracked follow-up.
• Dev-mode hot reload re-initializes Serverpod's connectors, dropping the endpoint span names until restart; middleware and metrics survive.
• Serverpod 3.4.x is not supported: the databaseInterceptor constructor parameter and the stable Database surface this package wraps exist only on the 4.0 line (constraint >=4.0.0-beta.1 <4.1.0, capped because upstream reserves the right to break the Database API in minor bumps).