GVFOG-82

Fixed the issue where TopologyObjectNotFound exception occurs on the Databases dashboard.

PIFOG-87

Categorize the new wait event CXCONSUMER as IDLE_WAIT type.

PIFOG-82

Fixed the issue where locked objects miss the object name.

PIFOG-80

Disable SQL PI Statistics debug messages by default.

PIFOG-77

Fixed the issue where "DBSS - Long Lock Running" alarm was not fired when PI is enabled on DBSS 5.7.5.50.

PIFOG-44

Categorize the following events to WAIT_IDLE: CLR_SEMAPHORE, MISCELLANEOUS, PREEMPTIVE_XE_GETTARGETSTATE, REDO_THREAD_PENDING_WORK, WAIT_XTP_HOST_WAIT WAIT_IDLE, WAIT_XTP_OFFLINE_CKPT_NEW_LOG, and PARALLEL_REDO_WORKER_WAIT_WORK.

SSFOG-853

Fixed the issue where DBSS_Error_Log_Data query consumes the significant amount of cache memory.

SSFOG-852

Set auto-commit to true in the selected statements.

SSFOG-851

Fixed the issue where query hash is not resolved but the related batch is resolved.

SSFOG-800

Fixed the issue where tables collection fails with arithmetic overflow.

SSFOG-446

Improved the comments of the grant script.

SSFOG-397

Fixed the wrong SSIS- Overview tooltip for packages on the performance tile.

GVFOG-79

The user access configuration does not work for the instance which agent name is created manually.

SSFOG-866

In SQL Server Cluster environment, when "Cluster Virtual host" is not monitored by the Infrastructure agent that has monitored the active node, Disk Latency and Slowest Disk will have no data displayed on the SQL Server Overview dashboard.

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-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-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 fails if SQL Server 2017 Agent is not running on Linux.

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.

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
https://support.quest.com/kb/215054.

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:

• Configuring the Command-Shell Connection Settings

• Configuring Windows Management Instrumentation

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

PIFOG-100

Failed to retrieve data from SQL PI repository due to invalid JDBC connection returned.

Workaround: Refresh your browser.

PIFOG-90

SQL Server Analysis Services agent cannot capture DAX commands ran in the SSAS database.

PIFOG-83

In PI Instance View > SQL Statement, there is no SQL text displayed when clicking View SQL Text for a single SQL statement.

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, 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.9.2.1, 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:

• Configure the firewalls to allow traffic between servers in the dynamic port range of 49152 through 65535 (less secure).

• Limit the port range that is used in each monitored server.

For Windows versions prior to Windows 2008/Vista:

1. Open TCP port: 135. WMI by default uses the port range 1024 to 5000.

2. Open up a range of ports above port 5000. Port numbers below 5000 may already be in use by other applications and could cause conflicts with your DCOM applications. It is recommended to have at least 100 ports opened, as several system services rely on these RPC ports to communicate with each other.

3. Add the registry key, including additional ports.

   • Use the RPCCfg.exe (Windows Resource Kits) by running: rpccfg.exe -pe 5009-5009 -d 0

   • Manually add the registry keys under: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\Internet

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:

• Memory - the full amount of the required machine memory

• CPU - the amount of CPU MHz

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.

FOGDG-650

If the monitored DB host is shut down, upgrade of the Agent Manager hangs and the Agent Manager throws the error "Could not obtain a deployment lock. Will try again in 30,000 ms".

Workaround: Use either of the following solutions:

• Reconnect the DB host, stop the agent which connection is lost, and then proceed the upgrade again.

• Upgrade JDK to 1.8_u152 or later, and then restart the Agent Manager.

• Delete the agent which connection is lost from the Agent Status dashboard, and then restart the Agent Manager.

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.
To reduce resource consumption it is highly recommended that you exclude the following directories from being scanned by the Anti-Virus tools:

• <installation directory>:\Quest\<foglight>

• <installation directory>:\Infobright

• <installation directory>:\Quest\<FoglightAgentManager>

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:

1. Open TCP port: 135.
   WMI by default uses the port range 1024 to 5000.
2. Open up a range of ports above port 5000.
   Port numbers below 5000 may already be in use by other applications and could cause conflicts with your DCOM applications. It is recommended to have at least 100 ports opened, as several system services rely on these RPC ports to communicate with each other.
3. Add the registry key, including additional ports.
   • Use the RPCCfg.exe (Windows Resource Kits) by running: rpccfg.exe -pe 5009-5009 -d 0
   • Manually add the registry keys under: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\Internet

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:

• Configure the firewalls to allow traffic between servers in the dynamic port range of 49152 through 65535 (less secure).
• Limit the port range that is used in each monitored server.

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:

• SQL Server 2012 Production version and later
• SQL Server 2008 Service Pack 3 Cumulative Update 4
• SQL Server 2008R2 Service Pack 1 Cumulative Update 6
• SQL Server 2008R2 Service Pack 2

n/a

Third Party Limitations

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

1. Browse to https://support.quest.com/ and log in
2. Perform solution https://support.quest.com/kb/SOL65870

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:

• <installation directory>\Quest\<foglight>
• <installation directory>\Infobright
• <installation directory>\Quest\<FoglightAgentManager>

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

Foglight Management Server

5.7.5.x

5.9.1

5.9.2

5.9.3

All platforms supported by these versions 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.5.x

5.9.1

5.9.2

5.9.3

All platforms supported by these versions of the Foglight Agent Manager