browser-sdk
browser-sdk copied to clipboard
DataDog
Datadog Browser SDK
**Describe the bug** Currently, `clientToken` and `applicationId` are public; anyone can use them to sabotage the RUM metrics if they use them on other unauthorized websites. More importantly they could...
Hi guys, here's a question I can't find my way around. Let's say I initialize the datadog rum agent as soon as possible in my index.html, and at the time...
**Describe the bug** Related to this: https://github.com/DataDog/browser-sdk/pull/1792 Getting a resource via relative url in an element's style attribute will keep it as is, which breaks in the iframe upon viewing...
**I want to track functions duration to determine if my web app is getting slower or faster** I wanna monitor event in my app. More especially want to track performances...
**Package versions** ``` "@datadog/browser-logs": "^4.28.1", "@datadog/browser-rum-slim": "^4.28.1", ``` **Describe the bug** RUM User Actions appear to have the wrong "@view.id" (which means they display with the wrong View name, etc)...
We have a proxy and we configured datadogRum to use it with the `proxyUrl` configuration. uBlock intercepts the call before even reaching our proxy Any suggestion?
Hi! I'm integrating the `@datadog/browser-rum` with at our react (16.12.0) application that uses react-router-dom (5.1.2) to manage the routers. We are currently using `HashRouter` and due to already existing analysis...
I would like to integrate RUM tracking with DataDog but do not wish to use the browser-sdk. It would be nice if the API contracts used by the browser-sdk were...
It would be very helpful to consumers if the TypeScript for configuration options was annotated. For example, in my own app, I added JSDoc comments based off the [Configuration documentation](https://github.com/DataDog/browser-sdk/blob/main/packages/rum#configuration)....
Hey Folks, With the shipping of https://github.com/DataDog/browser-sdk/pull/1601 the RUM SDK usage got **_a ton_** better for maintaining good observability and reliability on federated environments 🙏 I very much appreciate the...
