Please run ps -ef | grep -i Foglight on your Linux server
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 DBSS_Deadlock_Data collection fails because the extended event (xel) file cannot be found on the monitored host. ... An error similar to the following appears in the SQL Server agent log file.
In Foglight 6.1 and higher, Administrator users have the ability to export an Alarm Template from one Foglight Management Server (FMS) and import the alarm template into a different FMS. ... It is not possible to import and export the Factory Template via REST API.
The below instructions cover common steps used to configure an encrypted connection from the PostgreSQL Agent client. ... <div> <p>In order to use SSL, the ssl parameter must be set in the PostgreSQL server’s postgresql.conf file and the server certificate and private key must exist and be in the default data directory or another directory specified in the configuration.
How to backup and restore the Foglight installation? ... The Backup & Restore procedure of the Foglight installation (with embedded or external database; installed on Windows or Unix) can be found here.
How-to configure the Sybase SAP ASE MDA agent to collect the backup error log remotely ... In the version 7.3.1 and earlier releases of the Sybase SAP ASE MDA agent the backup error log information can only be collected when the FglAM is running on the Sybase machine (locally).
The Sybase agent is not able to monitor the Sybase backup server log and the following error is seen in the agent log file: ... - AgentErrorMessages: Backup Error Log File does not exist ... Entry did not contain the actual log file name
The following roles were not assigned for the user.
</strong>This will be done by replacing string, integer and decimal literals that are found in SQL statements and queries with placeholder data which has no reference to the original PII or sensitive data.
How might one export the scripts saved in the Script Console for a particular user so they can be imported into another FMS? <p>Use the "Export Scripts" and "Import Scripts" options in the Administration > Tooling > Script Console dashboard to export / import selected scripts:</p>
How can an Oracle PDB be monitored without using a CDB? ... When the user tries to add a PDB database directly for monitoring a message similar to the following appears. ... Monitoring Oracle 12c is only supported if using a common user and connection details that log in to CDB$ROOT container.
How to add Oracle 12c container and pluggable databases to Foglight? ... New icon in the Databases dashboard which indicated that the instance is 'Pluggable'. ... Plugable (CDB) database support was added beginning with the 5.6.7.2 Oracle cartridge.
Unable to monitoring Oracle 12c PDB with common user and cdb$root access ... The following error may appear when using trying to use an invalid common user name or role name. ... ORA-65096: invalid common user or role name when running the script on the container
Manually make the following improvement to the rule SAP HANA Database Availability which has an incorrect trigger. ... It should be data driven. ... Also, simplify the rule firing condition to just #availability# < 100.0
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).
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center