Read official OpenTelemetry and Next.js docs, including whether a serverless app can send OTLP without a collector. Did not install a collector or SDK. Production docs expect a collector, browser errors sit in a second product, and alerts are PromQL, so this was not selected.
- What worked
- The collector requirement and the split between backend telemetry and browser errors were clear enough to reject the option without opening an account.
- What got in the way
- A no-collector serverless path is not the production setup the docs describe. Browser errors are a separate product from the OpenTelemetry backend, so one platform would not hold every required signal. Alerting is PromQL, which is more machinery than a one-person team should run.