Skip to content

Commit a956ece

Browse files
committed
update diagnostic setting instructions
1 parent 73e223a commit a956ece

File tree

1 file changed

+14
-11
lines changed

1 file changed

+14
-11
lines changed

articles/frontdoor/standard-premium/how-to-logs.md

Lines changed: 14 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: halkazwini
55
ms.author: halkazwini
66
ms.service: azure-frontdoor
77
ms.topic: how-to
8-
ms.date: 05/20/2025
8+
ms.date: 05/21/2025
99
---
1010

1111
# Configure Azure Front Door logs
@@ -26,19 +26,22 @@ Access logs, health probe logs, and Web Application Firewall (WAF) logs aren't e
2626

2727
1. In **Diagnostic setting**, enter a name for **Diagnostic setting name**.
2828

29-
1. Select the **log** options for **FrontDoor Access Log**, **FrontDoor Health Probe Log**, and **FrontDoor WebApplicationFirewall Log**.
29+
1. Under **Logs**, select **audit**, **allLogs** or the  individual log you want. Available logs are: **FrontDoor Access Log**, **FrontDoor Health Probe Log**, and **FrontDoor WebApplicationFirewall Log**.
3030

3131
1. Select the **Destination details**. The destination options are:
3232

33-
* **Send to Log Analytics**
34-
* Azure Log Analytics in Azure Monitor is best used for general real-time monitoring and analysis of Azure Front Door performance.
35-
* Select the *Subscription* and *Log Analytics workspace*.
36-
* **Archive to a storage account**
37-
* Storage accounts are best used for scenarios when logs are stored for a longer duration and are reviewed when needed.
38-
* Select the *Subscription* and the *Storage Account*. and set **Retention (days)**.
39-
* **Stream to an event hub**
40-
* Event hubs are a great option for integrating with other security information and event management (SIEM) tools or external data stores, such as Splunk, Datadog, or Sumo.
41-
* Select the *Subscription*, *Event hub namespace*, *Event hub name (optional)*, and *Event hub policy name*.
33+
- **Send to Log Analytics**
34+
- Azure Log Analytics in Azure Monitor is best used for general real-time monitoring and analysis of Azure Front Door performance.
35+
- Select the *Subscription* and *Log Analytics workspace*.
36+
- **Archive to a storage account**
37+
- Storage accounts are best used for scenarios when logs are stored for a longer duration and are reviewed when needed.
38+
- Select the *Subscription* and *Storage Account*.
39+
- **Stream to an event hub**
40+
- Event hubs are a great option for integrating with other security information and event management (SIEM) tools or external data stores, such as Splunk, Datadog, or Sumo.
41+
- Select the *Subscription*, *Event hub namespace*, *Event hub name (optional)*, and *Event hub policy name*.
42+
- **Send to partner solution**
43+
- Partner solutions are fully integrated solutions with Azure. For more information, see [Destinations in Azure Monitor diagnostic settings](/azure-monitor/platform/diagnostic-settings#destinations) and [Azure Monitor partner solutions](/azure/partner-solutions/partners#observability).
44+
- Select the *Subscription* and *Destination*.
4245

4346
> [!TIP]
4447
> Microsoft recommends using Log Analytics for real-time monitoring and analysis of Azure Front Door performance.

0 commit comments

Comments
 (0)