The user can rule out these sizing issues, which can cause communication SQL PI errors, or data not appearing in SQL PI dashboard:
The Architecture illustrated on a diagram for SQL PI on this link.
The latest Deployment Guide for Databases is available for download from here.
Enter “Foglight” and select “Deployment Guide”
The user must know how many Db agents with SQL PI in order to size up the SQL PI environment to cross reference with the Deployment Guide.
1). SIZING REQUIREMENTS *This is the most common cause for Performance Investigator (SQL PI, Oracle PI) issues *
Confirm the sizing configuration of the FglAM where the SQL PI repository is installer and the FglAM where the database agents are installed. Cross reference this with the Deployment Guide to confirm that the current product requirements have been met.
2). ANTIVIRUS EXCLUSIONS
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 required that users exclude the following directories from being scanned by the Anti-Virus tools:
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 required that users exclude the following directories from being scanned by the tool:
Please refer to KB 209121 for more details.
3). CPU and MEMORY VIRTUAL MACHINE RESERVATIONS
If the FGLAM agent manager for Db and SQL PI repository is running on Vmware, please ensure Vmware reserved is set for CPU and Memory. This is requirement and mandatory. Otherwise, on the repository log there will be Infobright restarting numerous of times. This will be the reason for SQL PI to be unstable when the Memory and CPU is not reserved on the VM. The user can use the Deployment Guide based on the amount of Db agents with SQL PI enabled, reference step 1 above. There are no alternatives. On the Virtual Machine Properties under Resources tab, uncheck "Unlimeted" based on the example below.
Another option is to use the VMware toolset (if installed on the VM) the reservation information is available.
Please refer to KB article 233207 for more information on finding reservation setting values using VMWare tools from the command line inside the Virtual Machine.
For example, if the Foglight Deployment guide states 8 cores CPU depending on the total number of Db agents with SQL PI,
the calculation will be 8 cores * 2.4GHz = 19.2 GHz (19,200MHz). The reservation for CPU is expressed in MHz.
Please refer to KB article 259596 for details on finding VMWare reservations in the FglAM bundles beginning with 5.9.3 and higher.
Reservations are irrelevant in cloud machines, in other words, you get the resources that you pay for in Amazon AWS and Microsoft Azure installations. Amazon does have the option of “EC2 Reserved Instances” but this is different compared to VM resource reservations.
4). PAGE FILE
In some environments it may be that the Windows -> Virtual Memory -> Page size setting was configured to a custom size and does not calculate automatically. In such a scenario a Foglight Agent Manager (FglAM) can exceed the available memory on the machine and cause the Fglam to crash. In order to verify if this occurring, it is necessary to check the Page file settings as shown in the below screenshot to change this. A customer must approve this change with their internal IT team.
© 2020 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz