Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Foglight for Azure SQL Database (Cartridge) - Release Notes

Issues also resolved in version



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.

Known issues

General issues



Azure PI dashboard cannot be accessed if the PI repository uses non-default port.


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.

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.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation