new guides

Author: AlicjaKucharczyk

articles/postgresql/flexible-server/concepts-troubleshooting-guides.md

@@ -24,6 +24,8 @@ including:
 * high usage of temporary files, 
 * autovacuum monitoring and blockers. 
 
+:::image type="content" source="./media/concepts-troubleshooting-guides/overview-troubleshooting-guides.jpg" alt-text="Troubleshooting Guides":::
+
 Each guide is packed with multiple charts, guidelines, recommendations tailored to the specific problem you may encounter, which can help expedite the troubleshooting process.
 The troubleshooting guides are directly integrated into the Azure portal and your Azure Database for PostgreSQL - Flexible Server, making them convenient and easy to use. 
 

articles/postgresql/flexible-server/how-to-troubleshooting-guides.md

@@ -21,7 +21,7 @@ In this article, you'll learn how to use Troubleshooting guides for Azure Databa
 ## Prerequisites
 
 To effectively troubleshoot specific issue, you need to make sure you have all the necessary data in place. 
-Each troubleshooting guide requires a specific set of data, which is sourced from three separate features: Diagnostic settings, Query Store, and Enhanced Metrics.
+Each troubleshooting guide requires a specific set of data, which is sourced from three separate features: [Diagnostic settings](howto-configure-and-access-logs.md), [Query Store](concepts-query-store.md), and [Enhanced Metrics](concepts-monitoring.md#enabling-enhanced-metrics).
 All troubleshooting guides require logs to be sent to the Log Analytics workspace, but the specific category of logs to be captured may vary depending on the particular guide. 
 
 Please follow the steps described in the [Configure and Access Logs in Azure Database for PostgreSQL - Flexible Server](howto-configure-and-access-logs.md) article to configure diagnostic settings and send the logs to the Log Analytics workspace.