Skip to content

Commit e7475f2

Browse files
committed
add some whitespace for readability
1 parent 06e067f commit e7475f2

File tree

1 file changed

+15
-7
lines changed

1 file changed

+15
-7
lines changed

content/en/serverless/azure_app_service/windows_code.md

Lines changed: 15 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -48,21 +48,25 @@ The Datadog .NET, Java, and Node.js APM extensions support the following runtime
4848

4949
{{< tabs >}}
5050
{{% tab ".NET" %}}
51+
5152
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.
5253

5354
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].
5455

5556
[1]: /integrations/guide/azure-native-integration/#app-service-extension
5657
[2]: /integrations/guide/azure-native-integration/
58+
5759
{{% /tab %}}
5860
{{% tab "Java" %}}
5961
Support for Java Web Apps is in Preview for extension v2.4+.
6062

6163
There are no billing implications for tracing Java Web Apps during this period.
64+
6265
{{% /tab %}}
6366
{{< /tabs >}}
6467

6568
## Installation
69+
6670
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.
6771

6872
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
182186

183187
{{< 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%;" >}}
184188

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.
186190
<div class="alert alert-danger">This step requires that your application be in a stopped state.</div>
187191

188192
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
201205
{{% /tab %}}
202206
{{< /tabs >}}
203207

204-
205208
## Custom metrics
206209

207210
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:
212215

213216
{{< tabs >}}
214217
{{% tab ".NET" %}}
218+
215219
1. Add the [DogStatsD NuGet package](https://www.nuget.org/packages/DogStatsD-CSharp-Client) to your Visual Studio project.
216220
2. Initialize DogStatsD and write custom metrics in your application.
217221
3. Deploy your code to Azure App Service.
@@ -255,9 +259,10 @@ client.Increment("sample.startup");
255259

256260
{{% /tab %}}
257261
{{% tab "Node.js" %}}
262+
258263
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.
261266

262267
<div class="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>
263268

@@ -287,6 +292,7 @@ Learn more about [custom metrics][2].
287292
## Logging
288293

289294
### Application logging
295+
290296
{{< tabs >}}
291297
{{% tab ".NET" %}}
292298

@@ -299,6 +305,7 @@ Both methods allow trace ID injection, making it possible to connect logs and tr
299305

300306
[1]: /logs/log_collection/csharp/#agentless-logging-with-apm
301307
[2]: /logs/log_collection/csharp/#agentless-logging-with-serilog-sink
308+
302309
{{% /tab %}}
303310
{{% tab "Java" %}}
304311

@@ -334,6 +341,7 @@ Configure these environment variables in your Azure App Service Application Sett
334341

335342
{{< tabs >}}
336343
{{% tab ".NET" %}}
344+
337345
**Code Example: Microsoft Native Logging**
338346

339347
An example of how to set up logging in a .NET application using Microsoft.Extensions.Logging:
@@ -354,12 +362,12 @@ public class WeatherForecastController : ControllerBase
354362
public IActionResult Get()
355363
{
356364
_logger.LogInformation("Processing weather forecast request");
357-
365+
358366
// Your business logic here
359367
var forecast = GetWeatherForecast();
360-
368+
361369
_logger.LogInformation("Weather forecast retrieved for user: {UserId}", userId);
362-
370+
363371
return Ok(forecast);
364372
}
365373
}

0 commit comments

Comments
 (0)