v2.5.1
-
@splunk/otel-web- Trace separation of XHR and Fetch from parent trace #1693
- New
separateTracesconfiguration option that gives XHR and Fetch requests their own trace IDs instead of inheriting the parent click event's trace ID - Preserves the relationship through
parent.traceIdandparent.spanIdattributes, enabling proper Business Transaction correlation in backend APM while maintaining RUM trace correlation - Supports top-level config, per-instrumentation config, and mixed configurations with overrides
- New
- Add
user_agent.is_botanduser_agent.is_automatedattributes #1760- New global span attribute
user_agent.is_botthat uses regex detection to flag bot/crawler user agents - New global span attribute
user_agent.is_automatedthat checksnavigator.webdriverto identify browsers controlled by automation frameworks like Selenium, Puppeteer, and Playwright - Enables downstream filtering and analysis of synthetic versus real user traffic
- New global span attribute
- Add
splunk.rum.is_latest_tagattribute #1762- Adds a global span attribute
splunk.rum.is_latest_tag: truewhen the agent loads via the "latest" CDN tag - Updates deprecation warnings to clarify that the "latest" tag remains pinned to v2.5.x
- Adds a global span attribute
- Improve dead click detection for
role=buttonand anchor elements #1756- Elements with
role="button"are now treated as interactive components for dead click detection - Excludes
<a>elements with actual href attributes from detection since they trigger navigation - Keeps anchors without href or with
javascript:hrefs as candidates for detection
- Elements with
- Upgrade upstream to v2.11.1 #1758
- Trace separation of XHR and Fetch from parent trace #1693
⚠️ Upcoming breaking changes in v3.0.0
Action required before upgrading to v3.0.0:
- Domain migration: All domains are changing from
signalfx.comtoobservability.splunkcloud.com. This includes both the CDN (cdn.signalfx.com→cdn.observability.splunkcloud.com) and the ingest endpoint (rum-ingest.{realm}.signalfx.com→rum-ingest.{realm}.observability.splunkcloud.com). If your application uses a Content Security Policy (CSP), update yourscript-srcandconnect-srcdirectives to allow the new domains before upgrading. latestCDN tag discontinued: ThelatestCDN tag will stop being updated after v2.5.0. Users relying on thelatesttag should migrate to a versioned URL:
- <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>The following experimental config options will be removed in v3.0.0 and their behavior will be enabled by default. This may affect how sessions and data are counted:
_experimental_adjustSessionStartToTimeOrigin: Session start time will be automatically backdated toperformance.timeOrigin._experimental_discardDataAfterInactivity: Will be enabled by default. Data will be automatically discarded after 15 minutes of user inactivity. Set_experimental_discardDataAfterInactivity: falseto opt out.- OTLP exporter enabled by default: The OTLP exporter will replace Zipkin as the default export format. Set
exporter.otlp: falseto opt out. spaMetrics: Will be enabled by default. SetspaMetrics: falseto opt out.experimental_alignWebVitalsSpansWithDocumentLoad: All web vitals spans (LCP, CLS, INP) will be automatically anchored to the document load span — start time will match the documentLoad span timestamp rather than the time the metric was reported, andlocation.hrefwill reflect the original page load URL rather than the current URL after SPA navigation.
CDN
Version v2.5.1
background-service.html:
<script src="https://cdn.signalfx.com/o11y-gdi-rum/v2.5.1/background-service.html" integrity="sha384-0Plr22r4EPSZZYnvJBmBA9/uIjDusocispOGmWMnGxdiNRjuvgVHfOKsCCI90L1s" crossorigin="anonymous"></script>
splunk-otel-web-session-recorder.js:
<script src="https://cdn.signalfx.com/o11y-gdi-rum/v2.5.1/splunk-otel-web-session-recorder.js" integrity="sha384-UWsDRzXj6PwL9CrVe513I+khoJMsgS1MSp08bj8q8Xv0pYEMWDF3y3VVZ163Tf7m" crossorigin="anonymous"></script>
splunk-otel-web.js:
<script src="https://cdn.signalfx.com/o11y-gdi-rum/v2.5.1/splunk-otel-web.js" integrity="sha384-/IPW28xWyyOQ+DNW9SStfdmEJIhHAPyZyuWgG/6K7fkiLK0g+dg4R7DagbqzpRXv" crossorigin="anonymous"></script>Version v2.5
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.signalfx.com/o11y-gdi-rum/v2.5/background-service.html" crossorigin="anonymous"></script>
splunk-otel-web-session-recorder.js:
<script src="https://cdn.signalfx.com/o11y-gdi-rum/v2.5/splunk-otel-web-session-recorder.js" crossorigin="anonymous"></script>
splunk-otel-web.js:
<script src="https://cdn.signalfx.com/o11y-gdi-rum/v2.5/splunk-otel-web.js" crossorigin="anonymous"></script>Version v2
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.signalfx.com/o11y-gdi-rum/v2/background-service.html" crossorigin="anonymous"></script>
splunk-otel-web-session-recorder.js:
<script src="https://cdn.signalfx.com/o11y-gdi-rum/v2/splunk-otel-web-session-recorder.js" crossorigin="anonymous"></script>
splunk-otel-web.js:
<script src="https://cdn.signalfx.com/o11y-gdi-rum/v2/splunk-otel-web.js" crossorigin="anonymous"></script>Version latest
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.signalfx.com/o11y-gdi-rum/latest/background-service.html" crossorigin="anonymous"></script>
splunk-otel-web-session-recorder.js:
<script src="https://cdn.signalfx.com/o11y-gdi-rum/latest/splunk-otel-web-session-recorder.js" crossorigin="anonymous"></script>
splunk-otel-web.js:
<script src="https://cdn.signalfx.com/o11y-gdi-rum/latest/splunk-otel-web.js" crossorigin="anonymous"></script>