Merge pull request #221197 from johndowns/front-door-logs

Front Door - Update log documentation

Author: Stacyrch140

articles/frontdoor/TOC.yml

@@ -175,6 +175,8 @@
         href: private-link.md
       - name: Understand billing
         href: billing.md
+      - name: Logs and metrics
+        href: front-door-diagnostics.md?pivots=front-door-standard-premium
       - name: Best practices
         href: best-practices.md
       - name: Scenarios
@@ -313,11 +315,11 @@
             href: standard-premium/how-to-enable-private-link-web-app.md
           - name: Azure CLI
             href: standard-premium/how-to-enable-private-link-web-app-cli.md
-      - name: Monitor and Reports
+      - name: Monitor and reports
         items:
-        - name: Configure diagnostic
+        - name: Configure diagnostic logs
           href: standard-premium/how-to-logs.md
-        - name: Set up monitoring and alerts
+        - name: Access metrics and create alerts
           href: standard-premium/how-to-monitor-metrics.md
         - name: View Front Door reports
           href: standard-premium/how-to-reports.md

articles/frontdoor/best-practices.md

@@ -6,7 +6,7 @@ author: johndowns
 ms.service: frontdoor
 ms.topic: conceptual
 ms.workload: infrastructure-services
-ms.date: 12/05/2022
+ms.date: 02/23/2023
 ms.author: jodowns
 ---
 
@@ -32,6 +32,12 @@ Front Door's features work best when traffic only flows through Front Door. You
 
 When you work with Front Door by using APIs, ARM templates, Bicep, or Azure SDKs, it's important to use the latest available API or SDK version. API and SDK updates occur when new functionality is available, and also contain important security patches and bug fixes.
 
+### Configure logs
+
+Front Door tracks extensive telemetry about every request. When you enable caching, your origin servers might not receive every request, so it's important that you use the Front Door logs to understand how your solution is running and responding to your clients. For more information about the metrics and logs that Azure Front Door records, see [Monitor metrics and logs in Azure Front Door](front-door-diagnostics.md) and [WAF logs](../web-application-firewall/afds/waf-front-door-monitor.md#waf-logs).
+
+To configure logging for your own application, see [Configure Azure Front Door logs](./standard-premium/how-to-logs.md)
+
 ## TLS best practices
 
 ### Use end-to-end TLS
@@ -48,7 +54,7 @@ You can configure Front Door to automatically redirect HTTP requests to use the
 
 ### Use managed TLS certificates
 
-When Front Door manages your TLS certificates, it reduces your operational costs, and helps you to avoid costly outages caused by forgetting to renew a certificate. Front Door automatically issues and rotates managed TLS certificates.
+When Front Door manages your TLS certificates, it reduces your operational costs, and helps you to avoid costly outages caused by forgetting to renew a certificate. Front Door automatically issues and rotates the managed TLS certificates.
 
 For more information, see [Configure HTTPS on an Azure Front Door custom domain using the Azure portal](standard-premium/how-to-configure-https-custom-domain.md).
 
@@ -62,7 +68,7 @@ For more information, see [Select the certificate for Azure Front Door to deploy
 
 ### Use the same domain name on Front Door and your origin
 
-Front Door can rewrite the `Host` header of incoming requests. This feature can be helpful when you manage a set of customer-facing custom domain names that route to a single origin. The feature can also help when you want to avoid configuring custom domain names in Front Door and at your origin. However, when you rewrite the `Host` header, request cookies and URL redirections might break. In particular, when you use platforms like Azure App Service, features like [session affinity](../app-service/configure-common.md#configure-general-settings) and [authentication and authorization](../app-service/overview-authentication-authorization.md) might not work correctly.
+Front Door can rewrite the `Host` header of incoming requests. This feature can be helpful when you manage a set of customer-facing custom domain names that route to a single origin. This feature can also help when you want to avoid configuring custom domain names in Front Door and at your origin. However, when you rewrite the `Host` header, request cookies and URL redirections might break. In particular, when you use platforms like Azure App Service, features like [session affinity](../app-service/configure-common.md#configure-general-settings) and [authentication and authorization](../app-service/overview-authentication-authorization.md) might not work correctly.
 
 Before you rewrite the `Host` header of your requests, carefully consider whether your application is going to work correctly.
 
@@ -72,7 +78,7 @@ For more information, see [Preserve the original HTTP host name between a revers
 
 ### Enable the WAF
 
-For internet-facing applications, we recommend you enable the Front Door web application firewall (WAF) and configure it to use managed rules. When you use a WAF and Microsoft-managed rules, your application is protected from a range of attacks.
+For internet-facing applications, we recommend you enable the Front Door web application firewall (WAF) and configure it to use managed rules. When you use a WAF and Microsoft-managed rules, your application is protected from a wide range of attacks.
 
 For more information, see [Web Application Firewall (WAF) on Azure Front Door](web-application-firewall.md).
 

articles/frontdoor/front-door-caching.md

@@ -131,7 +131,7 @@ When you configure caching, you specify how the cache should handle query string
 
 * **Specify cache key query string** behavior to include or exclude specified parameters when the cache key is generated.
 
-  For example, suppose that the default cache key is `/foo/image/asset.html`, and a request is made to the URL `https://contoso.com//foo/image/asset.html?language=EN&userid=100&sessionid=200`. If there's a rules engine rule to exclude the `userid` query string parameter, then the query string cache key would be `/foo/image/asset.html?language=EN&sessionid=200`.
+  For example, suppose that the default cache key is `/foo/image/asset.html`, and a request is made to the URL `https://contoso.com/foo/image/asset.html?language=EN&userid=100&sessionid=200`. If there's a rules engine rule to exclude the `userid` query string parameter, then the query string cache key would be `/foo/image/asset.html?language=EN&sessionid=200`.
 
 Configure the query string behavior on the Front Door route.
 
@@ -206,11 +206,17 @@ In addition, Front Door attaches the `X-Cache` header to all responses. The `X-C
 - `PRIVATE_NOSTORE`: Request can't be cached because the *Cache-Control* response header is set to either *private* or *no-store*.
 - `CONFIG_NOCACHE`: Request is configured to not cache in the Front Door profile.
 
+## Logs and reports
+
 ::: zone pivot="front-door-standard-premium"
 
-## Logs and reports
+The [access log](front-door-diagnostics.md#access-log) includes the cache status for each request. Also, [reports](standard-premium/how-to-reports.md#caching-report) include information about how Azure Front Door's cache is used in your application.
+
+::: zone-end
+
+::: zone pivot="front-door-classic"
 
-The [Front Door Access Log](standard-premium/how-to-logs.md#access-log) includes the cache status for each request. Also, [reports](standard-premium/how-to-reports.md#caching) include information about how Front Door's cache is used in your application.
+The [access log](front-door-diagnostics.md#access-log) includes the cache status for each request.
 
 ::: zone-end
 
@@ -222,7 +228,7 @@ Cache behavior and duration can be configured in Rules Engine. Rules Engine cach
 
 * **When caching is disabled**, Azure Front Door doesn’t cache the response contents, irrespective of the origin response directives.
 
-* **When caching is enabled**, the cache behavior differs based on the cache behavior value applied by the Rules Engine:
+* **When caching is enabled**, the cache behavior is different depending on the cache behavior value applied by the Rules Engine:
 
    * **Honor origin**: Azure Front Door will always honor origin response header directive. If the origin directive is missing, Azure Front Door will cache contents anywhere from one to three days.  
    * **Override always**: Azure Front Door will always override with the cache duration, meaning that it will cache the contents for the cache duration ignoring the values from origin response directives. This behavior will only be applied if the response is cacheable.