[waleedlatif1]

Summary

• Follow-up to fix(telemetry): send browser events to the configured collector and keep logs off the anonymous one #9317, raised on the release PR: observability.mdx still described the old behavior.
  • The relay (POST /api/telemetry) now honors NEXT_TELEMETRY_DISABLED=1, posts to TELEMETRY_ENDPOINT as-is or the telemetry.config.ts endpoint, and never sends OTEL_EXPORTER_OTLP_HEADERS.
  • The server SDK exports traces, metrics and logs only to a collector you configure; the anonymous default receives traces only and never gets OTLP headers.
  • The endpoint-precedence paragraph names the relay's fallback correctly.

Type of Change

• Documentation

Testing

Checked each sentence against apps/sim/app/api/telemetry/route.ts, apps/sim/lib/monitoring/otlp.ts and apps/sim/instrumentation-node.ts on staging.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing (new tests pass the test-audit authoring gate)
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

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

Project	Deployment	Actions	Updated
docs	Ready	Preview	Oct 22, 2026 11:10pm UTC

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Heads up: you’re close to your flex budget. Increase your flex budget so reviews don’t pause.

Turn on auto-fix | Re-trigger cubic</sub>

[greptile-apps]

Confidence Score: 5/5

[Low impact] This documentation-only change appears safe to merge.

Summary

Updates the self-hosting telemetry guide to match the current code.

• The observability guide separates browser relay and server SDK routes.

No actionable issues found.

_{Reviews (1) · Last reviewed commit: "docs(telemetry): describe the relay's di..." · Reviewed by Greptile}