Auto instrumentation updates v2 (#28766)

* move limitations around and add further reading

* move limitations and add more descriptions

* Apply suggestions from code review

Co-authored-by: Joe Peeples <[email protected]>

* Apply suggestions from code review

Co-authored-by: Benoît <[email protected]>

---------

Co-authored-by: Joe Peeples <[email protected]>
Co-authored-by: Benoît <[email protected]>

Author: 3 people

content/en/real_user_monitoring/browser/setup/server/_index.md

@@ -48,10 +48,20 @@ To remotely configure your RUM application:
 
 <div class="alert alert-warning">To request support for a web server that is not listed here, <a href="https://www.datadoghq.com/private-beta/rum-sdk-auto-injection/">fill out this form.</a></div>
 
-Follow the documentation for your web server type to learn more:
+If you don't want to configure your RUM applications remotely, follow the documentation for your web server type to configure your RUM application locally:
 
+<br>
 {{< partial name="rum/rum-browser-setup.html" >}}
+<br>
 
+## Limitations
+
+Keep in mind the following limitations when using this setup:
+
+- This instrumentation method **does not support [advanced RUM configurations][1]**, except for `allowedTracingUrls` and `excludedActivityUrls`.
+- If your web server is acting as a proxy and the upstream server uses **end-to-end encryption (TLS)** or **content compression** (gzip, zstd, Brotli), the RUM Browser SDK **cannot be injected**. To ensure proper instrumentation:
+  - **Disable content compression** on the upstream server.
+  - **Enable TLS origination** on the web server.
 
 ## Further reading
 

content/en/real_user_monitoring/browser/setup/server/apache.md

@@ -4,6 +4,10 @@ beta: true
 code_lang: apache
 type: multi-code-lang
 code_lang_weight: 3
+further_reading:
+- link: '/real_user_monitoring/browser/setup/server/'
+  tag: 'Documentation'
+  text: 'Browser Monitoring Auto-Instrumentation (Server-Side)'
 ---
 
 <div class="alert alert-info">To try the preview for RUM Auto-Instrumentation, follow the instructions on this page.</div>
@@ -12,14 +16,7 @@ code_lang_weight: 3
 
 RUM Auto-Instrumentation works by injecting the RUM Browser SDK into the HTML responses being served through a web server or proxy.
 
-## Limitations
-
-Keep in mind the following limitations when using this setup:
-
-- This instrumentation method **does not support [advanced RUM configurations][1]**, except for `allowedTracingUrls` and `excludedActivityUrls`.
-- If your web server is acting as a proxy and the upstream server uses **end-to-end encryption (TLS)** or **content compression** (gzip, zstd, Brotli), the RUM Browser SDK may **not be injected**. To ensure proper instrumentation:
-  - **Disable content compression** on the upstream server.
-  - **Enable TLS origination** on the web server.
+To understand important limitations and compatibility requirements, see [Limitations][1].
 
 ## Prerequisites
 
@@ -47,6 +44,8 @@ To automatically instrument your RUM application:
 
 {{% collapse-content title="Manual configuration" level="h5" %}}
 
+To manually load the module onto your web server instead of running the installation script, follow the instructions below.
+
 To manually instrument your RUM application:
 
 #### Download the module file
@@ -106,9 +105,15 @@ To update your RUM Application:
 If you notice that RUM is not being injected into HTML pages, consider the following potential causes:
 
 - **Content-Type mismatch**: RUM is injected only into HTML pages. If the `Content-Type` header does not correctly indicate `text/html`, the injection is skipped.
-- **Upstream server has end-to-end encryption or content compression**: See [Limitations](#limitations).
 
-[1]: /real_user_monitoring/browser/advanced_configuration/
+### Limitations
+See other [Limitations][1].
+
+## Further reading
+
+{{< partial name="whats-next/whats-next.html" >}}
+
+[1]: /real_user_monitoring/browser/setup/server/#limitations
 [2]: /agent/
 [3]: https://httpd.apache.org/modules/
 [4]: https://app.datadoghq.com/rum/list

content/en/real_user_monitoring/browser/setup/server/ibm.md

@@ -4,6 +4,10 @@ beta: true
 code_lang: ibm
 type: multi-code-lang
 code_lang_weight: 4
+further_reading:
+- link: '/real_user_monitoring/browser/setup/server/'
+  tag: 'Documentation'
+  text: 'Browser Monitoring Auto-Instrumentation (Server-Side)'
 ---
 
 <div class="alert alert-info">To try the preview for RUM Auto-Instrumentation, follow the instructions on this page.</div>
@@ -12,14 +16,7 @@ code_lang_weight: 4
 
 RUM Auto-Instrumentation works by injecting the RUM Browser SDK into the HTML responses being served through a web server or proxy.
 
-## Limitations
-
-Keep in mind the following limitations when using this setup:
-
-- This instrumentation method **does not support [advanced RUM configurations][1]**, except for `allowedTracingUrls` and `excludedActivityUrls`.
-- If your web server is acting as a proxy and the upstream server uses **end-to-end encryption (TLS)** or **content compression** (gzip, zstd, Brotli), the RUM Browser SDK may **not be injected**. To ensure proper instrumentation:
-  - **Disable content compression** on the upstream server.
-  - **Enable TLS origination** on the web server.
+To understand important limitations and compatibility requirements, see [Limitations][1].
 
 ## Prerequisites
 
@@ -50,6 +47,8 @@ To automatically instrument your RUM application:
 
 {{% collapse-content title="Manual configuration" level="h5" %}}
 
+To manually load the module onto your web server instead of running the installation script, follow the instructions below.
+
 To manually instrument your RUM application:
 
 #### Download the module file
@@ -111,9 +110,15 @@ To update your RUM Application:
 If you notice that RUM is not being injected into HTML pages, consider the following potential causes:
 
 - **Content-Type mismatch**: RUM is injected only into HTML pages. If the `Content-Type` header does not correctly indicate `text/html`, the injection is skipped.
-- **Upstream server has end-to-end encryption or content compression**: See [Limitations](#limitations).
 
-[1]: /real_user_monitoring/browser/advanced_configuration/
+### Limitations
+See other [Limitations][1].
+
+## Further reading
+
+{{< partial name="whats-next/whats-next.html" >}}
+
+[1]: /real_user_monitoring/browser/setup/server/#limitations
 [2]: /agent/
 [3]: https://httpd.apache.org/modules/
 [4]: https://rum-auto-instrumentation.s3.amazonaws.com/httpd/latest/mod_datadog-amd64.zip

content/en/real_user_monitoring/browser/setup/server/nginx.md

@@ -4,6 +4,10 @@ beta: true
 code_lang: nginx
 type: multi-code-lang
 code_lang_weight: 5
+further_reading:
+- link: '/real_user_monitoring/browser/setup/server/'
+  tag: 'Documentation'
+  text: 'Browser Monitoring Auto-Instrumentation (Server-Side)'
 ---
 
 <div class="alert alert-info">To try the preview for RUM Auto-Instrumentation, follow the instructions on this page.</div>
@@ -12,14 +16,7 @@ code_lang_weight: 5
 
 RUM Auto-Instrumentation works by injecting the RUM Browser SDK into the HTML responses being served through a web server or proxy.
 
-## Limitations
-
-Keep in mind the following limitations when using this setup:
-
-- This instrumentation method **does not support [advanced RUM configurations][1]**, except for `allowedTracingUrls` and `excludedActivityUrls`.
-- If your web server is acting as a proxy and the upstream server uses **end-to-end encryption (TLS)** or **content compression** (gzip, zstd, Brotli), the RUM Browser SDK may **not be injected**. To ensure proper instrumentation:
-  - **Disable content compression** on the upstream server.
-  - **Enable TLS origination** on the web server.
+To understand important limitations and compatibility requirements, see [Limitations][1].
 
 ## Prerequisites
 
@@ -51,6 +48,8 @@ To automatically instrument your RUM application:
 
 {{% collapse-content title="Manual configuration" level="h5" %}}
 
+To manually load the module onto your web server instead of running the installation script, follow the instructions below.
+
 To manually instrument your RUM application:
 
 #### Download the appropriate `.tgz` file
@@ -122,7 +121,9 @@ Since the module is in Preview, it's possible NGINX may stop serving requests, p
 If you notice that RUM is not being injected into HTML pages, consider the following potential causes:
 
 - **Content-Type mismatch**: RUM is injected only into HTML pages. If the `Content-Type` header does not correctly indicate `text/html`, the injection is skipped.
-- **Upstream server has end-to-end encryption or content compression**: See [Limitations](#limitations).
+
+### Limitations
+See other [Limitations][1].
 
 ## Reference
 
@@ -147,8 +148,11 @@ If you notice that RUM is not being injected into HTML pages, consider the follo
 | 1.27.3 | [ngx_http_datadog-amd64-1.27.3][35] | [ngx_http_datadog-arm64-1.27.3][36] |
 | 1.27.4 | [ngx_http_datadog-amd64-1.27.4][37] | [ngx_http_datadog-arm64-1.27.4][38] |
 
+## Further reading
+
+{{< partial name="whats-next/whats-next.html" >}}
 
-[1]: /real_user_monitoring/browser/advanced_configuration/
+[1]: /real_user_monitoring/browser/setup/server/#limitations
 [2]: /agent/
 [3]: https://docs.nginx.com/nginx/admin-guide/dynamic-modules/dynamic-modules/
 [4]: https://app.datadoghq.com/rum/list

content/en/real_user_monitoring/browser/setup/server/windows_iis.md

@@ -4,6 +4,10 @@ beta: true
 code_lang: windows_iis
 type: multi-code-lang
 code_lang_weight: 6
+further_reading:
+- link: '/real_user_monitoring/browser/setup/server/'
+  tag: 'Documentation'
+  text: 'Browser Monitoring Auto-Instrumentation (Server-Side)'
 ---
 
 <div class="alert alert-info">To try the preview for RUM Auto-Instrumentation, follow the instructions on this page.</div>
@@ -12,14 +16,7 @@ code_lang_weight: 6
 
 RUM Auto-Instrumentation works by injecting the RUM Browser SDK into the HTML responses being served through a web server or proxy.
 
-## Limitations
-
-Keep in mind the following limitations when using this setup:
-
-- This instrumentation method **does not support [advanced RUM configurations][1]**, except for `allowedTracingUrls` and `excludedActivityUrls`.
-- If your web server is acting as a proxy and the upstream server uses **end-to-end encryption (TLS)** or **content compression** (gzip, zstd, Brotli), the RUM Browser SDK may **not be injected**. To ensure proper instrumentation:
-  - **Disable content compression** on the upstream server.
-  - **Enable TLS origination** on the web server.
+To understand important limitations and compatibility requirements, see [Limitations][1].
 
 ## Prerequisites
 
@@ -72,10 +69,15 @@ To update your RUM Application:
 If you notice that RUM is not being injected into HTML pages, consider the following potential causes:
 
 - **Content-Type mismatch**: RUM is injected only into HTML pages. If the `Content-Type` header does not correctly indicate `text/html`, the injection is skipped.
-- **Upstream server has end-to-end encryption or content compression**: See [Limitations](#limitations).
 
+### Limitations
+See other [Limitations][1].
+
+## Further reading
+
+{{< partial name="whats-next/whats-next.html" >}}
 
-[1]: /real_user_monitoring/browser/advanced_configuration/
+[1]: /real_user_monitoring/browser/setup/server/#limitations
 [2]: /agent/
 [3]: https://app.datadoghq.com/rum/list/create/
 [4]: /real_user_monitoring/guide/best-practices-for-rum-sampling/