[DBM] Document the Unmonitored status for Azure SQL databases - #39182
Draft
aldrickdev wants to merge 1 commit into
Draft
[DBM] Document the Unmonitored status for Azure SQL databases#39182aldrickdev wants to merge 1 commit into
aldrickdev wants to merge 1 commit into
Conversation
Contributor
Preview links (active after the
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Added a short Troubleshooting section to the Azure SQL Server Database Monitoring setup page explaining what it means when an Azure SQL Database, Managed Instance, or Elastic Pool node shows up under the DBM "Unmonitored" tab, and listing the most common causes and fixes: verifying the SQL Server integration is enabled and configured correctly, confirming
dbm: trueis set, confirming thedatadoglogin has the permissions required for the Azure SQL deployment type, checking the Agent's status output for thesqlservercheck, and checking Agent logs for connection or permission errors.Why
Azure SQL nodes can appear correctly configured yet remain stuck under the DBM "Unmonitored" tab, and the Azure SQL Server setup page never explained what causes or resolves that state, leaving readers without guidance to self-serve the fix.
Docs preview
https://docs.datadoghq.com/database_monitoring/setup_sql_server/azure/