MicrosoftThe other issue we are running into while on the preview is that on another tenant we have put in 19 databases for monitoring (a mix of primary and read-scale for Azure SQL DB). They all seem to be collecting fine, but some users aren't able to even get the Dashboard page to load, getting "Cannot connect to Kusto query URI. The Kusto cluster might be stopped or unreachable." I go to the Azure Data Explorer Cluster and try to click to different pages in the left tray (Databases, Query, Scale Up, etc.) and nothing works. I assume it is getting overloaded on the default tier it was created on (E2d_v5) and you just can't do anything on the portal with it unless you go stop the Data Watcher service (I will try it). But if that is the case, then some consideration might need to be put into ensuring the manageability of the cluster in Azure Portal has some resources and precedence even when fully maxed out...otherwise how can we ever hope to scale it up. Happy to provide screenshots or screen sharing if you would like to see anything.
