-
-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Capture Metrics from Readonly Replica on Azure SQL DB #465
Comments
With multiple read replicas, the question is how to monitor a specific replica. It appears this is answered here: https://learn.microsoft.com/en-us/azure/azure-sql/database/read-scale-out?view=azuresql
So It's possible to identify if you are connected to a read replica by running: In theory, DBA Dash should be able to add a second connection to the read replica and monitor it. It needs to be identified separately from the primary though - some investigation is needed here. |
It's possible to add the read replica to the service config tool but there are other issues that would need to be resolved to improve the experience. To add the read replica:
Note: Individual DB connections would be required rather than a single connection to the master DB. Issues:
Possible workaround:
As a first step adding some visual indication if a AzureDB is readonly might be useful. |
I am doing this now by creating a secondary repository that holds only the read-scale copies of the same connection strings I have for my main write connection. As you said, it was as easy as adding the ApplicationIntent=ReadOnly parameter to the connection strings in the config tool. By doing a second repo, I don't need to worry about duplicated connection names, etc. |
Thanks @jacobgexigo. That seems like a good workaround. I'd like to add support for this feature at some point but it's not a priority as I don't currently have a requirement to monitor read replicas. |
Some tiers of Azure SQL DB come with a read-only replica which appears to share the same server and DB name as the primary and is only connected to via the addition of
ApplicationIntent=readonly
into the connection string.Per @DavidWiseman's request I tried adding this into the config manually and it did not appear to work correctly, CPU stats from the primary displayed but nothing else.
The text was updated successfully, but these errors were encountered: