Foglight for SQL Server (Cartridge) 5.9.7.10 - Release Notes

FOM-609

Cannot use cluster server or AlwaysOn listener to monitor AlwaysOn environment on FIPS-enabled FMS.

Workaround: Refer to KB 324797 for detailed information.

FOM-800

When there are many DB agents with PI enabled in FMS environment and you want to upgrade the cartridge to the latest version, the SQL PI component update might fail.

Workaround: Click Cancel on Update SQL PI Failed and click Update SQL PI Components to update again.

FOGDG-858

DB instance is still synchronized and displayed in FMS federation master even though it is stopped for some reason and not displayed in the FMS federation child.

PIFOG-431

After DB agent restarts, there will be a 5 minutes data gap in the SQL PI baseline view.

PIFOG-666

Incomprehensible error message is displayed when using local account without hostname prefix to setup PI Repository.

Workaround: Use hostname\username to setup PI Repository instead of only using username.

PIFOG-701

Enabling SQL PI is only supported when the SQL PI agent manager is installed on one of the following operating systems:

PIFOG-723

“Context infos” display null in the Comparison Parameter dashboard.

GVFOG-207

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

SSFOG-456

If two SQL Server instances running in different hosts but these two hosts have the same short name, these two hosts shows same on the Home page.

Workaround: Contact Quest support to get the scripts for updating the loadGVData function.

SSFOG-551

Due to the metric collection interval, value of Data files, log files, and disk space metrics will be occasionally missing on the Databases > Temdb dashboard.

Workaround: Wait for 3 minutes, then you will see these metrics on the dashboard.

SSFOG-645

It fails to run DBSSSQLAgentErrorLogProcessor processor of DBSS_SQL_Agent_Error_Log collection if the SQL Server Agent Service is not started.

Workaround: Start the SQL Server Agent Service.

SSFOG-736

DBSS_Error_Log_List collection fails if SQL Server 2017 Agent is not running on Linux.

SSFOG-739

Logical Disk metrics of SUSE showing on the SQL Server Overview dashboard is different from its value showing in the Infrastructure dashboard.

SSFOG-770

Alarm is not triggered while the error has been collected on the DBSS - SQL Server Error Log page.

SSFOG-775

If AD authentication has been used to monitor SQL Server instance, the default option 'Log in to the host using the same account used for monitoring SQL Server' cannot be used to monitor Linux Operating System (OS).

Workaround: Switch to use the option 'Log in to the host using different login credentials', then choose either of the following Linux authentication types: input AD account info, input other Linux account info, or use 'Select from stored credentials...'.

SSFOG-844

When using IP address to create a SQL server agent, Disk metric and Host metric will be missing in the Global view.

SSFOG-943

Using CLI to create multiple SQL Server instances with OS monitoring might result in failure to activate some host agents.

Workaround: Either activate those host agents manually on the Agent Status dashboard or re-create those host agents.

SSFOG-948

When monitoring SQL Server 2017 on Linux, an error message will be shown in Logs > SQL Agent Error Logs page.

SSFOG-949

If you select either of DB_SQL_Server, DB_SQL_Server_UI, DB_Global_View_UI, SPIRepository* cartridges then click Reset on the Cartridge Inventory dashboard, the upgrade wizard will prompt again.

Workaround: Do the following:

SSFOG-956

Creating Infrastructure agent automatically after failover occurs on Linux-based SQL Server cluster may fail.

SSFOG-976

In the Master server of the federation environment, the values in Message of back up alarm are null.

SSFOG-1031

When SQL Server cluster on Linux does fail-over, IC agent may not be auto created when the host name of the node is different with previous node.

SSFOG-1071

Databases Replication Dashboard does not show all Subscriptions when using multiple distribution databases.

SSFOG-1206

Failed to monitor SQL Server 2005 on premise while using no required permission DB credential.

Workaround: Download the DB_SQL_Server_Grant_Permission_Script from Components for Download, execute the script at SQL Server client to grant permission to the new user, then use the new user to monitor SQL Server 2005 Instance.

SSFOG-1207

Databases on a secondary replica are read-only, so the grant script cannot create the user in the database. The Foglight user may still not be able to read data from these read-only replicas even if the users are synchronized.

Workarounds:

SSFOG-1310

When the VMwarePerformance Agent exists, the Disk Latency in SQL Server Overview would always show “-” while enabling OS monitoring.

SSDB-2060

On SQL Server 2008, deadlocks on two different databases of the same instance become one chained deadlock.

Workaround: Implement trace flag -T1234.

SSDB-2379

When working with Global View while the screen resolution is set to 1024 by 768 pixels, it is advisable to switch to the browser's full view (F11 toggles between full and normal views in all browsers).

SSDB-2455

User-defined collection names and fields must be entered in Latin characters (A to Z), without any special symbols.

SSDB-3039

The DBSS- Deadlock Details alarm is disabled by default.

SSDB-3061

Changes made in the Global Administrations > Alarms screen are saved when switching to another global administration screen, even if selecting “Yes” in the dialog box that asks whether to exit without saving changes.

SSDB-5248

Editing a user-defined collection results in periodic overlap of data.

SSDB-5542

Creating a user-defined collection with more than one SQL in it will not alert the user, however, only the first SQL in the collection will be executed.

SSDB-8949

When editing the properties of the Foglight Agent Manager concentrator (Dashboards > Administration > Agents > Agent Status), the name of the Foglight Agent Managers should be entered in the Downstream FglAMs section exactly as they appear in the topology, under Home > Agents > All agents > <Agent name> > RMI data > FglAM host property.

SSDB-8987, SSDB-7326

On Microsoft® Windows® 2008 R2, a SQL Server version 2012 instance with a name that contains inverted commas (''; (for example:'X641_ENT1') can encounter issues with the retrieval of WMI data. This is by design on the part of Microsoft.

Workaround: If WMI data is not retrieved, the instance name without the '' should be added in the field Service Name in the Agent Properties dashboard.

SSDB-9138

Cluster data can be collected only if the xp_cmdshell parameter is configured.

To configure this parameter, run the following commands:

EXEC sp_configure ‘show advanced options’,1

GO

--To update the currently configured value for advanced options.

RECONFIGURE

GO

—- To enable the feature.

EXEC sp_configure ‘xp_cmdshell’, 1

GO

—- To update the currently configured value for this feature.

RECONFIGURE

GO

SSDB-9277

In SQL Server® 2012, when a database is part of an availability group and is currently accessible for connections, when the application intent is set to read only, several collections will fail.

SSDB-13199

Selecting a batch text in the lock tree may navigate to a non-equal batch in the TSQL Batches dimension.

SSDB-13479

In environments configured to use Agent Manager in High Availability mode the chosen Agent Manager hosting the SQL PI repository will host watchdog and maintenance agents that cannot participate in the Agent Manager high availability utility.

SSDB-14323

The SQL Server Error log collection requires you to use WinShell. Follow the instructions below to configure the correct settings:

SSDB-15192

SQL BI - Reporting services, integration services and Analysis services are not supported on cluster configuration.

SSDB-16097

In case the privilege of OS monitoring is not set to the Local Administrator group on the host being monitored, see the Knowledge Article 215054.

ODB-1606

Performing an upgrade process on a large environment (more than 50 agents) takes time to complete.

ODB-2829

When running user-defined collections on dynamic tables, deleted items are still kept in the topology. As a result, the number of rows displayed on the user-defined collections table will exceed the configured value for maximum allowed rows.

ODB-2984

In the Global Administration > User-defined Collections screen, it is possible to create two collections that bear the same name with a different capitalization (for example: MyCollection and Mycollection); however, the more recently created collection will not appear in the topology, nor will it be displayed on the User-defined Collections panel.

n/a

Need to wait for more than ten minutes between the upgrade of the Foglight Management Server and Foglight for SQL Server.

n/a

In environments configured to monitor SSAS agent only, when upgrading to version 5.9.2.1 or later, the upgrade process will fail.

Workaround: In the Administration > Agents > Agent Status dashboard, click Deploy Agent Package, then follow on-screen instructions to deploy the SSAS package manually.

n/a

Monitoring Analysis services is supported only on Agent Managers running on Windows which must have a version of .NET 3.5 installed.

n/a

If the WMI exception “Format specifier '%s' “ is entered in agent log the following workaround is recommended:

Workaround:

For Windows® Vista® and Windows Server 2008 or above:

According to http://support.microsoft.com/kb/929851, the default dynamic port range for TCP/IP has changed in both versions. The new default start port is 49152 and end port is 65535. Subsequently, monitoring instances that run under these operating systems can be carried out by setting a static (fixed) WMI port in Windows Server.

For more information, see the Knowledge Article 114559.

n/a

When Foglight or the Agent Manager are installed on a VM, it is highly recommended to reserve the following:

n/a

Antivirus exclusions is required for the SQL Server-based SQL PI repository. For more information refer to the Microsoft’s official article https://support.microsoft.com/en-us/help/309422/choosing-antivirus-software-for-computers-that-run-sql-server.

SSDB-11283

Execution plan may not be resolved.

SSDB-11582

Sometimes, query_hash is changed by SQL Server and generating a plan using the Generate button fails. SQLhash isn't found in XML so the screen displays No operation was found and the execution plan changes are missing.

SSDB-11657

Time range changes are not affecting the execution plan dashboard.

n/a

In the Execution Plan comparison popup, the date of the selected plan is the insert time to the SQL PI repository and not the execution time.

n/a

In the Execution Plan Comparison popup for statement - the estimated plan appears only as the selected plan on the left side. It cannot be selected from the list.

SSFOG-1716

No throughput data on dashboard for SSAS 2017 due to WMI class missing.

Workaround:

WCF-16277

Popup SQL Statement dialog cannot show all SQL text when accessing with Firefox browser using FMS version higher than 5.9.4.

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

FAM-7722

In FIPS-compliant mode, it is required to use at least 2048 RSA and DSA key size to do OS monitoring via SSH connection in DB cartridge.

When FglAM version is lower than 5.9.7.1, FglAM will not check RSA/DSA key size < 2048, and the connection is non-FIPS compliant.

Workaround: Upgrade the FglAM version to 5.9.7.1 or later.

n/a

WMI-related issue

Problem: WMI support is affected by the firewall

Workaround: For Windows versions prior to Windows 2008/Vista, use the following steps:

For Windows Vista® and Windows Server 2008:

According to Microsoft® http://support.microsoft.com/kb/929851, the default dynamic port range for TCP/IP has changed in these versions. The new default start port is 49152 and end port is 65535.

Subsequently, monitoring instances that run under these operation systems can be carried out by using either of the following options:

n/a

As a result of the change introduced in Java 6 update 29 to how data is sent to databases, users may experience connection failures when using the Microsoft JDBC Driver for SQL Server® to connect to SQL Server. This interoperability enhancement is available in the following SQL Server versions:

n/a

Third Party Limitations

Monitoring an SQL Server instance that resides on a Windows 2008R2 or higher requires a workaround as follows:

n/a

Some base values are not updated when using the Win32_PerfRawData_PerfDisk_LogicalDisk WMI class to calculate performance data in Windows Vista or in Windows Server 2008, because this class does not contain the PercentDiskTime_Base metric.

Workaround: A hotfix is available on Microsoft site, https://support.microsoft.com/kb/961435/en-us.

n/a

Due to a known Microsoft issue, on SQL Server instances version 2014 the SQL text presented may be truncated.

n/a

SQL's and execution plans may not be collected on SQL Server 2014 as a result of a Microsoft bug: “The values of column query_hash and query_plan_hash are NULL for DMV sys.dm_exec_requests in SQL Server 2014"

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.