You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/serverless/azure_app_service/windows_code.md
+15-7Lines changed: 15 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,21 +48,25 @@ The Datadog .NET, Java, and Node.js APM extensions support the following runtime
48
48
49
49
{{< tabs >}}
50
50
{{% tab ".NET" %}}
51
+
51
52
Datadog's automatic instrumentation relies on the .NET CLR Profiling API. This API allows only one subscriber (for example, Datadog's .NET Tracer with Profiler enabled). To ensure maximum visibility, run only one APM solution within your application environment.
52
53
53
54
Additionally, if you are using the Azure Native integration, you can use the Datadog resource in Azure to add the extension to your .NET apps. For instructions, see the [App Service extension section][1] of Datadog's [Azure Native integration guide][2].
Support for Java Web Apps is in Preview for extension v2.4+.
60
62
61
63
There are no billing implications for tracing Java Web Apps during this period.
64
+
62
65
{{% /tab %}}
63
66
{{< /tabs >}}
64
67
65
68
## Installation
69
+
66
70
Datadog recommends doing regular updates to the latest version of the extension to ensure optimal performance, stability, and availability of features. Note that both the initial install and subsequent updates require your web app to be fully stopped in order to install/update successfully.
67
71
68
72
If you haven't already, set up the [Datadog-Azure integration][3]. You can verify that your Azure integration is configured correctly by ensuring that you see the `azure.app_services.count` or `azure.functions.count` metrics in Datadog.
@@ -182,7 +186,7 @@ The [Datadog Windows Web App module][2] only deploys the Web App resource and ex
182
186
183
187
{{< img src="infrastructure/serverless/azure_app_services/choose_extension.png" alt="Example of Extensions page in Azure portal, showing .NET Datadog APM extension." style="width:100%;" >}}
184
188
185
-
6. Accept the legal terms, click **OK**, and wait for the installation to complete.
189
+
6. Accept the legal terms, click **OK**, and wait for the installation to complete.
186
190
<divclass="alert alert-danger">This step requires that your application be in a stopped state.</div>
187
191
188
192
7. Start the main application, click **Start**:
@@ -201,7 +205,6 @@ The [Datadog Windows Web App module][2] only deploys the Web App resource and ex
201
205
{{% /tab %}}
202
206
{{< /tabs >}}
203
207
204
-
205
208
## Custom metrics
206
209
207
210
The Azure App Service extension includes an instance of [DogStatsD][1], Datadog's metrics aggregation service. This enables you to submit custom metrics, service checks, and events directly to Datadog from Azure Web Apps and Functions with the extension.
@@ -212,6 +215,7 @@ To submit custom metrics to Datadog from Azure App Service using the extension:
212
215
213
216
{{< tabs >}}
214
217
{{% tab ".NET" %}}
218
+
215
219
1. Add the [DogStatsD NuGet package](https://www.nuget.org/packages/DogStatsD-CSharp-Client) to your Visual Studio project.
216
220
2. Initialize DogStatsD and write custom metrics in your application.
1.[Initialize DogStatsD and write custom metrics][1] in your application.
259
-
1. Deploy your code to a supported Azure Web App.
260
-
1. If you have not already, install Datadog's Azure App Service Node.js extension.
264
+
2. Deploy your code to a supported Azure Web App.
265
+
3. If you have not already, install Datadog's Azure App Service Node.js extension.
261
266
262
267
<divclass="alert alert-info">You do not need to install a Node.js DogStatsD client, as it is included in the Node.js tracer (<code>dd-trace</code>) packaged in the Azure App Service extension.</div>
263
268
@@ -287,6 +292,7 @@ Learn more about [custom metrics][2].
287
292
## Logging
288
293
289
294
### Application logging
295
+
290
296
{{< tabs >}}
291
297
{{% tab ".NET" %}}
292
298
@@ -299,6 +305,7 @@ Both methods allow trace ID injection, making it possible to connect logs and tr
0 commit comments