Chat now with support
Chat with Support

Foglight for Azure SQL Database (Cartridge) 6.0.0 - Release Notes

Issues also resolved in version and



Fixed an issue where AD account might not be used to monitor Azure SQL DB when the FglAM is deployed in Azure VM.


Fixed an issue when using customized email setting, email might not be sent for the Alarm SQL_AZURE - Database Unresponsive.


Disabled the alarm SQL_AZURE - Blockers Connections Baseline Deviation by default.


Disabled the alarm SQL_AZURE - All Active Connections Baseline Deviation by default.


Fixed an issue when the customers have hundreds of agents, the table records grow very fast. And 'registry_registry_value' and 'registry_registry_variable' take more than 1TB.


Fixed an issue where the DB agent log might print password information as Pa$$word, even if the value has been encrypted.


Fixed an issue where on-demand data connections might fail unless more TCP ports are opened.

Known issues

General issues



PI engine didn't use new credential changed in Connection Details dashboard.

Workaround: Reactive the agent after changing the credential.


When the monitored user is not an admin, the database is DTU, and the service tier is basic, standard s0, or standard s1, User cannot see data in Blocking (Current) dashboard and there is no data in PI dashboard.


When accessing the Database dashboard, no entry to the Upgrade wizard can be found after new version cartridge has been installed.

Workaround: Upgrade agent on Agent Status dashboard.


User Level Access and Manage Alarm Blackouts are not supported for Azure SQL DB, and they are not UI limitation/notes.


Azure cannot change RMI setting in Administration.

Workaround: Refer to KB:


An error log showed in FMS log for loading heatmap component in FMS version before 5.9.3.


Cross platform report is not supported for Azure SQL DB.


Agent does not support MFA (Multi-Factor_Authentication) connections to Azure databases.


Databases - SQL PI dashboard does not display an Azure SQL database agent configured with SQL PI.


Using the Azure SQL database cartridge, a FMS is configured only with Azure SQL DB agents configured with SQL PI, the Databases - SQL PI dashboard shows "No agent found to be configured with SQL PI. To configure SQL PI go to the Databases - SQL Performance Investigator"


Azure SQL database agents with SQL PI configured are not displayed in the Databases - SQL PI dashboard.


When creating a new user account to monitor an instance, If the same account is used as PI repository login to enable PI, the process will failed showing no permission error.

Workaround: Manually grant the database user the db_owner role for the new created PI repository database.

For more information, refer to KB article 331530.


When applying an alarm template to an agent, the Inconsistent Values indication may appear. This indication can be ignored.

Third party known issues

The following is a list of third party issues known to exist at the time of this release.


Cannot import license into installer with license file name XXX.lic.


Install xxx.lic after login FMS.
Change license file name to XXX.license and put it into license folder before FMS start up.


The Foglight Agent Manager (FglAM) failed to restart when upgrading DB Cartridge, which is due to Could not obtain a deployment lock error.

Workaround: Perform the procedure described in the Knowledge Article 266110.


Cannot use AD account to monitor Azure SQL DB when the FglAM deploy in Azure VM.

Workaround: Upgrade DataDirect driver to version 6.0.


The Foglight Time Bar Chart click event does not work with Chrome version 40.x.x.x and 39.x.x.x. Refer to for more information.


The Windows System Center Endpoint Protection (SCEP) tool and Anti-Virus Protection tools installed on Windows® may negatively impact CPU and system performance of machines running Foglight, Foglight Agent Manager, and the SQL PI repository.

To reduce resource consumption it is highly recommended that you exclude the following directory from being scanned by the protection tools:


Anti-virus software may negatively impact the CPU and system performance of machines running Foglight. To reduce resource consumption, it is highly recommended to exclude the relevant directory, processes, and executables from being scanned by the anti-virus software. For detailed information, refer to the “Configuring anti-virus exclusion settings” in Installing Foglight on Windows with an Embedded PostgreSQL Database.


When upgrading Foglight, if the FMS is upgraded to version 6.0.0 and the database cartridge is not, the dashboard will display “There is no data to display”.

Workaround: When upgrading Foglight to 6.0.0, first upgrade the FMS to 6.0.0, then directly upgrade the cartridges.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating