The following is a list of issues addressed and enhancements implemented in this release.
Defect ID |
Resolved Issue |
FOGDG-300 |
Microsoft Visual C++ 2010 Redistributable Package is installed automatically when setting up PI. |
SSFOG-704 |
Support for long collation names in Index Fragmentation Report. |
SSFOG-691 |
Enhanced performance of Availability group monitoring. |
SSFOG-647 |
Do not fire backup alarm on Snapshot Databases. |
SSFOG-626 |
Fixed the issue where the Export as PDF alarm did not display data. |
SSFOG-616 |
Skip replication collections for an instance that is not a distributor. |
SSFOG-613 |
Reduced overhead on the monitored instance due to tuned lock collection. |
SSFOG-604 |
DBSS_Replication_Subscriptions failed with the exception: Failed to execute collect collection. |
SSFOG-588 |
Fixed the issue where Replication Agent does not properly detect misc jobs that are in the running state. |
SSFOG-576 |
Improved the SQL Agent Jobs dashboard. |
SSFOG-517 |
Filter Out Foglight Queries from the SSAS PI View. |
SSFOG-514 |
Fixed the issue where PI does not collects waits occurred by threads associated with parallel execution queries. |
SSFOG-486 |
Fixed the issue where some wait events were not categorized correctly as idle. |
SSFOG-451 |
Fixed the issue where the Database dashboard showed wrong files for secondary databases. |
SSFOG-403 |
Fixed the issue where Default Email settings in the Database Alarms dashboard did not accept the To field. |
SSFOG-399 |
Fixed the issue where VMware details could not be removed/unset from SQL Server agent within the DB Wizard GUI. |
SSFOG-398 |
Fixed the resource pool display issue for the instance which target_memory topology was null. |
SSFOG-337 |
Fixed the issue where DBSS_DTC_Information collection failed when connecting with WinRM. |
PIFOG-6 |
Windows PI repository has been upgraded to Infobright version 5.0.4. |
The following is a list of issues known to exist at the time of this release.
Defect ID |
Known Issue |
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-739 |
Logical Disk metrics of SUSE showing on the SQL Server Overview dashboard is different from its value showing in the Infrastructure dashboard. |
SSFOG-736 |
DBSS_Error_Log_List collection may fail for SQL Server on Linux if SQL Server Agent is not running. |
SSFOG-561 |
PI extension cannot be enabled for DB agents that are deployed on mixed environments (Linux® and Windows®). Workaround: Use the same version of DLP for both Linux and Windows environments. See the Knowledge Article 215534 for details. |
SSFOG-558 |
The Timeout error occurs when enabling OS monitoring in the Management Server 5.7.1. Workaround: Upgrade the Management Server to 5.7.5 or later. |
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-520 |
DB agents need be re-upgraded after upgrading the Foglight Management Server. Workaround: Make sure to wait for more than 10 minutes between upgrade of the Foglight Management Server and Foglight for SQL Server. |
SSFOG-442 | Anti-Virus Protection tools may result in the failure of setting up the installer agent, due to the occupied gar file. It is highly recommended that you exclude |
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 available at |
SSDB-15192 |
SQL BI - Reporting services, integration services and Analysis services are not supported on cluster configuration. |
SSDB-14323 |
The SQL Server Error log collection requires you to use WinShell. Follow the instructions below to configure the correct settings: |
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-13199 |
Selecting a batch text in the lock tree may navigate to a non-equal batch in the TSQL Batches dimension. |
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-9138 |
Cluster data can be collected only if the xp_cmdshell parameter is configured. To configure this parameter, run the following commands: |
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-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-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-5248 |
Editing a user-defined collection results in periodic overlap of data. |
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-3039 |
The DBSS- Deadlock Details alarm is disabled by default. |
SSDB-2455 |
User-defined collection names and fields must be entered in Latin characters (A to Z), without any special symbols. |
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-2060 |
On SQL Server 2008, deadlocks on two different databases of the same instance become one chained deadlock. Workaround: Implement trace flag -T1234 |
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. |
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-1606 |
Performing an upgrade process on a large environment (more than 50 agents) takes time to complete. |
n/a |
In environments configured to monitor SSAS agent only, when upgrading to version 5.7.5.50, 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 |
On mixed Windows and Linux environments, SQL PI stops monitoring after upgrading the Foglight database cartridge to 5.7.5.30 and higher. Workaround: Perform the procedure described in the Knowledge Article 212566. If you are upgrading from 5.7.5.30 (and higher) to version 5.7.5.50, redo this procedure. |
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: 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 operation systems can be carried out by using either of the following options:
For Windows versions prior to Windows 2008/Vista:
For more information, see the Knowledge Article 114559 available at https://support.quest.com/kb/114559. |
n/a |
In cases when Foglight or the Agent Manager are installed on a VM the following need to be reserved:
|
Defect ID |
Known Issue |
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 effecting 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. |
The following is a list of third party issues known to exist at the time of this release.
Defect ID |
Known Issue |
n/a |
Anti-Virus Protection tools installed on Windows® may negatively impact CPU and system performance of machines running Foglight the Agent Manager and the SQL PI repository.
|
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 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, http://support.microsoft.com/kb/961435/en-us. |
n/a |
Due to a known Microsoft issue (https://support.microsoft.com/en-us/kb/3036328), on SQL Server instances version 2014 the SQL text presented may be truncated. |
n/a |
The Windows System Center 2012 Endpoint Protection tool may negatively impact CPU and system performance of machines running Foglight and the Agent Manager. To reduce resource consumption it is highly recommended that you exclude the following directories from being scanned by the tool:
|
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" http://support.microsoft.com/kb/2953592 |
n/a |
The Foglight Time Bar Chart click event does not work with Chrome version 40.x.x.x and 39.x.x.x. https://code.google.com/p/chromium/issues/detail?id=428308 |
Workaround for all missing WMI metric cases
In some cases, running the command: %windir%\system32\wbem\wmiadap.exe /f in Windows' command-line (CMD) may solve the problem of missing WMI classes. This command parses all the performance libraries on the system and refreshes the Performance Counter Classes. For further details, see http://msdn.microsoft.com/en-us/library/aa394528%28VS.85%29.aspx
A direct upgrade to Foglight for SQL Server 5.7.x is only available from version 5.5.8 or later. Customers that are running earlier versions of the product must first upgrade to version 5.5.8 and then upgrade to version 5.7.x.
Note: The Foglight for Infrastructure agent will not be created in the following scenarios:
Foglight for SQL Server 5.7.5.50 requires Management Server version 5.7.0 or later and Agent Manager version 5.8.0 or later.
To upgrade Foglight for SQL Server:
Once you have upgraded the cartridge, to deploy the agent package, navigate to the Global View dashboard and follow the upgrade wizard instructions. For a procedure describing how to deploy the agent package, see the Foglight for Databases Deployment Guide.
Note: Foglight for SQL Server does not support the upgrade method of placing the new version in the folder <foglight_home>/upgrade/cartridge/.
Important: If you are upgrading to the current version of Foglight for SQL Server in a Federation architecture, the upgrade should be applied first to the Federated Children and then to the Federation Master. If the Federation Master is upgraded first, it will display incorrect information regarding the number of instances being monitored in the Status Summary section.
The following Foglight product versions and platforms are compatible with this release.
Product Name |
Product Version |
Platform |
Foglight Management Server |
5.7.0 or later |
All platforms supported by this version of the Foglight Management Server |
Foglight Agent Manager Note: The monitoring agents available in this version of Foglight for SQL Server support the Agent Manager HA failover mode, except for the Agent Manager monitoring SQL PI agents. For more information about this mode, see the Agent Manager Guide. |
5.8.0 or later |
All platforms supported by this version of the Foglight Agent Manager |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center