renames

Author: v-thepet

articles/postgresql/.openpublishing.redirection.postgresql.json

@@ -1515,6 +1515,46 @@
         "redirect_url": "/azure/postgresql/migrate/best-practices-seamless-migration-single-to-flexible",
         "redirect_document_id": false
     },    
+    {
+        "source_path_from_root": "/articles/postgresql/flexible-server/howto-alert-on-metrics.md",
+        "redirect_url": "/azure/postgresql/flexible-server/how-to-alert-on-metrics",
+        "redirect_document_id": true
+    },    
+    {
+        "source_path_from_root": "/articles/postgresql/flexible-server/howto-configure-and-access-logs.md",
+        "redirect_url": "/azure/postgresql/flexible-server/how-to-configure-and-access-logs",
+        "redirect_document_id": true
+    },    
+    {
+        "source_path_from_root": "/articles/postgresql/flexible-server/howto-configure-server-parameters-using-cli.md",
+        "redirect_url": "/azure/postgresql/flexible-server/how-to-configure-server-parameters-using-cli",
+        "redirect_document_id": true
+    },    
+    {
+        "source_path_from_root": "/articles/postgresql/flexible-server/howto-configure-server-parameters-using-portal.md",
+        "redirect_url": "/azure/postgresql/flexible-server/how-to-configure-server-parameters-using-portal",
+        "redirect_document_id": true
+    },    
+    {
+        "source_path_from_root": "/articles/postgresql/flexible-server/howto-connect-to-data-factory-private-endpoint.md",
+        "redirect_url": "/azure/postgresql/flexible-server/how-to-connect-to-data-factory-private-endpoint",
+        "redirect_document_id": true
+    },    
+    {
+        "source_path_from_root": "/articles/postgresql/flexible-server/howto-optimize-performance-pgvector.md",
+        "redirect_url": "/azure/postgresql/flexible-server/how-to-optimize-performance-pgvector",
+        "redirect_document_id": true
+    },    
+    {
+        "source_path_from_root": "/articles/postgresql/flexible-server/howto-restore-different-subscription-resource-group-api.md",
+        "redirect_url": "/azure/postgresql/flexible-server/how-to-restore-different-subscription-resource-group-api",
+        "redirect_document_id": true
+    },    
+    {
+        "source_path_from_root": "/articles/postgresql/flexible-server/concept-reserved-pricing.md",
+        "redirect_url": "/azure/postgresql/flexible-server/concepts-reserved-pricing",
+        "redirect_document_id": true
+    },    
     {
         "source_path_from_root": "/articles/postgresql/single-server/overview.md",
         "redirect_url": "/azure/postgresql/flexible-server/service-overview",

articles/postgresql/TOC.yml

@@ -44,7 +44,7 @@
   - name: Major version upgrades
     href: single-server/how-to-upgrade-using-dump-and-restore.md
   - name: Prepay for reserved capacity
-    href: flexible-server/concept-reserved-pricing.md
+    href: flexible-server/concepts-reserved-pricing.md
   - name: Request quota increase
     href: flexible-server/how-to-request-quota-increase.md
   - name: Known issues & limitations
@@ -107,7 +107,7 @@
     - name: Scaling resources
       href: flexible-server/concepts-scaling-resources.md
     - name: Prepay for reserved capacity
-      href: flexible-server/concept-reserved-pricing.md
+      href: flexible-server/concepts-reserved-pricing.md
     - name: Networking
       items:
       - name: Networking with public access (allowed IP addresses)
@@ -300,7 +300,7 @@
         - name: Azure portal
           href: flexible-server/how-to-restore-to-different-subscription-or-resource-group.md
         - name: Azure REST API
-          href: flexible-server/howto-restore-different-subscription-resource-group-api.md 
+          href: flexible-server/how-to-restore-different-subscription-resource-group-api.md 
       - name: Restart a server
         items:
         - name: Azure portal
@@ -352,7 +352,7 @@
         - name: Azure portal
           href: flexible-server/how-to-manage-virtual-network-private-endpoint-portal.md
         - name: Connect to managed data factory via Private Endpoint
-          href: flexible-server/howto-connect-to-data-factory-private-endpoint.md
+          href: flexible-server/how-to-connect-to-data-factory-private-endpoint.md
       - name: Public access (allowed IP addresses)
         items:
         - name: Azure portal
@@ -362,10 +362,10 @@
     - name: Configure server parameters
       items:
       - name: Azure portal
-        href: flexible-server/howto-configure-server-parameters-using-portal.md
+        href: flexible-server/how-to-configure-server-parameters-using-portal.md
         displayName: application development, server parameters
       - name: Azure CLI
-        href: flexible-server/howto-configure-server-parameters-using-cli.md
+        href: flexible-server/how-to-configure-server-parameters-using-cli.md
         displayName: application development, server parameters
     - name: Enable authentication
       items:
@@ -395,9 +395,9 @@
     - name: Monitor
       items:
       - name: Create alerts on metrics using portal
-        href: flexible-server/howto-alert-on-metrics.md
+        href: flexible-server/how-to-alert-on-metrics.md
       - name: Configure and access logs
-        href: flexible-server/howto-configure-and-access-logs.md
+        href: flexible-server/how-to-configure-and-access-logs.md
     - name: Intelligent performance
       items:
         - name: Intelligent tuning
@@ -428,7 +428,7 @@
         - name: Basics of pgvector
           href: flexible-server/how-to-use-pgvector.md
         - name: Optimize performance when using pgvector
-          href: flexible-server/howto-optimize-performance-pgvector.md
+          href: flexible-server/how-to-optimize-performance-pgvector.md
     - name: pg_azure_storage
       href: flexible-server/reference-pg-azure-storage.md 
 - name: Azure Database for PostgreSQL - Single Server

articles/postgresql/flexible-server/concepts-audit.md

@@ -43,7 +43,7 @@ az postgres flexible-server parameter set --resource-group <your resource group>
    ```
 
 
-To install pgAudit, you need to include it in the server's shared preload libraries. A change to Postgres's `shared_preload_libraries` parameter requires a server restart to take effect. You can change parameters using the [Azure portal](howto-configure-server-parameters-using-portal.md), [Azure CLI](howto-configure-server-parameters-using-cli.md), or [REST API](/rest/api/postgresql/singleserver/configurations/createorupdate).
+To install pgAudit, you need to include it in the server's shared preload libraries. A change to Postgres's `shared_preload_libraries` parameter requires a server restart to take effect. You can change parameters using the [Azure portal](how-to-configure-server-parameters-using-portal.md), [Azure CLI](how-to-configure-server-parameters-using-cli.md), or [REST API](/rest/api/postgresql/singleserver/configurations/createorupdate).
 
 Using the [Azure portal](https://portal.azure.com):
 
@@ -123,4 +123,4 @@ AzureDiagnostics
 
 ## Next steps
 - [Learn about logging in Azure Database for PostgreSQL - Flexible Server](concepts-logging.md)
-- [Learn how to setup logging in Azure Database for PostgreSQL - Flexible Server and how to access logs](howto-configure-and-access-logs.md)
+- [Learn how to setup logging in Azure Database for PostgreSQL - Flexible Server and how to access logs](how-to-configure-and-access-logs.md)

articles/postgresql/flexible-server/concepts-business-continuity.md

@@ -103,8 +103,8 @@ Below are some unplanned failure scenarios and the recovery process.
 ### Configure your database after recovery from regional failure
 
 * If you are using geo-restore or geo-replica to recover from an outage, you must make sure that the connectivity to the new server is properly configured so that the normal application function can be resumed. You can follow the [Post-restore tasks](concepts-backup-restore.md#geo-redundant-backup-and-restore).
-* If you've previously set up a diagnostic setting on the original server, make sure to do the same on the target server if necessary as explained in [Configure and Access Logs in Azure Database for PostgreSQL - Flexible Server](howto-configure-and-access-logs.md).
-* Setup telemetry alerts, you need to make sure your existing alert rule settings are updated to map to the new server. For more information about alert rules, see [Use the Azure portal to set up alerts on metrics for Azure Database for PostgreSQL - Flexible Server](howto-alert-on-metrics.md).
+* If you've previously set up a diagnostic setting on the original server, make sure to do the same on the target server if necessary as explained in [Configure and Access Logs in Azure Database for PostgreSQL - Flexible Server](how-to-configure-and-access-logs.md).
+* Setup telemetry alerts, you need to make sure your existing alert rule settings are updated to map to the new server. For more information about alert rules, see [Use the Azure portal to set up alerts on metrics for Azure Database for PostgreSQL - Flexible Server](how-to-alert-on-metrics.md).
 
 
 > [!IMPORTANT]

articles/postgresql/flexible-server/concepts-compute-storage.md

@@ -205,7 +205,7 @@ When you reach the storage limit, the server starts returning errors and prevent
 
 To avoid this situation, the server is automatically switched to read-only mode when the storage usage reaches 95 percent or when the available capacity is less than 5 GiB.
 
-We recommend that you actively monitor the disk space that's in use and increase the disk size before you run out of storage. You can set up an alert to notify you when your server storage is approaching an out-of-disk state. For more information, see [Use the Azure portal to set up alerts on metrics for Azure Database for PostgreSQL - Flexible Server](howto-alert-on-metrics.md).
+We recommend that you actively monitor the disk space that's in use and increase the disk size before you run out of storage. You can set up an alert to notify you when your server storage is approaching an out-of-disk state. For more information, see [Use the Azure portal to set up alerts on metrics for Azure Database for PostgreSQL - Flexible Server](how-to-alert-on-metrics.md).
 
 ### Storage autogrow
 

articles/postgresql/flexible-server/concepts-extensions.md

@@ -298,7 +298,7 @@ TimescaleDB is a time-series database that is packaged as an extension for Postg
 [Learn more about TimescaleDB](https://docs.timescale.com/timescaledb/latest/), a registered trademark of Timescale, Inc.. Azure Database for PostgreSQL provides the TimescaleDB [Apache-2 edition](https://www.timescale.com/legal/licenses).
 ### Install TimescaleDB
 
-To install TimescaleDB, in addition, to allow listing it, as shown [above](#how-to-use-postgresql-extensions), you need to include it in the server's shared preload libraries. A change to Postgres's `shared_preload_libraries` parameter requires a **server restart** to take effect. You can change parameters using the [Azure portal](howto-configure-server-parameters-using-portal.md) or the [Azure CLI](howto-configure-server-parameters-using-cli.md).
+To install TimescaleDB, in addition, to allow listing it, as shown [above](#how-to-use-postgresql-extensions), you need to include it in the server's shared preload libraries. A change to Postgres's `shared_preload_libraries` parameter requires a **server restart** to take effect. You can change parameters using the [Azure portal](how-to-configure-server-parameters-using-portal.md) or the [Azure CLI](how-to-configure-server-parameters-using-cli.md).
 
 Using the [Azure portal](https://portal.azure.com/):
 
@@ -385,7 +385,7 @@ Example:
 The above example causes the planner to use the results of a `seq scan` on the table a to be combined with table b as a `hash join`.
 
 
-To install pg_hint_plan, in addition, to allow listing it, as shown [above](#how-to-use-postgresql-extensions), you need to include it in the server's shared preload libraries. A change to Postgres's `shared_preload_libraries` parameter requires a **server restart** to take effect. You can change parameters using the [Azure portal](howto-configure-server-parameters-using-portal.md) or the [Azure CLI](howto-configure-server-parameters-using-cli.md).
+To install pg_hint_plan, in addition, to allow listing it, as shown [above](#how-to-use-postgresql-extensions), you need to include it in the server's shared preload libraries. A change to Postgres's `shared_preload_libraries` parameter requires a **server restart** to take effect. You can change parameters using the [Azure portal](how-to-configure-server-parameters-using-portal.md) or the [Azure CLI](how-to-configure-server-parameters-using-cli.md).
 
 Using the [Azure portal](https://portal.azure.com/):
 

articles/postgresql/flexible-server/concepts-logging.md

@@ -21,7 +21,7 @@ Audit logging is made available through a Postgres extension, `pgaudit`. To lear
 
 You can configure Postgres standard logging on your server using the logging server parameters. To learn more about Postgres log parameters, visit the [When To Log](https://www.postgresql.org/docs/current/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHEN) and [What To Log](https://www.postgresql.org/docs/current/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHAT) sections of the Postgres documentation. Most, but not all, Postgres logging parameters are available to configure in Azure Database for PostgreSQL.
 
-To learn how to configure parameters in Azure Database for PostgreSQL, see the [portal documentation](howto-configure-server-parameters-using-portal.md) or the [CLI documentation](howto-configure-server-parameters-using-cli.md).
+To learn how to configure parameters in Azure Database for PostgreSQL, see the [portal documentation](how-to-configure-server-parameters-using-portal.md) or the [CLI documentation](how-to-configure-server-parameters-using-cli.md).
 
 > [!NOTE]
 > Configuring a high volume of logs, for example statement logging, can add significant performance overhead. 
@@ -61,6 +61,6 @@ The following table describes the fields for the **PostgreSQLLogs** type. Depend
 
 ## Next steps
 
-- Learn more about how to [Configure and Access Logs](howto-configure-and-access-logs.md).
+- Learn more about how to [Configure and Access Logs](how-to-configure-and-access-logs.md).
 - Learn more about [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/).
 - Learn more about [audit logs](concepts-audit.md)

articles/postgresql/flexible-server/concepts-logical.md

@@ -326,7 +326,7 @@ The 'active' column in the `pg_replication_slots` view indicates whether there's
 ```sql
 SELECT * FROM pg_replication_slots;
 ```
-[Set alerts](howto-alert-on-metrics.md) on the **Maximum Used Transaction IDs** and **Storage Used** flexible server metrics to notify you when the values increase past normal thresholds.
+[Set alerts](how-to-alert-on-metrics.md) on the **Maximum Used Transaction IDs** and **Storage Used** flexible server metrics to notify you when the values increase past normal thresholds.
 
 
 ## Limitations

articles/postgresql/flexible-server/concepts-monitoring.md

@@ -250,6 +250,6 @@ In addition to the metrics, you can use Azure Database for PostgreSQL to configu
 
 ## Next steps
 
-- Learn more about how to [configure and access logs](howto-configure-and-access-logs.md).
+- Learn more about how to [configure and access logs](how-to-configure-and-access-logs.md).
 - Learn more about [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/).
 - Learn more about [audit logs](concepts-audit.md).

articles/postgresql/flexible-server/concepts-query-performance-insight.md

@@ -34,7 +34,7 @@ Query Performance Insight provides intelligent query analysis for Azure Postgres
 > [!NOTE]
 > **Query Store Wait Sampling** is currently **disabled**. Query Performance Insight depends on Query Store wait sampling data. You need to enable it by setting the dynamic server parameter `pgms_wait_sampling.query_capture_mode` to **ALL**.
 
-3. **[Log analytics workspace](howto-configure-and-access-logs.md)** is configured for storing 3 log categories including - PostgreSQL Sessions logs, PostgreSQL Query Store and Runtime and PostgreSQL Query Store Wait Statistics. To configure log analytics, refer [Log analytics workspace](howto-configure-and-access-logs.md#configure-diagnostic-settings).
+3. **[Log analytics workspace](how-to-configure-and-access-logs.md)** is configured for storing 3 log categories including - PostgreSQL Sessions logs, PostgreSQL Query Store and Runtime and PostgreSQL Query Store Wait Statistics. To configure log analytics, refer [Log analytics workspace](how-to-configure-and-access-logs.md#configure-diagnostic-settings).
 
 > [!NOTE]
 > The **Query Store data is not being transmitted to the log analytics workspace**. The PostgreSQL logs (Sessions data / Query Store Runtime / Query Store Wait Statistics) is not being sent to the log analytics workspace, which is necessary to use Query Performance Insight. To configure the logging settings for category PostgreSQL sessions and send the data to a log analytics workspace.