Loading

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.

If the troubleshooting steps above don't resolve your issue, you can reach the team through the Elastic discuss forum or by opening a GitHub issue. Use the following guidance to choose the right repo:

  • Open an issue in the EDOT Browser repo if the issue relates to:

    • EDOT Browser-specific behavior or configuration options (for example, startBrowserSdk, otlpEndpoint)
    • Elastic-specific defaults or signal configuration
    • EDOT Browser packaging or installation
    • Sending data to Elastic Observability

  • Open an issue in the OpenTelemetry JS repo or JS contrib repo if the issue relates to:

    • A specific instrumentation (for example, @opentelemetry/instrumentation-fetch, @opentelemetry/instrumentation-user-interaction)
    • OpenTelemetry SDK core behavior
    • OpenTelemetry specification compliance