diff --git a/blog-service/2024-11-28-apps.md b/blog-service/2024-11-28-apps.md
index 2c1c6396a3..83f734fffb 100644
--- a/blog-service/2024-11-28-apps.md
+++ b/blog-service/2024-11-28-apps.md
@@ -19,6 +19,8 @@ We’re excited to announce the release of the new Azure Database for PostgreSQL
[Learn more](/docs/integrations/microsoft-azure/azure-database-for-postgresql/).
- **Azure Cosmos DB**. Azure Cosmos DB is a fully managed NoSQL and relational database for modern app development offering single-digit millisecond response times, automatic and instant scalability, along with guaranteed speed at any scale. This integration helps in monitoring the overall performance, failures, capacity, and operational health of all your Azure Cosmos DB resources.
[Learn more](/docs/integrations/microsoft-azure/azure-cosmos-db/).
+- **Azure Cosmos DB for PostgreSQL**. Azure Cosmos DB for PostgreSQL is a managed service for PostgreSQL powered by the Citus open source extension which enables you to build highly scalable relational apps. This integration helps in identifying configurations errors, analyzing executed statements, and monitoring resource usage of individual nodes in a cluster.
+[Learn more](/docs/integrations/microsoft-azure/azure-cosmos-db-for-postgresql/).
- **Azure App Service Environment**. An Azure App Service Environment is an Azure App Service feature that provides a fully isolated and dedicated environment for running App Service apps securely at high scale. This integration helps in monitoring your environments operational events such as upgrades, scaling, and suspensions. [Learn more](/docs/integrations/microsoft-azure/azure-app-service-environment).
### Enhancements
diff --git a/docs/integrations/microsoft-azure/azure-cosmos-db-for-postgresql.md b/docs/integrations/microsoft-azure/azure-cosmos-db-for-postgresql.md
index 0c3ade7bf3..844231740c 100644
--- a/docs/integrations/microsoft-azure/azure-cosmos-db-for-postgresql.md
+++ b/docs/integrations/microsoft-azure/azure-cosmos-db-for-postgresql.md
@@ -15,7 +15,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
For Azure Cosmos DB for PostgreSQL, you can collect the following logs and metrics:
* **PostgreSQL Server Logs**. These logs are available for every node of a cluster and can be used to identify, troubleshoot, and repair configuration errors and suboptimal performance.
-* **Audit Logs**. Audit logging of database activities is available through [pgAudit](https://www.pgaudit.org/) extension. By default, pgAudit log statements are emitted along with your regular log statements by using Postgres's standard logging facility. To learn more about the audit log format, refer to the [pgAudit documentation](https://github.com/pgaudit/pgaudit/blob/master/README.md#format).
+* **Activity logs**. Provides insight into any subscription-level or management group level events that have occurred in Azure. To learn more, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/activity-log-schema).
* **Metrics**. These metrics are available for every node of a cluster, and in aggregate across the nodes. For more information on supported metrics, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/cosmos-db/postgresql/concepts-monitoring#list-of-metrics).
## Setup
@@ -29,32 +29,262 @@ You must explicitly enable diagnostic settings for each Azure Cosmos DB for Post
When you configure the event hubs source or HTTP source, plan your source category to ease the querying process. A hierarchical approach allows you to make use of wildcards. For example: `Azure/CosmosDBforPostgreSQL/Logs`, `Azure/CosmosDBforPostgreSQL/Metrics`.
+
+### Configure field in field schema
+
+1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Logs > Fields**.
[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Logs** select **Fields**. You can also click the **Go To...** menu at the top of the screen and select **Fields**.
+2. Search for the following fields:
+ - `tenant_name`. This field is tagged at the collector level. You can get the tenant name using the instructions in the [Microsoft Documentation](https://learn.microsoft.com/en-us/azure/active-directory-b2c/tenant-management-read-tenant-name#get-your-tenant-name).
+ - `location`. The region to which the resource name belongs to.
+ - `subscription_id`. ID associated with a subscription where the resource is present.
+ - `resource_group`. The resource group name where the Azure resource is present.
+ - `provider_name`. Azure resource provider name (for example, Microsoft.Network).
+ - `resource_type`. Azure resource type (for example, storage accounts).
+ - `resource_name`. The name of the resource (for example, storage account name).
+ - `service_type`. Type of the service that can be accessed with a Azure resource.
+ - `service_name`. Services that can be accessed with an Azure resource (for example, Azure SQL databases in Azure SQL Server).
+3. Create the fields if they are not present. Refer to [Manage fields](/docs/manage/fields/#manage-fields).
+
+### Configure Field Extraction Rules
+
+Create the following Field Extraction Rules (FER) for Azure Storage by following the instructions in the [Create a Field Extraction Rule](/docs/manage/field-extractions/create-field-extraction-rule/). Create the below rules if they are not present.
+
+#### Azure location extraction FER
+
+ ```sql
+ Rule Name: AzureLocationExtractionFER
+ Applied at: Ingest Time
+ Scope (Specific Data): tenant_name=*
+ ```
+
+ ```sql title="Parse Expression"
+ json "location", "properties.resourceLocation", "properties.region" as location, resourceLocation, service_region nodrop
+ | replace(toLowerCase(resourceLocation), " ", "") as resourceLocation
+ | if (!isBlank(resourceLocation), resourceLocation, location) as location
+ | if (!isBlank(service_region), service_region, location) as location
+ | if (isBlank(location), "global", location) as location
+ | fields location
+ ```
+
+#### Resource ID extraction FER
+
+ ```sql
+ Rule Name: AzureResourceIdExtractionFER
+ Applied at: Ingest Time
+ Scope (Specific Data): tenant_name=*
+ ```
+
+ ```sql title="Parse Expression"
+ json "resourceId", "ResourceId" as resourceId1, resourceId2 nodrop
+ | if (isBlank(resourceId1), resourceId2, resourceId1) as resourceId
+ | toUpperCase(resourceId) as resourceId
+ | parse regex field=resourceId "/SUBSCRIPTIONS/(?[^/]+)" nodrop
+ | parse field=resourceId "/RESOURCEGROUPS/*/" as resource_group nodrop
+ | parse regex field=resourceId "/PROVIDERS/(?[^/]+)" nodrop
+ | parse regex field=resourceId "/PROVIDERS/[^/]+(?:/LOCATIONS/[^/]+)?/(?[^/]+)/(?.+)" nodrop
+ | parse regex field=resource_name "(?[^/]+)(?:/PROVIDERS/[^/]+)?/(?[^/]+)/?(?.+)" nodrop
+ | if (isBlank(parent_resource_name), resource_name, parent_resource_name) as resource_name
+ | fields subscription_id, location, provider_name, resource_group, resource_type, resource_name, service_type, service_name
+ ```
+
+### Configure metric rules
+
+Create the following metrics rules by following the instructions in [Create a metrics rule](/docs/metrics/metric-rules-editor/#create-a-metrics-rule). Create the below rules if they are not present.
+
+#### Azure observability metadata extraction flexible PostgreSQL server level
+
+```sql
+Rule Name: AzureObservabilityMetadataExtractionAzureCosmosDBForPostgreSQLLevel
+```
+
+```sql title="Metric match expression"
+resourceId=/SUBSCRIPTIONS/*/RESOURCEGROUPS/*/PROVIDERS/MICROSOFT.DBFORPOSTGRESQL/FLEXIBLESERVERS/* tenant_name=*
+```
+
+| Fields extracted | Metric rule |
+|:------------------|:-------------------------|
+| subscription_id | $resourceId._1 |
+| resource_group | $resourceId._2 |
+| provider_name | MICROSOFT.DBFORPOSTGRESQL|
+| resource_type | SERVERGROUPSV2 |
+| resource_name | $resourceId._3 |
+
+
### Configure metrics collection
In this section, you will configure a pipeline for shipping metrics from Azure Monitor to an Event Hub, on to an Azure Function, and finally to an HTTP Source on a hosted collector in Sumo Logic.
-1. [Configure an HTTP Source](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-1-configure-an-http-source).
+1. Create hosted collector and tag `tenant_name` field.
})
+2. [Configure an HTTP Source](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-1-configure-an-http-source).
2. [Configure and deploy the ARM Template](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-2-configure-azure-resources-using-arm-template).
-3. [Export metrics to Event Hub](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-3-export-metrics-for-a-particular-resource-to-event-hub). Perform below steps for each Azure Cosmos DB for PostgreSQL cluster that you want to monitor.
- * Choose `Stream to an event hub` as destination.
- * Select `AllMetrics`.
- * Use the Event hub namespace created by the ARM template in Step 2 above. You can create a new Event hub or use the one created by ARM template. You can use the default policy `RootManageSharedAccessKey` as the policy name.
+3. [Export metrics to Event Hub](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-3-export-metrics-for-a-particular-resource-to-event-hub). Perform below steps for each Flexible PostgreSQL Server resource that you want to monitor.
+ 1. Choose `Stream to an event hub` as destination.
+ 1. Select `AllMetrics`.
+ 1. Use the Event hub namespace created by the ARM template in Step 2 above. You can create a new Event hub or use the one created by ARM template. You can use the default policy `RootManageSharedAccessKey` as the policy name.
})
+1. Tag the location field in the source with right location value.
})
### Configure logs collection
In this section, you will configure a pipeline for shipping diagnostic logs from Azure Monitor to an Event Hub.
-1. To enable audit logs perform below steps:
- * [Install the pgAudit extension](https://learn.microsoft.com/en-us/azure/cosmos-db/postgresql/how-to-enable-audit#installing-pgaudit).
- * [Configure audit logging](https://learn.microsoft.com/en-us/azure/cosmos-db/postgresql/how-to-enable-audit#pgaudit-settings).
-2. To set up the Azure Event Hubs source in Sumo Logic, refer to [Azure Event Hubs Source for Logs](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source/).
-3. To create the Diagnostic settings in Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/cosmos-db/postgresql/howto-logging#capture-logs). Perform below steps for each Azure Cosmos DB for PostgreSQL cluster that you want to monitor.
- * Choose `Stream to an event hub` as the destination.
- * Select `allLogs`.
- * Use the Event hub namespace and Event hub name configured in previous step in destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.
+1. To set up the Azure Event Hubs source in Sumo Logic, refer to the [Azure Event Hubs Source for Logs](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source/).
+2. To create the diagnostic settings in Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-gb/azure/data-factory/monitor-configure-diagnostics). Perform the steps below for each Azure Redis cache account that you want to monitor.
+ 1. Choose **Stream to an event hub** as the destination.
+ 1. Select `allLogs`.
+ 1. Use the Event Hub namespace and Event Hub name configured in the previous step in the destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.
})
+3. Set server parameters as below:
+ - `log_statement`. Select **DDL**.
+ - `log_lock_waits`. Set to **ON**. If required, you can also configure `deadlock_timeout`.
+ - `log_connections`. Set to **ON**.
+ - `log_disconnections`. Set to **ON**.
+ - `log_duration`. Set to **ON**. If required, you can also configure `log_min_duration_statement`.
+ - `log_hostname`. Set to **ON**.
+ - `log_min_error_statement`. Set to **INFO**.
+ - `log_min_messages`. Set to **INFO**.
+ - `log_line_prefix`. Set to `%m [%p][%v] : %q[app=%a]`.
+
+4. Tag the location field in the source with right location value.
+
+#### Activity Logs
+
+To collect activity logs, follow the instructions [here](/docs/integrations/microsoft-azure/audit). Skip this step if you are already collecting activity logs for a subscription.
+
+:::note
+Since this source contains logs from multiple regions, ensure that you do not tag this source with the location tag.
+:::
+
+## Installing the Azure Cosmos DB for PostgreSQL app
+
+Now that you have set up data collection, install the Azure Database for PostgreSQL Sumo Logic app to use the pre-configured dashboards that provide visibility into your environment for real-time analysis of overall usage.
+
+import AppInstallNoDataSourceV2 from '../../reuse/apps/app-install-index-apps-v2.md';
+
+
+
+## Viewing the Azure Cosmos DB for PostgreSQL dashboards
+
+import ViewDashboards from '../../reuse/apps/view-dashboards.md';
+
+
+
+### Overview
+
+The **Azure Cosmos DB for PostgreSQL - Overview** dashboard provides details about replication lag, active connections and query duration distribution across clusters and servers.
+
+Use this dashboard to:
+* Track replication lag across replica clusters.
+* Analyse query execution duration distribution and common errors across all servers.
+* Identify clusters with max cpu usage, memory usage, and storage usage.
+
+})
+
+### Network
+
+The **Azure Cosmos DB for PostgreSQL - Network** dashboard provides insights on active connections, failed Ccnnections, and network activity including ingress and egress bytes.
+
+Use this dashboard to:
+
+* Quickly identify connection errors across clusters.
+* Monitor active connections, ingress, and egress trends across clusters.
+* Identify abnormally long sessions.
+
+
+})
+
+### Errors
+
+The **Azure Cosmos DB for PostgreSQL - Errors** dashboard provides insight into server error logs by specifically monitoring errors and database shutdown/start events.
+
+Use this dashboard to:
+
+* Quickly identify top errors across clusters and servers.
+* Monitor error trends and distribution across clusters and servers.
+* Identify unexpected database shutdown or start activity.
+
+})
+
+
+### Security
+
+The **Azure Cosmos DB for PostgreSQL - Security** dashboard provides insight into locations of incoming connections, failed authentications, and top database errors and warnings.
+
+Use this dashboard to:
+
+* Monitor incoming connections, failed authorization requests, and failed authentication requests.
+* Track the user performing failed authentication attempts across servers.
+
+})
+
+### Storage
+
+The **Azure Cosmos DB for PostgreSQL - Storage** dashboard provides details about data usage, document count, and physical partition size by database.
+
+Use this dashboard to:
+* Monitor the storage utilisation to decide on scaling up storage or scaling out the nodes if this metric exceeds 85 percent consistently.
+* Track total storage used across the clusters.
+
+})
+
+### Performance
+
+The **Azure Cosmos DB for PostgreSQL - Performance** dashboard provides insights into the performance of your Azure Cosmos DB for PostgreSQL databases. This includes metrics on query duration, server side latency, and failed queries.
+
+Use this dashboard to:
+* Track clusters approaching the maximum IOPS capacity, to decide on adding worker nodes.
+* Identify clusters using a high percentage of the clusters available memory to decide on scaling up the compute if this metric consistently exceeds 90 percent.
+* Monitor the CPU usage to decide on scaling up the compute if this metric exceeds 95 percent consistently.
+
+})
+
+### Queries
+
+The **Azure Cosmos DB for PostgreSQL - Queries** dashboard provides insights into the queries executed in your Azure Cosmos DB for PostgreSQL databases.
+
+Use this dashboard to:
+* Analyze query execution duration distribution across servers.
+* Identify query statements with errors.
+* Monitor spike in query duration.
+
+})
+
+### Health
+
+The **Azure Cosmos DB for PostgreSQL - Health** dashboard provides information of any service health incidents or resource health events associated with Azure Cosmos DB for PostgreSQL accounts in your azure account.
+
+Use this dashboard to:
+* View recent resource and service health incidents.
+* View distribution of service and resource health by incident type.
+* Monitor service availability.
+
+})
+
+### Administrative Operations
+
+The **Azure Cosmos DB for PostgreSQL - Administrative Operations** dashboard provides details on users performing admin operations.
+
+Use this dashboard to:
+* Identify top users performing administrative operations.
+* View top 10 operations that caused the most errors.
+* View recent diagnostic, network, and replication settings updates operations.
+
+})
+
+
+## Upgrade/Downgrade the Azure Cosmos DB for PostgreSQL app (Optional)
+
+import AppUpdate from '../../reuse/apps/app-update.md';
+
+
+
+## Uninstalling the Azure Cosmos DB for PostgreSQL app (Optional)
+
+import AppUninstall from '../../reuse/apps/app-uninstall.md';
+
+
## Troubleshooting
### HTTP Logs and Metrics Source used by Azure Functions
To troubleshoot metrics collection, follow the instructions in [Collect Metrics from Azure Monitor > Troubleshooting metrics collection](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#troubleshooting-metrics-collection).
+
diff --git a/docs/integrations/microsoft-azure/azure-database-for-postgresql.md b/docs/integrations/microsoft-azure/azure-database-for-postgresql.md
index dc8483f866..9690df96c9 100644
--- a/docs/integrations/microsoft-azure/azure-database-for-postgresql.md
+++ b/docs/integrations/microsoft-azure/azure-database-for-postgresql.md
@@ -17,7 +17,7 @@ The below instructions applies to Azure Database for PostgreSQL with Flexible Se
For Azure Database for PostgreSQL, you can collect the following logs and metrics:
* **PostgreSQL Logs**. These logs can be used to identify, troubleshoot, and repair configuration errors and suboptimal performance. To learn more about the log format, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-logging#log-format).
-* **Audit Logs**. Audit logging of database activities is available through [pgAudit](https://www.pgaudit.org/) extension. By default, pgAudit log statements are emitted along with your regular log statements by using Postgres's standard logging facility. To learn more about the audit log format, refer to the [pgAudit documentation](https://github.com/pgaudit/pgaudit/blob/master/README.md#format).
+* **Activity logs**. Provides insight into any subscription-level or management group level events that have occurred in the Azure. To learn more, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/activity-log-schema).
* **Metrics**. These metrics are available for a flexible server instance of Azure Database for PostgreSQL. For more information on supported metrics and instructions for enabling them, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-monitoring#metrics).
## Setup
@@ -139,15 +139,15 @@ In this section, you will configure a pipeline for shipping diagnostic logs from
1. Use the Event Hub namespace and Event Hub name configured in the previous step in the destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.
})
3. Set server parameters as below:
- `wal_level`. Set to **logical**.
- - `cron.log_statement`. Set to **ON**.
- `log_statement_stats`. Set to **ON**.
- - `pgaudit.log_statement_once`. Set to **ON**.
- `log_statement`. Select **ALL**.
- - `log_lock_waits`. Set to **ON**.
+ - `log_lock_waits`. Set to **ON**. Set `deadlock_timeout`
- `log_recovery_conflict_waits`. Set to **ON**.
+
+
4. Tag the location field in the source with right location value.
-#### Activity Logs
+#### Activity logs
To collect activity logs, follow the instructions [here](/docs/integrations/microsoft-azure/audit). Skip this step if you are already collecting activity logs for a subscription.
diff --git a/static/img/send-data/export-logs-diagnostic-settings-cosmosdbforpostgresql.png b/static/img/send-data/export-logs-diagnostic-settings-cosmosdbforpostgresql.png
new file mode 100644
index 0000000000..d9ba0db395
Binary files /dev/null and b/static/img/send-data/export-logs-diagnostic-settings-cosmosdbforpostgresql.png differ
diff --git a/static/img/send-data/export-metrics-diagnostic-settings-cosmosdbforpostgresql.png b/static/img/send-data/export-metrics-diagnostic-settings-cosmosdbforpostgresql.png
new file mode 100644
index 0000000000..5cf663cc1c
Binary files /dev/null and b/static/img/send-data/export-metrics-diagnostic-settings-cosmosdbforpostgresql.png differ