Hello @Maria Sales Here are a few things you might want to check:
- Diagnostic Settings: Ensure that you have correctly configured the Diagnostic Settings for your Azure SQL Database. You should have selected the ‘sqldbaAL’ workspace and turned on Diagnostics.
- Log Analytics Workspace: Make sure that the Log Analytics workspace
sqldbaAL
is correctly set up and is in the same subscription and region as your Azure SQL Databaseyour Azure SQL Database. - Resource Logs: Azure SQL Database collects Resource Logs, which were previously referred to as diagnostic logs. These logs are not collected and stored until you create a diagnostic setting and route them to one or more locations.
- Log Types: Check if the correct log types are enabled. Diagnostic settings available include: log: SQLInsights, AutomaticTuning, QueryStoreRuntimeStatistics, QueryStoreWaitStatistics, Errors, DatabaseWaitStatistics, Timeouts, Blocks, Deadlocks.
- Azure Monitor: Azure SQL Database can be monitored by Azure Monitor. If you are unfamiliar with the features of Azure Monitor common to all Azure services that use it, you might want to read up on Monitoring Azure resources with Azure Monitor.
I hope this solves your problem and answers your questions.