EDOT Browser

The Elastic Distribution of OpenTelemetry Browser (EDOT Browser) is a lightweight wrapper around the OpenTelemetry SDK that makes it easy to get started using OpenTelemetry in your web applications, especially if you are using Elastic Observability as your observability solution.

See the EDOT Browser docs for details. Some direct links:

• Get started
• Configuration
• Changelog / Release Notes
• Elastic Discuss forum | GitHub issue tracker

How does EDOT Browser differ from the OpenTelemetry JS SDK?

EDOT Browser is very similar to the @opentelemetry/auto-instrumentations-web package from OpenTelemetry in its usage goal: a single-dependency that provides a simple path to zero-code instrumentation of web applications. In general, Elastic's goal is to contribute all SDK improvements upstream. That said, there are sometimes differences that are specific to Elastic (e.g. Elastic-authored additional instrumentations or specific configurations). Here is a concise list of differences:

• EDOT Browser, being a distribution of the OpenTelemetry JS SDK, always adds the telemetry.distro.* resource attributes to identify itself.

• EDOT Browser defaults to OTEL_SEMCONV_STABILITY_OPT_IN=http such that telemetry from the @opentelemetry/instrumentation-fetch and @opentelemetry/instrumentation-xml-http-request package will use stable HTTP semantic conventions by default. Upstream OpenTelemetry JS has a tracking issue for the migration to newer HTTP semantic conventions in its instrumentations.