Supported technologies
This page lists supported browser versions, included instrumentations and their default behavior.
At a minimum, the runtime environment must support:
- ES2022 (the SDK bundle targets this version)
- The
fetchAPI Promise- The
PerformanceandPerformanceObserverAPIs
EDOT Browser is designed to run in modern evergreen browsers that meet these requirements.
| Browser | Supported versions |
|---|---|
| Chrome | 94+ |
| Edge | 94+ |
| Firefox | 93+ |
| Safari | 15.4+ |
Internet Explorer is not supported.
If your application targets older browsers, you might need to downlevel the code with a bundler and provide polyfills. EDOT Browser doesn't include built-in polyfills.
When you install EDOT Browser as a package (refer to Install the agent), you build your application with a JavaScript bundler. The following bundlers are supported:
| Bundler | Notes |
|---|---|
| Webpack 4 | Supported. Refer to this sample configuration and adapt it to your setup. |
| Webpack 5 | Supported. Refer to this sample configuration and adapt it to your setup. |
| Rollup | Supported. Refer to this sample configuration and adapt it to your setup. |
| esbuild | Supported. No plugins are required. Refer to the example configuration. |
Usage of @elastic/opentelemetry-browser in TypeScript code requires:
- TypeScript 5.0.4 or later
- Using
"module": "node16"or "nodenext" in "tsconfig.json" to get support for handling the "exports" entry in package.json. This is so entry points like@opentelemetry/browser-instrumentation/experimental/web-vitalscan be used.
EDOT Browser bundles a curated set of OpenTelemetry JS instrumentations suitable for browser environments. This list is being reviewed and might change in future releases.
The following instrumentations are included and turned on by default. You can turn off any of them using instrumentations by setting { enabled: false } for the corresponding key when calling startBrowserSdk:
| Instrumentation | NPM package | Config key | On by default |
|---|---|---|---|
| Document load | @opentelemetry/instrumentation-document-load |
@opentelemetry/instrumentation-document-load |
Yes |
| Fetch | @opentelemetry/instrumentation-fetch |
@opentelemetry/instrumentation-fetch |
Yes |
| XMLHttpRequest | @opentelemetry/instrumentation-xml-http-request |
@opentelemetry/instrumentation-xml-http-request |
Yes |
| User interaction | @opentelemetry/instrumentation-user-interaction |
@opentelemetry/instrumentation-user-interaction |
Yes |
| Long tasks | @opentelemetry/instrumentation-long-task |
@opentelemetry/instrumentation-long-task |
Yes |
| Web exception | @opentelemetry/instrumentation-web-exception |
@opentelemetry/instrumentation-web-exception |
Yes |
| Web vitals | @opentelemetry/browser-instrumentation |
@opentelemetry/instrumentation-web-vitals |
Yes |
By default, EDOT Browser:
- Initializes tracing
- Registers included instrumentations
- Configures an OTLP exporter
- Applies Elastic-specific defaults (for example, resource detection or attribute normalization)
To turn off an instrumentation, pass instrumentations to startBrowserSdk with the instrumentation key and { enabled: false } (for example, instrumentations: { '@opentelemetry/instrumentation-long-task': { enabled: false } }).
| Component | Version |
|---|---|
| OpenTelemetry JS API | ^1.9.0 |
| OpenTelemetry JS Trace SDK | ^2.2.0 |
| OpenTelemetry JS Metrics SDK | ^2.2.0 |
| OpenTelemetry JS Logs SDK | ^0.213.0 |
For capabilities that are not yet available and per-signal limitations (metrics, traces, logs), refer to Limitations on the overview page and Metrics, traces, and logs.
- Refer to Set up EDOT Browser and Install the agent to get started.
- Refer to Metrics, traces, and logs for what is emitted per signal and what is not yet supported.
- Review Configuration to customize behavior.
- Refer to Known limitations above, Troubleshooting for EDOT Browser–specific guidance, or OpenTelemetry ingest troubleshooting for general OTLP ingest issues.