Skip to content

[DBM] Document the Unmonitored status for Azure SQL databases #39182

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.

Sign up for GitHub

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

Draft
aldrickdev wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

[DBM] Document the Unmonitored status for Azure SQL databases #39182

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions hugo/content/en/database_monitoring/setup_sql_server/azure.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -491,6 +491,20 @@
## Example Agent Configurations
{{% dbm-sqlserver-agent-config-examples %}}

## Troubleshooting

### Database shows as "Unmonitored"

Check warning on line 496 in hugo/content/en/database_monitoring/setup_sql_server/azure.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.headings 

'Database shows as "Unmonitored"' should use sentence-style capitalization.

If an Azure SQL Database, Managed Instance, or Elastic Pool node appears under the **Unmonitored** tab in Database Monitoring even though the Agent can connect to it, this usually means the Agent's connection is working but a required setup step was not completed. Check the following:

Check notice on line 498 in hugo/content/en/database_monitoring/setup_sql_server/azure.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.sentencelength 

Suggestion: Try to keep your sentence length to 25 words or fewer.

- Verify the Agent's SQL Server integration is enabled and configured correctly for your Azure deployment type.
- Confirm that `dbm: true` is set in the `sqlserver.d/conf.yaml` instance configuration—without it, the check reports basic metrics only and the database is not classified as monitored by DBM.
- Confirm the `datadog` login has the permissions required for your Azure SQL deployment type, as described in [Grant the Agent access](#grant-the-agent-access). A login that is missing a required grant (for example, `VIEW SERVER STATE` or `VIEW ANY DEFINITION` on Managed Instance) can connect successfully but be unable to collect the data DBM needs.
- [Run the Agent's status subcommand](/agent/configuration/agent-commands/#agent-status-and-information) and confirm `sqlserver` appears under the **Checks** section without errors.
- Check the Agent logs for connection or permission errors, which often point to a missing grant or an incorrect `azure` configuration block.

See [Troubleshoot Common Issues](/database_monitoring/troubleshooting/?tab=sqlserver) for more general DBM troubleshooting steps.

## Install the Azure integration

To collect more comprehensive database metrics and logs from Azure, install the [Azure integration][1].
Expand Down
Loading