Optional
allowedList of origins where the SDK is allowed to run when used in a browser extension context. Matches urls against the extensions origin. If not provided and the SDK is running in a browser extension, a warning will be displayed.
Optional
allowAllows the use of localStorage when cookies cannot be set. This enables the RUM Browser SDK to run in environments that do not provide cookie support.
Important: If you are using the RUM and Logs Browser SDKs, this option must be configured with identical values See Monitor Electron Applications Using the Browser SDK for further information.
Optional
allowAllow listening to DOM events dispatched programmatically (untrusted events). Enabling this option can be useful if you heavily rely on programmatic events, such as in an automated UI test environment.
Optional
beforeAccess to every logs collected by the Logs SDK before they are sent to Datadog. It allows:
The client token for Datadog. Required for authenticating your application with Datadog.
Optional
datacenter[Internal option] Set the datacenter from where the data is dual shipped
Optional
envThe application’s environment, for example: prod, pre-prod, and staging. Follows the tag syntax requirements.
Optional
forwardForward logs from console.* to Datadog. Use "all" to forward everything or an array of console API names to forward only a subset.
Optional
forwardForward console.error logs, uncaught exceptions and network errors to Datadog.
Optional
forwardForward reports from the Reporting API to Datadog. Use "all" to forward everything or an array of report types to forward only a subset.
Optional
proxyOptional proxy URL, for example: https://www.proxy.com/path. See Proxy Your Browser RUM Data for further information.
Optional
replica[Internal option] Configure the dual shipping to another datacenter
Optional
serviceThe service name for your application. Follows the tag syntax requirements.
Optional
sessionWhich storage strategy to use for persisting sessions. Can be either 'cookie' or 'local-storage'.
Important: If you are using the RUM and Logs Browser SDKs, this option must be configured with identical values
Optional
sessionThe percentage of sessions tracked. A value between 0 and 100.
Optional
silentInitialization fails silently if the RUM Browser SDK is already initialized on the page.
Optional
siteThe Datadog site parameter of your organization.
Optional
storeStore global context and user context in localStorage to preserve them along the user navigation. See Contexts life cycle for further information.
Optional
telemetryThe percentage of telemetry events sent. A value between 0 and 100.
Optional
trackTrack anonymous user for the same site and extend cookie expiration date
Optional
trackingSet the initial user tracking consent state. See User tracking consent for further information.
Optional
trackPreserve the session across subdomains for the same site.
Important: If you are using the RUM and Logs Browser SDKs, this option must be configured with identical values
Optional
useUse a partitioned secure cross-site session cookie. This allows the RUM Browser SDK to run when the site is loaded from another one (iframe). Implies useSecureSessionCookie
.
Important: If you are using the RUM and Logs Browser SDKs, this option must be configured with identical values
Optional
useUse PCI-compliant intake. See PCI DSS Compliance for further information.
Optional
useUse a secure session cookie. This disables RUM events sent on insecure (non-HTTPS) connections.
Important: If you are using the RUM and Logs Browser SDKs, this option must be configured with identical values
Optional
versionThe application’s version, for example: 1.2.3, 6c44da20, and 2020.02.13. Follows the tag syntax requirements.
Init Configuration for the Logs browser SDK.
Example