Known issues with the Azure SQL cartridge (4381560)

FAIO-217

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

Workaround: Reactive the agent after changing the credential.

FOM-1006

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.

AZFOG-29

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.

SSFOG-1569

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

SSFOG-1629

Azure cannot change RMI setting in Administration.

Workaround: Refer to KB: 4229801

GVFOG-207

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

N/A

Cross platform report is not supported for Azure SQL DB.

N/A

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

N/A

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

FOG-499

Using the 5.9.7.20 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"

or

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

FOG-728

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 4226213.

FGL-20596

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

Workaround:

FOGDG-650

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 4227225.

FOGDG-1372

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

Workaround: Upgrade DataDirect driver to version 6.0.

N/A

The Foglight Time Bar Chart click event does not work with Chrome version 40.x.x.x and 39.x.x.x. Refer to https://code.google.com/p/chromium/issues/detail?id=428308 for more information.

N/A

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:

N/A

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.

n/a

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.