Send OpenTelemetry traces to Dynatrace and remove Vercel Analytics

[TimoStaudinger]

Exports server-side traces to Dynatrace via OpenTelemetry, and removes Vercel Analytics now that Dynatrace RUM (#81) covers audience monitoring.

Changes

• Added src/instrumentation.ts registering OpenTelemetry through @vercel/otel, with an OTLP http/protobuf trace exporter pointed at the Dynatrace OTLP API — the format Dynatrace ingest requires (no gRPC, no JSON)
• Added @vercel/otel and its OpenTelemetry peer dependencies (yarn 1 does not install peers automatically)
• Removed @vercel/analytics and its usage in the root layout
• Documented the new environment variables in the README

Configuration

Tracing activates only when both variables are set (in Vercel for production):

• DYNATRACE_OTLP_ENDPOINT — https://{environment-id}.live.dynatrace.com/api/v2/otlp
• DYNATRACE_API_TOKEN — access token with the openTelemetryTrace.ingest scope (server-side only, no NEXT_PUBLIC_ prefix)

When either is unset — locally, in CI — register() returns early and no SDK is registered.

Verification

• Smoke-tested end to end: ran the production server against a local OTLP sink and confirmed spans arrive as POST …/v1/traces with Content-Type: application/x-protobuf and the Api-Token authorization header
• yarn build and all functional Playwright tests pass; visual snapshots unaffected

🤖 Generated with Claude Code

---

Generated by Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
timostaudinger-com	Ready	Preview	Aug 21, 2026 8:17pm