Browser Monitoring Auto-Instrumentation (Server-Side)

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.
To try the preview for RUM Auto-Instrumentation, follow the instructions on this page.

Overview

RUM Auto-Instrumentation works by injecting the RUM Browser SDK into the HTML responses being served through a web server or proxy.

Getting started

Select a platform to start collecting RUM data on your application

To request support for a web server that is not listed here, fill out this form.

apache
ibm
nginx
windowsiis

Limitations

Keep in mind the following limitations when using auto-instrumentation:

  • This instrumentation method does not support advanced RUM configurations.
  • 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

Documentation, liens et articles supplémentaires utiles:

Learn about the RUM ExplorerDOCUMENTATION more more Learn about the Datadog Browser SDK for LogsDOCUMENTATION more more
PREVIEWING: aymeric/auto-injection-remote-configuration