Instrumenting Windows IIS Server

이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.

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.

To understand important limitations and compatibility requirements, see Limitations.

The Datadog Agent is installed and configured.

The auto-instrumentation method leverages a Windows module that injects the RUM SDK into the response body for responses served by the IIS instance.

In Datadog, navigate to the Digital Experience > Add an Application Page and select the JavaScript (JS) application type.
Select Auto-Instrumentation and Windows IIS.
Set up the IIS module using either the GUI installer or command line as described below:

Download the Datadog RUM installer.
Follow the installer as an administrator by opening the .msi file.
Follow the prompts and accept the license agreement.
Set your Session and Session Replay sample rates. See guidance on configuring sampling.
Copy and run the config command shown for each IIS site that you wish to inject RUM into.

Run the Powershell command line as an administrator.
Set your Session and Session Replay sample rates. See guidance on configuring sampling.
Copy and run the config command shown for each IIS site that you wish to inject RUM into.

You can adjust your Session Sampling and Session Replay Sampling rates from the Application Management page.

To update your RUM Application:

Go to your RUM application from the Application Management list.
On the SDK Configuration page, adjust the slider or enter a specific percentage in the input box for Session Sampling or Session Replay Sampling.
Copy and replace the code in the Datadog RUM config file for the IIS site that you instrumented.

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.