Add browser SDK setup options to Cdocs browser partial#37270
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…age" This reverts commit 1f1d825.
|
Closing — change was accidentally committed to the wrong branch. New PR incoming. |
Preview links (active after the
|
@github-actions this can be ignored because it's for the specific instrumentation option |
urseberry
left a comment
There was a problem hiding this comment.
Thanks for the detailed summary in the PR description to help me understand the scope of the changes!
I did not contact cdocs-reviewers, so make sure that you also get a review from someone in that group.
There was a problem hiding this comment.
This file needs to be removed from the repository and from this PR, since it will be generated by Cdocs going forward. Similarly, you need to add an entry for it to the .gitignore. For an example, see #36102
| [12]: /real_user_monitoring/application_monitoring/browser/setup/server | ||
| [13]: /real_user_monitoring/application_monitoring/agentic_onboarding/?tab=realusermonitoring |
There was a problem hiding this comment.
| [13]: /real_user_monitoring/application_monitoring/agentic_onboarding/?tab=realusermonitoring |
The body no longer references links 12 and 13, so you should remove them.
| @@ -0,0 +1,11 @@ | |||
| #### Limitations | |||
|
|
|||
| Auto-instrumentation for this server has the following limitations. If your use case requires more control, use [client-side instrumentation][101] instead. | |||
There was a problem hiding this comment.
| Auto-instrumentation for this server has the following limitations. If your use case requires more control, use [client-side instrumentation][101] instead. | |
| Server-side auto-instrumentation has the following limitations. If your use case requires more control, use [client-side instrumentation][101] instead. |
When this partial shows up on the index page (https://docs-staging.datadoghq.com/rtrieu/add-browser-setup-options/client_sdks/setup/), the user hasn't had to select a server, so "this server" doesn't make sense. I suggest rewording it to be more general.
|
|
||
| ## Overview | ||
|
|
||
| The Datadog Browser SDK enables Real User Monitoring (RUM) for your web applications, providing comprehensive visibility into user experience and application performance. With RUM, you can monitor page load times, user interactions, resource loading, and application errors in real-time. |
There was a problem hiding this comment.
| The Datadog Browser SDK enables Real User Monitoring (RUM) for your web applications, providing comprehensive visibility into user experience and application performance. With RUM, you can monitor page load times, user interactions, resource loading, and application errors in real-time. | |
| The Datadog Browser SDK enables Real User Monitoring (RUM) for your web applications, providing visibility into user experience and application performance. With RUM, you can monitor page load times, user interactions, resource loading, and application errors in real time. |
| There are three ways to instrument your browser-based web applications with the Browser SDK: | ||
|
|
||
| - [**Manual client-side setup**][1]: Instrument your browser-based web applications, deploy them, configure the initialization parameters you want to track, and use advanced configuration to further manage the data and context that RUM collects. | ||
| - [**Agentic Onboarding**][2]: Instrument your frontend applications with one prompt using LLM coding agents like Cursor or Claude. |
There was a problem hiding this comment.
| - [**Agentic Onboarding**][2]: Instrument your frontend applications with one prompt using LLM coding agents like Cursor or Claude. | |
| - [**Agentic Onboarding**][2]: Instrument your frontend applications with one prompt using LLM coding agents such as Cursor or Claude. |
| | **SDK setup mechanism** | Manually add the RUM SDK to your application code and manage configurations in code. | Use an AI-guided setup that detects your project's framework and adds the RUM SDK with a single prompt. | Automatically add RUM JS to your web app HTML, then manage configurations in the UI. | | ||
| | **Code changes required** | Yes | Yes (automated by AI agent) | No | | ||
| | **Setup complexity** | Medium | Low | Low | | ||
| | **Supported platforms** | All browser-based applications | Next.js, React, Svelte, Vue, Vanilla JavaScript | Apache, IBM HTTP Server, Java Servlet, Nginx, Windows IIS | |
There was a problem hiding this comment.
| | **Supported platforms** | All browser-based applications | Next.js, React, Svelte, Vue, Vanilla JavaScript | Apache, IBM HTTP Server, Java Servlet, Nginx, Windows IIS | | |
| | **Supported platforms** | All browser-based applications | Next.js, React, Svelte, Vue, Vanilla JavaScript | Apache, IBM HTTP Server, Java Servlet, NGINX, Windows IIS | |
What does this PR do? What is the motivation?
Fixes DOCS-14485
Best to preview this page: https://docs-staging.datadoghq.com/rtrieu/add-browser-setup-options/client_sdks/setup/?platform=browser
Merge instructions
Merge readiness:
Additional notes