Troubleshooting EDOT Browser

If telemetry doesn't appear in Elastic Observability, try the following:

• Confirm the otlpEndpoint option points to your reverse proxy (not directly to Elastic Observability) and doesn't include signal paths like /v1/traces.
• Check the browser console for network errors or OpenTelemetry-related messages. Cross-Origin Resource Sharing (CORS) errors often mean the reverse proxy is not sending the right Access-Control-Allow-Origin or preflight response.
• Ensure the reverse proxy can reach your EDOT Collector or Elastic Cloud Managed OTLP endpoint. To do so, check proxy logs for connection or authorization failures.
• Ensure service name is set and doesn't contain special characters.
• Set logLevel to debug or verbose in the startBrowserSdk options to see detailed export and instrumentation output in the console.

If you use a Content Security Policy, ensure the proxy or OTLP endpoint domain is in the connect-src directive. For bundler or module resolution errors, refer to OpenTelemetry for Real User Monitoring (RUM) and the general OpenTelemetry ingest troubleshooting docs.

• Refer to Known limitations for what is not yet supported.
• Refer to Set up EDOT Browser, Install the agent, and Proxy and CORS for installation and proxy configuration.
• For general OTLP ingest issues, refer to OpenTelemetry ingest troubleshooting.