Merge pull request #278331 from gbowerman/patch-3

Update concepts-azure-advisor-recommendations.md to reflect  new and …

Author: v-dirichards

articles/postgresql/flexible-server/concepts-azure-advisor-recommendations.md

@@ -4,7 +4,7 @@ description: Learn about Azure Advisor recommendations for Azure Database for Po
 author: nathan-wisner-ms
 ms.author: nathanwisner
 ms.reviewer: maghan
-ms.date: 04/27/2024
+ms.date: 06/14/2024
 ms.service: postgresql
 ms.subservice: flexible-server
 ms.topic: conceptual
@@ -17,24 +17,19 @@ ms.topic: conceptual
 Learn about how Azure Advisor is applied to Azure Database for PostgreSQL flexible server and get answers to common questions.
 ## What is Azure Advisor for PostgreSQL?
 The Azure Advisor system uses telemetry to issue performance and reliability recommendations for your Azure Database for PostgreSQL flexible server database. 
-Advisor recommendations are split among our Azure Database for PostgreSQL flexible server database offerings:
-* Azure Database for PostgreSQL single server
-* Azure Database for PostgreSQL flexible server
 
 Some recommendations are common to multiple product offerings, while other recommendations are based on product-specific optimizations.
 ## Where can I view my recommendations?
 Recommendations are available from the **Overview** navigation sidebar in the Azure portal. A preview will appear as a banner notification, and details can be viewed in the **Notifications** section located just below the resource usage graphs.
 
 :::image type="content" source="../media/concepts-azure-advisor-recommendations/advisor-example.png" alt-text="Screenshot of the Azure portal showing an Azure Advisor recommendation.":::
 ## Recommendation types
-Azure Database for PostgreSQL flexible server prioritizes the following types of recommendations:
-* **Performance**: To improve the speed of your Azure Database for PostgreSQL flexible server instance. This includes CPU usage, memory pressure, connection pooling, disk utilization, and product-specific server parameters. For more information, see [Advisor Performance recommendations](../../advisor/advisor-reference-performance-recommendations.md).
-* **Reliability**: To ensure and improve the continuity of your business-critical databases. This includes storage limits, and connection limits. For more information, see [Advisor Reliability recommendations](../../advisor/advisor-reference-reliability-recommendations.md).
-* **Cost**: To optimize and reduce your overall Azure spending. This includes server right-sizing recommendations. For more information, see [Advisor Cost recommendations](../../advisor/advisor-reference-cost-recommendations.md).
+Azure Database for PostgreSQL flexible server prioritizes the following type of recommendation:
+* **Performance**: To enhance the performance of your Azure Database for PostgreSQL flexible server instance, the recommendations proactively identify servers experiencing scenarios which can impact performance. These scenarios include high CPU utilization, frequent checkpoint initiations, performance-impacting log parameter settings, inactive logical replication slots, long-running transactions, orphaned prepared transactions, a high bloat ratio, and transaction wraparound risks. For more information, see [Advisor Performance recommendations](../../advisor/advisor-performance-recommendations.md).
 
 ## Understanding your recommendations
-* **Daily schedule**: For Azure Database for PostgreSQL flexible server databases, we check server telemetry and issue recommendations on a twice a day schedule. If you make a change to your server configuration, existing recommendations will remain visible until we re-examine telemetry at either 7PM or 7AM according to PST. 
-* **Performance history**: Some of our recommendations are based on performance history. These recommendations will only appear after a server has been operating with the same configuration for 7 days. This allows us to detect patterns of heavy usage (e.g. high CPU activity or high connection volume) over a sustained time period. If you provision a new server or change to a new vCore configuration, these recommendations are paused temporarily. This prevents legacy telemetry from triggering recommendations on a newly reconfigured server. However, this also means that performance history-based recommendations may not be identified immediately.
+* **Daily schedule**: For Azure Database for PostgreSQL flexible server databases, we review server telemetry and issue recommendations daily. If you make changes to your server configuration, the existing recommendations will remain visible until we re-evaluate the recommendation the following day, approximately 24 hours later.
+* **Performance history**: Some of our recommendations are based on performance history. These recommendations will only appear after a server has been operating with the same configuration for 7 days. This allows us to detect patterns of heavy usage (e.g., high CPU activity or high connection volume) over a sustained period. If you provisioned a new server or change to a new vCore configuration, these recommendations are paused temporarily. This prevents legacy telemetry from triggering recommendations on a newly reconfigured server. However, this also means that performance history-based recommendations may not be identified immediately.
 
 ## Next steps
 For more information, see [Azure Advisor Overview](../../advisor/advisor-overview.md).