No Support for Microsoft.DBForPostgreSql/flexibleServers

Question

No Support for Microsoft.DBForPostgreSql/flexibleServers

Closed this issue 3 years ago · 8 comments

I am trying to export metrics for azure postgres flexible server. Post configuration, i am getting the below error.

2021/09/05 21:25:36 Using managed identity
2021/09/05 21:25:38 azure_metrics_exporter listening on port :9276
2021/09/05 21:25:47 Failed to get resource info: No api version found for type: Microsoft.DBForPostgreSql/flexibleServers

--list.definition and namespace works though.

`/etc/azure-metrics-exporter # /bin/azure_metrics_exporter --config.file=/etc/azure-metrics-exporter/azure.yml --list.definitions
2021/09/05 20:44:38 Using managed identity
2021/09/05 20:44:39 Resource: /resourceGroups//providers/Microsoft.DBForPostgreSql/flexibleServers/

Available Metrics:
2021/09/05 20:44:39 - backup_storage_used
2021/09/05 20:44:39 - cpu_credits_consumed
2021/09/05 20:44:39 - cpu_credits_remaining
2021/09/05 20:44:39 - cpu_percent
2021/09/05 20:44:39 - memory_percent
2021/09/05 20:44:39 - iops
2021/09/05 20:44:39 - disk_queue_depth
2021/09/05 20:44:39 - read_throughput
2021/09/05 20:44:39 - write_throughput
2021/09/05 20:44:39 - read_iops
2021/09/05 20:44:39 - write_iops
2021/09/05 20:44:39 - storage_percent
2021/09/05 20:44:39 - storage_used
2021/09/05 20:44:39 - storage_free
2021/09/05 20:44:39 - txlogs_storage_used
2021/09/05 20:44:39 - active_connections
2021/09/05 20:44:39 - network_bytes_egress
2021/09/05 20:44:39 - network_bytes_ingress
2021/09/05 20:44:39 - connections_failed
2021/09/05 20:44:39 - connections_succeeded
2021/09/05 20:44:39 - maximum_used_transactionIDs`

Answer 1 · 2021-09-05T22:05:06.000Z

Hmm, might we need a newer version of the library?

Answer 2 · 2021-09-06T07:50:27.000Z

Yea, looks there is a new providers api version.
https://docs.microsoft.com/en-us/rest/api/resources/providers
old api-version=2019-05-10 needs to be updated with 2021-04-01

Answer 3 · 2021-09-06T07:52:10.000Z

Would you like to send a PR?

Answer 4 · 2021-09-06T08:04:49.000Z

Raised the PR.
#108

Answer 5 · 2021-09-06T08:36:18.000Z

I presume this is fixed now?

Answer 6 · 2021-09-07T04:29:34.000Z

sadly, the problem still persists.

[jenkins@pgaztest01-bastion ~ ]$ kubectl logs -n cloudops azure-metrics-exporter -f
2021/09/07 04:18:36 Using managed identity
2021/09/07 04:18:39 azure_metrics_exporter listening on port :9276
2021/09/07 04:18:50 Failed to get resource info: No api version found for type: Microsoft.DBForPostgreSql/flexibleServers
2021/09/07 04:19:50 Failed to get resource info: No api version found for type: Microsoft.DBForPostgreSql/flexibleServers
2021/09/07 04:20:50 Failed to get resource info: No api version found for type: Microsoft.DBForPostgreSql/flexibleServers
2021/09/07 04:21:50 Failed to get resource info: No api version found for type: Microsoft.DBForPostgreSql/flexibleServers
2021/09/07 04:22:50 Failed to get resource info: No api version found for type: Microsoft.DBForPostgreSql/flexibleServers

Answer 7 · 2021-09-07T08:00:07.000Z

I'm afraid I'm not familiar enough with Azure to know what's going on. I'd suggest double checking the docs and config.

Answer 8 · 2021-09-14T19:32:27.000Z

This turned out to be issue with some case inventiveness between the resourceType name as listed in portal as compared to the one returned by the https://docs.microsoft.com/en-us/rest/api/resources/providers api.

"Microsoft.DBforPostgreSQL/flexibleServers" --> as returned by the provider api
"Microsoft.DBForPostgreSql/flexibleServers" --> as listed in the portal.

The problem sorted after I modified the target name with proper case in the azure.yml configuration