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
<!-- Repeat the following section for each resource type/namespace in your service. Find the table(s) for your service at https://learn.microsoft.com/azure/azure-monitor/reference/tables-index.
133
-
Replace the <ResourceType/namespace> and tablename placeholders with the namespace name. -->
@@ -147,12 +147,12 @@ The following example JSON snippet shows a health probe log entry for a failed h
147
147
148
148
For more information on the Front Door web application firewall (WAF) logs, see [Azure Web Application Firewall monitoring and logging](../web-application-firewall/afds/waf-front-door-monitor.md).
149
149
150
-
151
-
152
150
::: zone-end
153
151
154
152
::: zone pivot="front-door-classic"
155
153
154
+
For classic Azure Front Door, built-in monitoring includes diagnostic logs.
Diagnostic logs provide rich information about operations and errors that are important for auditing and troubleshooting. Diagnostic logs differ from activity logs.
@@ -205,10 +205,10 @@ Raw logs include logs generated from both CDN edge (child POP) and origin shield
205
205
206
206
For every request that goes to an origin shield, there are two log entries:
207
207
208
-
* One for edge nodes
209
-
* One for origin shield.
208
+
- One for edge nodes
209
+
- One for origin shield
210
210
211
-
To differentiate the egress or responses from the edge nodes vs. origin shield, you can use the field **isReceivedFromClient** to get the correct data.
211
+
To differentiate the egress or responses from the edge nodes vs. origin shield, you can use the field **isReceivedFromClient** to get the correct data.
212
212
213
213
If the value is false, then it means the request is responded from origin shield to edge nodes. This approach is effective to compare raw logs with billing data. Charges aren't incurred for egress from origin shield to the edge nodes. Charges are incurred for egress from the edge nodes to clients.
214
214
@@ -239,46 +239,19 @@ After the chunk arrives at the Azure Front Door edge, it's cached and immediatel
239
239
240
240
::: zone-end
241
241
242
-
243
-
<!-- Add any monitoring mechanisms build in to your service here. -->
244
-
245
-
<!--## Use Azure Monitor tools to analyze the data-->
0 commit comments