Informazioni & Risorse specifiche del Fornitore ... Maggiori informazioni sono scritte qui. ... Hyper-V: https://support.microsoft.com/en-us/help/4072698/windows-server-guidance-to-protect- ...
Is Sybase SAP ASE High Availability monitoring supported? <p><b>Workaround</b><br>None<br> </p> ... <p><b>Status</b><br>High Availability (HA) in Sybase SAP ASE databases is not supported. Enhancement Request FGDBSYB-I-17 has been created for the Product Management to consider this enhancement for a future release of the Sybase SAP ASE cartridge.<br><br><strong>NOTE: </strong>To configure FglAM HA for Sybase SAP ASE agents (a different issue), refer to knowledgebase article <a href="https://support.quest.com/foglight/kb/4309338/how-to-configure-fglam-ha-for-sybase-agents" target="_blank">4309338</a>)</p> FGDBSYB-I-17
What is Support's policy on installations and upgrades? ... Here at Technical Support it is Quest’s policy not to be on call for assistance with Upgrades or Installations as we deal with break/fix issues at time of the problem.
This <a href="https://www.quest.com/community/blogs/b/database-management/posts/why-is-my-database-server-slow" target="_blank">blog post</a> written by Jason Hall from the Quest Pre-Sales team provides helpful general information on determining how to use Foglight to determine why the monitored database is slow.
The most common cause for resource issues on servers in a Foglight environment is due to insufficient sizing or not meeting the minimum requirements of the product. ... KB 227070 High CPU usage on Foglight Agent Manager (FglAM) where a PI repository is installed
See KB 138568 for example of servers exclusion at the rule level.
The TSQL Batches and individual SQL Statements are sorted based on "Active Time", with the batches / statements that consumed most active time appearing in the Tops 'n' list (Top 25 , Top 50 and so on).
The Monitor Instance dialog box appears. ... Choose the agent manager on which the agent is running. ... The default is the agent manager with the least agents installed. ... On the Monitor Instance pane, provide connection details.
Foglight collects data by running scripts (i.e. shell, sql, wmi) on a regular basis. ... Some these frequencies may be determined by the collection frequencies that are set in the agent properties.
Click Monitor | DB2 in the upper left corner of the Databases View. ... The Monitor Instance dialog box appears. ... Follow the online prompts to configure an agent to monitor the DB2 host, instance, and databases.
Hardware requirements for database monitoring vary depending whether SQL PI is configured and by the number of monitoring agents.
On the Database Dashboard, place a check mark next to the Oracle agent or agents to be modified. ... Click Settings | Administration. ... Select the Collections menu item.
discusses using the "Groovy Script" field of the Alarm Filter to select the rules and severities of the alarms associated with a service.
The Foglight cartridges for DB2, Oracle, and SQL Server has a user defined query (user defined collection) component that allows users to provide custom SQL statements to retrieve data. ... With this solution you would be able to run custom queries to gather data in addition to data the Foglight SQL Server cartridge provides without installing an agent on the monitored server.
Therefore, Foglight Management Server must be installed before installing a cartridge. ... To install the Foglight cartridge: ... Copy the cartridge car file included in the installation media to your local computer.
Please refer to the System Requirements and Platform Support Guide available for download from <a href="https://support.quest.com/foglight/technical-documents" target="_blank">here</a> for the current list of the supported platforms for the Foglight Agent Manager (FglAM).
Please consult the Deployment Guide for the Foglight database cartridge available for download from <a href="https://support.quest.com/foglight/technical-documents" target="_blank">here</a> for the current list of supported monitored databases.
Please refer to the System Requirements and Platform Support Guide available for download from <a href="https://support.quest.com/foglight/technical-documents" target="_blank">here</a> for the list of supported platforms for the Foglight Management Server (FMS).
See <a href="https://support.quest.com/foglight/kb/90881" target="_blank">KB 90881</a> for example regex usage.
The available sampling frequencies are as follows: ... Real-Time - When a user is currently focusing on a screen, the sampling frequency for all of the collections associated with this screen switches to Real-Time.
Beginning with the 5.7.5.2 FMS, users can run the "Rules Report" and get the details of the rules, with or without registry variables themselves. ... The rules should all now be self-documented in the UI, which is what the report pulls.
Permissions required for database monitoring depend on the database that is being used.
PI manages data using an internal time pyramid; the roll-up process runs every 15 minutes. ... 1 minute 6 hours
There are three main components: ... Foglight Management Server and Foglight Database Repository — Responsible for managing, alerting and viewing the collected data. ... Both components can be set to run on the same machine or reside on separate machines.
The MultiHostProcessAgent name can be known by doing a search of the hostname in the MonitoringPolicies_yyyy-mm-dd_nnnnnn.xml file. ... This file is included in the root of the Foglight Management Server (FMS) Support Bundle zip file.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center