Breaking Changes
@splunk/otel-web- Domain migration from
signalfx.comtoobservability.splunkcloud.com#1695- All endpoints have moved to new domains:
- CDN:
cdn.signalfx.com→cdn.observability.splunkcloud.com - RUM ingest:
rum-ingest.{realm}.signalfx.com→rum-ingest.{realm}.observability.splunkcloud.com - Source map upload API:
api.{realm}.signalfx.com→api.{realm}.observability.splunkcloud.com - Session Replay ingest:
rum-ingest.{realm}.signalfx.com→rum-ingest.{realm}.observability.splunkcloud.com
- CDN:
- Content Security Policy (CSP): If your application uses a CSP, you must update your directives before upgrading:
script-src: addcdn.observability.splunkcloud.com(for loading the agent and session replay via CDN)connect-src: addrum-ingest.{realm}.observability.splunkcloud.com(for telemetry and replay data export) andapi.{realm}.observability.splunkcloud.com(if using source map upload via build plugins)- The old
signalfx.comdomains can be removed from your CSP after all agents are upgraded
latestCDN tag discontinued: Thelatesttag is permanently pinned to v2.5.1 and will not receive any future updates — including v3.0.0 and beyond. Users loading the agent viacdn.signalfx.com/o11y-gdi-rum/latest/splunk-otel-web.jswill remain on v2.5.1 indefinitely. Migrate to a versioned URL on the new CDN domain:Available version locks:- <script src="https://cdn.signalfx.com/o11y-gdi-rum/latest/splunk-otel-web.js"></script> + <script src="https://cdn.observability.splunkcloud.com/o11y-gdi-rum/v3/splunk-otel-web.js"></script>
v3— major version lock (recommended), receives all minor and patch updatesv3.0— minor version lock, receives patch updates onlyv3.0.0— exact version pin
- All endpoints have moved to new domains:
- OTLP exporter enabled by default #1791
- OTLP is now the default export format when
beaconEndpointis not specified - A deprecation warning is emitted when
beaconEndpointis explicitly provided withoutexporter.otlp: true, indicating Zipkin will be removed in a future version - Migration: Set
exporter.otlp: falseto opt out.
- OTLP is now the default export format when
- Promoted experimental flags to stable defaults #1780
_experimental_adjustSessionStartToTimeOrigin→adjustSessionStartToTimeOrigin(default:true) — session start time is backdated toperformance.timeOrigin_experimental_discardDataAfterInactivity→discardDataAfterInactivity(default:true) — telemetry is discarded after 15 minutes of user inactivityspaMetricsnow defaults totrue— SPA route metrics collected by defaultexperimental_alignWebVitalsSpansWithDocumentLoad→instrumentations.webvitals.alignWebVitalsSpansWithDocumentLoad— LCP, CLS, and INP spans are anchored to the documentLoad span timestamp by default- Migration: Set individual flags to
falseto opt out of new defaults.
- Domain migration from
New Features and Improvements
-
@splunk/otel-web- Add
http.cache.hitattribute to resource spans #1768- Boolean attribute on resource fetch spans (document-load and post-document-load) indicating cache status
- Detects cache hits via 304 response status or zero transfer size with non-zero decoded body size
- Attribute is omitted for cross-origin requests without
Timing-Allow-Originheaders
- Add
_experimental_captureBrowserDebugAttributesoption #1793- Experimental flag that collects browser diagnostics (hardware concurrency, device memory, viewport/screen data, network hints, JS heap memory, storage quota, User-Agent Client Hints) and attaches them as global span attributes
- High cardinality — intended for temporary debugging only
- Add
-
@splunk/otel-web-session-recorder- Add option to store failed segments to IndexedDB #1766
- New
persistFailedReplayData: 'indexeddb'configuration option for storing failed replay segments in IndexedDB instead of localStorage - Automatic retry on subsequent page loads
- New
- Add option to store failed segments to IndexedDB #1766
-
Updated dependencies #1771, #1772, #1773, #1774, #1775, #1777, #1778, #1779, #1782, #1783, #1784, #1785, #1786, #1787, #1788, #1789, #1790
CDN
Version v3.0.0
background-service.html:
<script src="https://cdn.observability.splunkcloud.com/o11y-gdi-rum/v3.0.0/background-service.html" integrity="sha384-0Plr22r4EPSZZYnvJBmBA9/uIjDusocispOGmWMnGxdiNRjuvgVHfOKsCCI90L1s" crossorigin="anonymous"></script>
splunk-otel-web-session-recorder.js:
<script src="https://cdn.observability.splunkcloud.com/o11y-gdi-rum/v3.0.0/splunk-otel-web-session-recorder.js" integrity="sha384-dfTBovwhNIZNfT0bDhY5r1DbMmoiWTxnTMUM6lQndfPpjJZL6Ud1s1hyQFqyfXXs" crossorigin="anonymous"></script>
splunk-otel-web.js:
<script src="https://cdn.observability.splunkcloud.com/o11y-gdi-rum/v3.0.0/splunk-otel-web.js" integrity="sha384-Ic25qGYVTgaMsMh6CLv+cj/OI9QshU6d8leunR8UwWMwCH+8Km/AgClNe2oFHsjn" crossorigin="anonymous"></script>Version v3.0
WARNING: Content behind this URL might be updated when we release a new version.
For this reason we do not provide integrity attribute.
background-service.html:
<script src="https://cdn.observability.splunkcloud.com/o11y-gdi-rum/v3.0/background-service.html" crossorigin="anonymous"></script>
splunk-otel-web-session-recorder.js:
<script src="https://cdn.observability.splunkcloud.com/o11y-gdi-rum/v3.0/splunk-otel-web-session-recorder.js" crossorigin="anonymous"></script>
splunk-otel-web.js:
<script src="https://cdn.observability.splunkcloud.com/o11y-gdi-rum/v3.0/splunk-otel-web.js" crossorigin="anonymous"></script>Version v3
WARNING: Content behind this URL might be updated when we release a new version.
For this reason we do not provide integrity attribute.
background-service.html:
<script src="https://cdn.observability.splunkcloud.com/o11y-gdi-rum/v3/background-service.html" crossorigin="anonymous"></script>
splunk-otel-web-session-recorder.js:
<script src="https://cdn.observability.splunkcloud.com/o11y-gdi-rum/v3/splunk-otel-web-session-recorder.js" crossorigin="anonymous"></script>
splunk-otel-web.js:
<script src="https://cdn.observability.splunkcloud.com/o11y-gdi-rum/v3/splunk-otel-web.js" crossorigin="anonymous"></script>