What database setup and resource tracking requirements must be made to configure a SAP HANA system for Foglight agent monitoring? <div> <h4><strong>Database User Setup</strong></h4> <p><strong></strong>To configure the monitoring of an SAP HANA system, the Foglight agent requires a database user with sufficient privileges on the SYSTEMDB and each tenant database for which monitoring is desired.
The following message is filling the PostgreSQL agent log file monitoring Amazon RDS platforms. ... WORKAROUND ... None ... STATUS ... This issue was logged as defect FOGPGSQL-192 and has been fixed in the PostgreSQL 7.3.1.13 and higher cartridge.
What are agent properties for the Snowflake agent? ... Organization – The organization that this account belongs to. ... The Foglight topology created for this account will be under this organization, so it is very important that any accounts belonging to this organization are all provided the exact same string in the agent properties.
Add the following to the baseline.jvm.config file and restart the FglAM, this can be done manually directly in the file or using the JVM Config column in the Agent Managers panel.
Top SQL statements are truncated in the Top SQL drilldown pages of the DB2 agent for the monitored database. ... Change the setting in the Agent Properties increasing the Top SQL size. ... Navigate to Administration | Agents | Agent Status
All other database related data is being collected. ... CAUSE 1 ... Within the agent configuration (viewed via the latest agent log file), the Top SQL collection appears to be disabled: ... CAUSE 3
How can a user test deadlocks and blocking in the SQL Server agent? ... Lock: is done by database when any connection accesses the same piece of data concurrently. ... One connection needs to access a piece of data .
Foglight is not picking up deadlock activity on a monitored SQL Server instance. ... Foglight generates an email notification or alarm advising a deadlock condition has occurred, but the Activity dashboard does not display any data indicating a deadlock has or is occurring.
Please increase the maximum number of Top SQL rows retrieved in the Sybase agent properties and restart the Agent. ... From Foglight UI go to: Administration | Agents | Agent Status ... Select the Agent in question
Which Foglight Cartridge for SQL Server Availability/Usability alarms will fire against certain system status? <p>Below are the expected alarms to trigger when the monitored system is in a particular status.
How can be Foglight be installed to monitor SQL Server database instances on hosts in a DMZ? <p>There are two options available to monitor a SQL Server host located in the DMZ outside of an internal firewall.</p> <ul><li>Install a Foglight Agent Manager in the DMZ and then have the FglAM communicate with the hosts also in the DMZ.
DBSS_Databases collection times out with messages like the following in the agent log ... java.lang.RuntimeException: Failed to execute collection [DBSS_Database], reason=The query has timed out.
For Oracle ASM monitoring using SSL the password file should be configured correctly. ... ASM (Automatic Storage Management) is a system used by Oracle to manage storage for databases. ... It requires a password file to securely control administrative access, particularly when connecting remotely or performing critical operations.
After upgrading to 7.2.2.10 and higher, the username and password or service account that is running the FMS application is being passed to retrieve data from SQL PI instead of previously entered PI repository credentials.
Can a default database other than sybsystemprocs be used in the Sybase SAP ASE agent? ... The Sybase agent stored procedures are hardcoded to be written to sybsystemprocs. ... WORKAROUND ... None.
In order to set up Statement monitoring in the PostgreSQL agent monitoring Azure Database for PostgreSQL you'll need to first follow these steps to enable the pg_stat_statements extension for collecting query statistics.
Investigating OS connection issues can be challenging when there are numerous credentials present in the FMS. ... This knowledgebase article describes some techniques to identify and resolve common OS credentials issues for Windows and Linux / Unix.
How can Kerberos debug be enabled in the Foglight Agent Manager (FglAM)? <ol><li>Change line 7 of [FGLAM_HOME]/state/default/config/auth.login.config to the following: ... <pre class="language-markup" style="background: #efefef;padding: 8px;display: block;border: 1px solid rgb(204, 204, 204);overflow-x: auto;"><code>com.sun.security.auth.module.Krb5LoginModule required client=TRUE refreshKrb5Config=TRUE debug=TRUE;</code></pre>
Receiving alarms about the CRS software, which is used for monitoring Oracle Clusterware, requires creating CRS agents. ... NOTE: The Monitor More Clusterwares wizard supports the monitoring of a single CRS cluster.
Databases on a secondary replica are read-only, so the grant script cannot create the user in the database. ... The foglight user may still not be able to read data from these read-only replicas until the users will be synchronized.
In some cases, the following errors can be seen when running the report: ... "Too many databases requested. ... For SQL versions lower than 2012, can only produce fragmentation report on one database at a time"
What generic steps can be followed to troubleshoot and investigate database agent rule and alarm issues such as ... Top SQL). ... Analogous SQL or OS queries can also be run directly against the monitored host to see the results outside of Foglight.</p> <p> </p> <h2>Agent Configuration</h2> <p>Each agent is managed by the settings configured in the Agent Status Properties for each agent.
Why is there a difference? ... Plan query length is over the limitation of [400000] for handle [0x0500220034210a7445fff23566500000001000000000000000000000000000000000000000000000000000000] ... Most plans which are not resolved because their length exceeds the 400,000-character limitation.
While using the Cartridge for Oracle, an instance is backed up once a day using RMAN. ... The "DBO - Days Since Full Backup " rule incorrectly fires because the alarm is not validating the INCR LEVEL 0 as a FULL backup.
Other wait indicates miscellaneous instance waits consisting of infrequent or otherwise special purpose wait states that should, in most cases, be very close to 0. ... Although this deviation does not necessarily indicate a performance problem, the performance history should be reviewed.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center