MicrosoftWhat is the timeline for having hundreds of databases displayed in a Watcher heatmap and for the ability to configure and manage watchers with PowerShell and AzureCLI?
MicrosoftKeith_L_Corser​ the intent of heatmaps in database watcher dashboards is to let you focus on the top resource consuming databases, rather than all databases being monitored.
To see more databases, you can use the Databases tab. You can also filter the databases displayed on a dashboard by subscription, resource group, logical server, database name to make it easier to find a specific database. Finally, once you are on the detailed dashboard for a given database, you can use the dropdown at the top to switch to any other monitored database.
If your question is about increasing the number of databases a single watcher can monitor, that's planned but we do not yet have an ETA we can share. The current workaround is to create multiple watchers that all use the same data store, each to monitor a subset of your databases.
Similarly, we do not yet have an ETA for the PowerShell and Azure CLI support, though both are planned. We do support programmatic deployments via Bicep, ARM templates, Terraform, and REST API. For more information including specific links, see Create and configure a watcher.
