The following is a list of issues addressed and enhancements implemented in this release.
General
|
Defect ID |
Resolved Issue |
| SSDB-14052 | In Memory databases doesn't return information when the number of databases is high |
| SSDB-13849 | Supports long FglAM names through the installation wizard |
| SSDB-13809 | Prevent SQL agents topology duplication |
| SSDB-13772 | Enterprise Disk Storage is now replaced by two reports: Top Disk Space Usage: Shows top instances (By size) and enables filtering their displayed disks by available free space (% or MB). Disk Space Usage: Shows the disk usage by an instance |
| SSDB-13751, SSDB-13747, SSDB-13594 | Reduce the log files to the minimum required |
| SSDB-13558 | Degree of Parallelism – Metric units changed to 'Threads' |
| SSDB-13604 | Protect against false CPU utilization reported on SQL Server of version 2008 (due to Microsoft's case number 115020112345243) |
| SSDB-13899 | Prevent SQL agents topology duplications |
Database Administration Dashboard
|
Defect ID |
Resolved Issue |
| SSDB-13400 | Add description to all alarms |
| SSDB-14046 | Default Email have been revised to check the minimal severity |
Rules
|
Defect ID |
Resolved Issue |
| SSDB-14075 | Rule DBSS - File Group Utilization has been tuned |
| SSDB-14019 | Rule "DBSS - Long Running Job' have been tuned |
| SSDB-13935 | Rule "DBSS - Days Since Last Backup" has been tuned |
Collections
|
Defect ID |
Resolved Issue |
| SSDB-13897, SSDB-13638 |
The Blocking collection has been revised in order to handle Lock request time out period and multiple lock types |
| SSSDB-13867 | HADR - Always on collection have been revised to handle listeners with multiple IP's |
| SSSDB-13848 | SPI collections now supports Case Sensitive instances |
| SSSDB-13216 | Added protection to Agent Job List collection when job duration is negative (Due to time change) |
| SSSDB-13621 | Error log collection has been revised due to Microsoft bug SR Number: 115020112345243 |
General
|
Defect ID |
Resolved Issue |
| SSDB-13235 | SPM Installer includes embedded agent manager for Win 64 |
| SSDB-13045 | Change defaults settings for alert log collection affecting alarms |
| SSDB-12721 | Revised the validation process of windows group users is SQL Server during the monitoring and creation of the agent |
| SSDB-12645 | Revised the OS credential mapping in case credentials are NULL |
| SSDB-12134 | Revised the agent manager selection mechanism in the agent installer |
| SSDB-12098 | Revised the installer to handle agent display name with special characters |
| SSDB-12069 | Alert the user for each log shipping failure |
| SSDB-11661 | Check disk percentage used for the disk containing database backups as well as database files |
| SSDB-10652 | Revised the Databases support dashboard - Topology cleaner |
Database Administration Dashboard
|
Defect ID |
Resolved Issue |
| SSDB-12710, SSDB-12626 | Revised the Save mechanism |
| SSDB-11572 | Exclude databases - Added an option to exclude databases by submitting a regular expression |
| SSDB-10537 | Email settings was moved from the alarms section to the Foglight administration and will apply to all cartridges also added the ability to prefix a default Email address for all agents |
| SSDB-12845 | default values in the Error log settings are changed:
|
Rules
|
Defect ID |
Resolved Issue |
| SSDB-12835 |
Revised DBSS - Availability Group Database is not Failover Ready |
|
New Rules:
|
Collections
|
Defect ID |
Resolved Issue |
| SSDB-12450, SSDB-12340 | Reporting services collection has been revised to be able to handle Reporting services database name with special characters |
| SSDB-11068 | Revised the Databases collection:
|
|
Defect ID |
Resolved Issue |
|
SSDB-13652 |
Improve command-line Installer performance |
|
SSDB-13643 |
Remove deleted SQL PI repository agent from available agents |
|
SSDB-13618 |
Improve SQL PI dashboard performance |
General
|
Defect ID |
Resolved Issue |
| SSDB-12046 | Cluster collection has been revised to support virtual name containing special characters. |
| SSDB-10977 | Revised the Deadlock collection usage of the SQL Server trace. |
| SSDB-10642 | Revised the Agent Installer time out mechanism. |
| SSDB-11515, SSDB-11113 | Support for connecting with a Windows account for a user whose password contains more than 14 characters. |
| SSDB-11144 | Support in the Agent Install for non-Latin collations |
| SSDB-11479 | The Cache hit metric has been replaced to present % in the History HP, Real-time HP and Reports. |
| SSDB-10524 | Added the option to reuse the DB credentials. |
Database Administration Dashboard
|
Defect ID |
Resolved Issue |
| SSDB-9937, SSDB-11496 | Revised the Email notification settings and configuration. |
| SSDB-11855 | Support changing retention policy for multiple agents in one action. |
| SSDB-11809 | Revised the Alarm severity saving. |
| SSDB-11383 | Email Server settings can now only be configured through Foglight Administration > Email Configuration |
Rules
|
Defect ID |
Resolved Issue |
| SSDB-11816 | DDBS- Replication Agents Status rules have been modified to be fired for the correct status of the snapshots agents. |
|
The following rules have been removed:
The following rules have been modified:
| |
| SSDB-11383 | Email Server settings can now only be configured through Foglight Administration > Email Configuration |
Collections
|
Defect ID |
Resolved Issue |
| SSDB-11775 | File group collection has been revised for files located on different disk volumes. |
| SSDB-11717 | Error log collection has been revised to handle special strings. |
The following is a list of issues known to exist at the time of this release.
| Defect ID | Known Issue |
| 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: 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-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-8826 | A Foglight Agent Manager (FglAM) residing on a Linux/UNIX machine cannot use Windows Remote Management (WinRM) to establish a connection with a Windows server. Connection using WinRM can only be carried out by a Foglight Agent Manager (FglAM) residing on a Windows machine. |
| SSDB-8388 | In an environment that includes a Foglight Agent Manager concentrator, when upgrading the environment where the concentrator does not contain any regular agents, the concentrator is not upgraded. Therefore, after the upgrade process takes place the Foglight Agent Manager concentrator has to be deployed manually. |
| SSDB-7866 | When running the agent installation wizard on a monitored host whose OS version is Windows 2008 R2, the OS validation fails. Workaround: review the following knowledge base article: https://support.quest.com/kb/SOL63439 |
| SSDB-7241, WCF-12907 | Currently users can create a recursive service, which calls itself and thereby causes an endless loop. If a user creates such a service the Databases dashboard will not be displayed. |
| SSDB-7090 | Reuse and copy of user-defined collections is only possible for collections that were created after the 5.6.4 version of the product was installed. |
| SSDB-7059 | The reports wizard contains multiple "all reports" tabs. Each tab is for a different database type. |
| SSDB-3045 | In a Federation environment, deleted agents are still displayed in the Global View > Databases table. |
| 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 |
| 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. |
| 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. |
| SSDB-10920 | row_count metric is supported from SQL Server version 10.50.2500 and above |
| Defect ID | Known Issue |
| 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. | |
| SSDB-11283 | Execution plan may not be resolved |
| SSDB-11657 | Time range changes are not effecting the execution plan dashboard. |
| 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. | |
| 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. |
| Defect ID | Known Issue | |
| n/a | The SQL PI repository is supported for Agent Managers that reside on:
| |
| n/a | Installing SQL PI repository is not possible on as Agent Manager installed on Linux with user root | |
| n/a | SQL PI repository and the Agent Manager running the monitoring Oracle agents (with the SQL PI extension), can reside on Windows64 or Linux64 OS platforms in either combination, as follows: | |
| SQL PI Repository | Oracle Agents With SQL PI | |
| Windows64 | Windows64 | |
| Windows64 | Linux64 | |
| Linux64 | Linux64 | |
| Linux64 | Windows64 | |
The following is a list of third party issues known to exist at the time of this release.
| Defect ID | Known Issue |
| 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:
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 (case 114081811709822), 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
To upgrade Foglight for SQL Server, follow the instructions in the Foglight Upgrade Guide
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.
This patch supports a minimum Foglight version 5.6.11 and minimum Agent Manager version 5.7.0.
The Foglight for Infrastructure agent will not be created in the following scenarios:
