Here's a simple KQL query you can run in AI Logs to summarize exceptions from the Azure SQL calls:

dependencies
| where target contains ".database.windows.net"
| where tostring(customDimensions.Exception) !contains "Violation of"
| summarize sum(itemCount) by substring(tostring(customDimensions.Exception),0,275)
| order by sum_itemCount desc
| project sum_itemCount, Column1

Looking into stability issues and when problems arise we see large amounts of these:

1. Microsoft.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (258): Unknown error 258
2. Timeout expired.  The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.

I'm interested if others are also seeing these two exceptions in some volume for their CMS 12 on DXP?

Here's an issue for SqlClient that suggests this may be a broader issue with dotnet core running in Linux containers in general:
https://github.com/dotnet/SqlClient/issues/1530
 
For the DXP this suggests some tweaks are already in place:
https://support.optimizely.com/hc/en-us/articles/4432366206733-CMS-12-site-crash-due-to-SQL-timeout-error-when-working-in-CMS-edit-mode