Chatee ahora con Soporte
Chat con el soporte

Foglight for SQL Server (Cartridge) 6.0.1.10 - Release Notes

Third party known issues

The following is a list of third party issues known to exist at the time of this release.

 
Table 5. Third-party known issues
Issue ID
Known issue

SSFOG-1716

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

Workaround:

1
Download cumulative update package through https://support.microsoft.com/en-us/help/4056328/performance-counters-are-missing-after-the-installation-of-ssas-2017.
2
Install the package on the host where SSAS is installed.
3
Restart the host.

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:

1
When importing license into installer, change license file name to XXX.license.
2
Install xxx.lic after login FMS.
3
Change license file name to XXX.license and put it into license folder before FMS start up.

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:

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

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

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.

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.

Upgrade and Compatibility

A direct upgrade to Foglight for SQL Server 6.0.x is only available from version 5.7.5.x or later. Customers that are running 5.7.x of the product must first upgrade to version 5.7.5.x and then upgrade to version 6.0.x. A direct upgrade to Foglight for SQL Server 6.0.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.

For example, if your Foglight for SQL Server is version 5.5.8 and you are going to upgrade to version 6.0.x, the upgrade path will be 5.5.8 > 5.7.x > 5.7.5.x (or later) > 6.0.x.

To upgrade Foglight for SQL Server to version 6.0.x:
•
Install version 6.0.x of the cartridge as you would install a new Foglight for SQL Server cartridge. Do not delete the older version of the .car file. Install version 6.0.x over the older version.
For cartridge installation instructions, see the Foglight for Databases Deployment Guide.

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/.
•
Starting from version 5.9.5.20, Infobright is no longer supported. It is necessary to move existing agents to the SQL Server-based PI repository. We have provided a data migration utility for customers who want to keep their historical performance data. For more information, refer to How to migrate database agents to a SQL Server-based PI repository.

 

* 
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

6.0.0

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.

6.0.0

All platforms supported by this version of the Foglight Agent Manager

System requirements

Before installing Foglight for SQL Server, ensure that your system meets the hardware and software requirements detailed in Foglight System Requirements and Platform Support Guide.

Customers running large deployments (that is, with more than 20 agents) should consult the Foglight for Databases Deployment Guide.

Required privileges

For information on the required privileges, refer to the Foglight for Databases Deployment Guide.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación