Azure postgres flexible server metrics not sent to Amazon Managed Prometheus.

Deepika Deshpande 0

I am trying to export azure postgres flexible server metrics to Amazon Managed Prometheus. Able to view all the metrics for the existing database that were created in 2024.

When i create a new database now i can see only azure_active_connections_count being exported to prometheus and all other metrics as azure_cpu_percent being captured as 0. What can be the different parameters which can cause this differed behaviour between 2 similar database

Prasad Chaganti 0 Reputation points Microsoft Vendor

2025-02-20T04:52:29.5166667+00:00

Hi Deepika Deshpande,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

It looks like your new PostgreSQL Flexible Server database is not exporting all expected metrics to Amazon Managed Prometheus, except for azure_active_connections_count, while others like azure_cpu_percent are showing as 0. Here are some possible reasons for this behavior.

1.Database Monitoring Not Enabled for the New Database

The newly created database may not have diagnostic settings enabled to send metrics to Azure Monitor.

Verify if monitoring is enabled. Run the following command in Azure CLI

az monitor diagnostic-settings list --resource /subscriptions/<subscription-id>/resourceGroups/<resource-group>/providers/Microsoft.DBforPostgreSQL/flexibleServers/<server-name>

If missing, enable it. Run the following command in Azure CLI

az monitor diagnostic-settings create --name <name> --resource <resource-id> --workspace <log-analytics-workspace-id> --logs '[{"category": "PostgreSQLLogs", "enabled": true}]'

2.Metrics Export Delay or Throttling

Azure might take time to start sending metrics for a newly created database.

Wait for some time and check again.

Monitor the metric logs using. Run the following command in Azure CLI

az postgres flexible-server show --name <server-name> --resource-group <resource-group>

3.Prometheus Scrape Configuration Missing the New Database

Amazon Managed Prometheus might not be correctly scraping new database metrics.

Ensure that the Prometheus scrape jobs are correctly configured for the new database.

Check the Prometheus config file (prometheus.yml) and verify the target endpoint for the new database is included.

4.Metrics Permissions Issue

The new database might not have the right IAM roles or permissions for exporting metrics.

Assign the Monitoring Metrics Publisher role to the database. Run the following command in Azure CLI

az role assignment create --assignee <service-principal-id> --role "Monitoring Metrics Publisher"

Check the IAM settings in AWS for Prometheus to ensure Azure is allowed to send metrics.

5.PostgreSQL Extension for Metrics Not Enabled

Some Azure PostgreSQL extensions might not be enabled for the new database.

Run the following query on the new database:

SELECT * FROM pg_extension;

If extensions like pg_stat_statements or pg_monitor are missing, enable them:

CREATE EXTENSION IF NOT EXISTS pg_stat_statements;

please verify the below steps:

Enable diagnostic settings and check the logs for any issues.

Review the Amazon Managed Prometheus setup to make sure all required targets are correctly configured.

Confirm IAM permissions are properly assigned to allow metric exports.

Check that the necessary PostgreSQL extensions are enabled for metric collection.

I hope this information helps. Please do let us know if you have any further queries
Prasad Chaganti 0 Reputation points Microsoft Vendor

2025-02-21T08:50:49.8666667+00:00

Hi Deepika Deshpande,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.

In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Share via

Azure postgres flexible server metrics not sent to Amazon Managed Prometheus.

Your answer