Type to search.

Troubleshooting EDOT Browser

Serverless Observability

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Stack

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

EDOT Browser Preview

The Elastic Distribution of OpenTelemetry (EDOT) Browser SDK (RUM) collects performance metrics, traces, and logs from web applications in OpenTelemetry format, and sends them to Elastic Observability.

Availability

  • Preview

    This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

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

  • Confirm the exportConfig.url 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, exportConfig)
    • Elastic-specific defaults or signal configuration
    • EDOT Browser packaging or installation
    • Sending data to Elastic Observability

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

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