OpenTelemetry JavaScript
Vendor-neutral instrumentation for traces, metrics, and logs across commerce applications and supporting services.
How the Fieldbook uses it
We refer to OpenTelemetry JavaScript in work involving observability and incident response. Its own documentation remains the authority for installation, compatibility, and current behavior. A listing here does not imply endorsement by its maintainers.
Good fit for
- Checkout-service tracing
- Incident and reliability evidence
Before you adopt it
- Maintainer
- OpenTelemetry community
- License or usage boundary
- Apache-2.0
Check the official source for the current release, support policy, compatibility notes, and license terms. The review date on this page only records when Beseam last checked the listing.
Related guides
problem · stable
Checkout fails for only some visitors
Narrow a partial purchase failure by browser, device, market, consent state, payment method, and funnel step.
Open workflowproblem · stable
Shopify, analytics, and ad platforms disagree on revenue
Reconcile scope, dates, currency, transaction IDs, event collection, refunds, and attribution rules before comparing totals.
Open workflowskill · stable
Purchase-friction triage
Reproduce an intermittent storefront failure and narrow it to a browser, state, component, service, or configuration.
Open workflowskill · stable
Commerce measurement reconciliation
Match orders, analytics events, and attributed channel results at transaction level before comparing totals.
Open workflowplaybook · stable
Partial checkout incident triage
Coordinate support, QA, storefront, analytics, and reliability teams when a purchase failure affects only some visitors.
Open workflow