Foglight comes with several Rules out of the box, and some of them have an associated EmailAction action. ... Those can be customized to also execute a CommandAction action, which passes a specified command to the OS where the Foglight Management Server is running.
When trying to validate the type of connection being established by the Windows agents, the log file 001 for the agent can be reviewed for the keywords:
From Foglight web console, navigate to the Databases dashboard. ... Select all of the database agents of a single type (for example SQL Server) to change. ... Click Settings | Administration ... select Connection Details
The Foglight login page is not accessible for few of the users when used with Windows Single Sign-On (SSO). ... HTTP Status 400 - Bad Request ... Request header is too large ... Logging on a user account that is a member of more than 1,010 groups may fail on a Windows Server.
The following versions of the JDK are used for the External Foglight Agent Managers. * An embedded FglAM shares the JRE with the Foglight Management Server that it has been installed with ... Platform
How to determine the version of Tomcat in use by Foglight? <p>The Tomcat version will be logged into the Foglight Management Server log which is located in "[FMS_HOME]/logs". The entry looks like this:</p>
Message: Cluster Failover. ... The SQL Server cluster group active node has moved from node SERVER1 to node SERVER2 Created on: 2025-01-16T06:11:42-08:00 ... Messages like the following appear in the SQL Server agent log file
The cipher suites added to the server.xml must also support the same key exchange algorithm as your SSL certificate, otherwise browsers and FGLAMS (Agent Managers) will not be able to connect to your server.</li><li>In order to list the certificates you can issue the following command from this directory: <strong>Quest_Software\Foglight\jre\bin></strong></li></ul>
This issue occurs only when accessing via the Angular UI (/aui) and Foglight is behind a proxy or load balancer; the Classic Console (/console) is not affected. ... When debug logging is enabled, the following message is included in the logs:
What PGA statistics are monitored in the Oracle agent? ... How can a user monitor when the Oracle database is reaching its maximum PGA (Program Global Area) allocation? ... What steps can you do to remedy the situation?
The SQL Server Error Log on a monitored instance indicates that the database agent has killed sessions. ... An "idle" session, is any session that was opened by the database agent but remained open on the server side, even after being closed on the client side (FglAM).
A popup with the message "Failed to save ASP for DB agents" popup appears when changing a SQL PI repository password for Oracle agents. ... This has not been found with the SQL Server agent but be present for agents of other domains including Azure SQL and MySQL PI.
After changing the account used to monitor SQL Server to use a service account in the validate connection area of the database agent, the standard SQL Server collections run with the new service account, but the PI collections keep running with the older SQL authenticated login.
The percentage of Worker Threads used (100.00%) is greater than the defined threshold 95.00%. ... I can't find an explanation for the alarm. ... What does it mean? ... SQL Server uses the native thread services of the Windows operating systems so that one or more threads support each network that SQL Server supports simultaneously, another thread handles database checkpoints, and a pool of threads handles all users.
A security scan has identified vulnerability CVE-2025-24813 for the Apache Tomcat version used by Foglight. ... Is Foglight affected by the Apache Tomcat Vulnerability CVE-2025-24813 for Remote Code Execution and/or Information disclosure and/or malicious content added to uploaded files via write enabled Default Servlet?
You can select any of the following type of credential depending on your system configuration or preference: ... RSA Key - Generate a new RSA key using the following commands (use -m PEM to ensure the key is in PEM format): ssh-keygen -t rsa -m PEM
Messages like the following appear in database agent log files for SQL PI where the current value for repository.storage.host differs from a previous value. ... Current value: [MYSERVERB], engine value: [MYSERVERA]</span> <p>or</p> <span style="font-family: Courier New,Courier,monospace;">ERROR [AGENTNAME-lowPriorityPool-1-[DBSS_PI_Engine_Maintenance][]] com.quest.qsi.fason.sqlserver.common.spi.BaseSpiController - Failed to initialize SQL PI engine<br>java.lang.RuntimeException: Cannot register engine due to mismatch in connection to the repository parameter: repository.storage.host.
Some alarms are cleared by the system while others must be cleared by the user. ... How do multiple-severity and simple rules alarms get cleared? ... This is by design. ... Whether Foglight clears alarms automatically or it must be done manually depends on the type of rule.
There is a multiple severity rule that has promoted to Fatal. ... The rule will not send any additional alerts as per the design of Foglight. ... Is there a way to configure repeated alarms so that it sends continuous notifications until it is resolved?
to authenticate users. ... It allows organizations to share and manage information about users and network resources. ... When properly configured, Active Directory provides an SSO environment that can be integrated with the standard Windows OS desktop login.</p> <p>When setting up the Kerberos Service Principal Name (SPN), use the following instructions to create mappings between the user account and SPNs, and to create a keytab file to configure in krb5‑auth.config.
Go to the Quest Support Portal to access the Foglight - Technical Documentation and search for the following items for details and help in the design and creation of custom Dashboards, Views, and Reports in Foglight:
On-Demand Data Settings does not work when customer is using Callback instead of RMI<br><br>The following error message is displayed (in red) in the UI and in the FMS log file.<br><br><span style="font-family: Courier New,Courier,monospace;">No signature of method: com.quest.qsi.fason.framework.connections.rmi.mssql.MSSQLAgentCallbackConnector.validateConnectivity() is applicable for argument types: () values: []</span> Change from RMI to Callbacks in Foglight 7.1 <p><br>1. Navigate to <strong>Administration | Rules & Notifications | Manage Registry Variables</strong><br>2. Type <strong>RMI </strong>in the search box and click <strong>DBWC_Use_Callback_Instead_RMI | View and Edit Details</strong><br>3. Click the <strong>Change </strong>button in Global Default and choose the <strong>False </strong>radio button under Select <strong>boolean </strong>value<br>4. Select the database agent from <strong>Global View | Settings | Administration | On-demand Data Settings</strong>, then validate connectivity with the On-Demand Data Port. There should be a green icon if the validation passes.<br><br></p>
Foglight allows you to configure rule behavior to ensure it does not fire repeatedly. ... Defining the behavior of rule alarms and actions can help to avoid being overwhelmed with alerts when a rule condition is met many times within a short period.
A user who wants to add SQL Server for monitoring with Active Directory authentication by using Foglight Agent Manager with AD (Active Directory) in place, once the user specifies the credentials, the FglAM will try to connect to the server with user from FglAM's service, not the AD user that is specified.
<p>Oracle 12c Exadata Multi-Tenant(CDB/PDB) ... was supported for FMS repository use beginning with the 5.7.5.7 version.</p> ... <div>Please consult the Foglight documentation for the database platforms currently supported FMS repository use, which includes CDB and PDB configurations.</div>
© ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center