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.
An agent blackout or global blackout is configured during a maintenance window; no alarms are received while the blackout is active but once it ends many Credential Management Event alarms fire and get cleared automatically.
Foglight is unable to start when using MySQL 8.x as the external database; the errors in the Management Server log indicate that the connection is not using a password even though one is set in the server configuration file.
How to configure email notifications when the FMS crashes or stops unexpectedly. ... <p>High Availability foglight can be used in conjuction with <a href="https://support.quest.com/technical-documents/foglight/7.1.0/high-availability-field-guide/4#TOPIC-2071242" target="_blank">Remote Monitor</a>
Please refer to the Foglight Upgrade Guides for the release you want to upgrade to. ... NOTE: Support recommends restarting the Foglight Agent Managers (FglAM) prior to cartridge upgrades via the Windows services or Linux/Windows command line, or using the restart functionality in the Agent Managers panel.
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.
Are there any alarms which notify when the Foglight database or server is having issues? ... What do alarms and email notifications regarding the "Catalyst" mean? ... The "Catalyst" alarms are related to the Foglight Management Server repository database or the server itself; for example:
In using Capacity Director to plan a host decommission, error "Host HOSTNAME is already scheduled for decommission" is displayed even though no hosts are listed under the Planned Changes pane. ... Topology objects related to a previously planned host decommission for the same host exist but are not listed in the Planned Changes pane from the Capacity Director dashboard.
How to update SAML 2.0 hostname used in the metadata.xml if you need to use a custom DNS entry instead of the physical hostname.
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.
From the Agent Status dashboard, when trying to add a tag to an agent, existing tags are not listed. ... ERROR [http-exec-24] com.quest.wcf.core.context.ContextUtils - Error getting value of context entry with key: tags com.quest.wcf.core.module.runtimevalue.RuntimeValueException: com.quest.wcf.publicapi.code.FunctionInvocationException: Failed to invoke method "findAllTags" for Java Function definition id=system:wcf_common_ui_table.findTagsByCategory using class=com.quest.wcf.components.table2.TaggingFunctions in view: 'system:wcf_common_ui_table.nested' in top-level view: 'system:administration_agents_agent_status.updatePageWrapper'
The configured limit of 50000 instances of type HostProcess has been reached. ... The configured limit of 50000 instances of type DB2_Database_Partition_Table has been reached. ... Foglight has a default limit of 50000 topology instances per object type.
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>
Enhancement Request to support customized values in Foglight SNMP Trap Actions <p>WORKAROUND</p> ... <p>Enhancement FGLCM-265 was opened to support customized values in Foglight trap actions and has been included in the 5.9.8 and higher releases of the Foglight Management Server.<br><br>The <strong>Send SNMP Trap Action</strong> parameters VarBind01OID to VarBind10OID and VarBind01Value to VarBind10Value can be used to specify custom OIDs and values to be sent in the SNMP trap.<br><br>For example:</p>
After enabling the Forward Alarms as SNMP Traps rule, we noticed that the trap was actually sent twice, once when the alarm was cleared and once when it was raised again. ... Is there a way to suppress sending the SNMP Trap for a cleared alarm?
When clicked on the explore button there is no response from the UI and the request hangs. ... Bug with the product. ... WORKAROUND ... Please contact Support for a hotfix patch for this issue. ... STATUS
Troubleshooting import of LDAP groups when logging into Foglight with LDAP users. ... Troubleshooting import of LDAP groups when logging into Foglight with LDAP users. ... AD groups that Foglight sees the user is a member of (based on the mode of group searching) get added as "External" Groups.
There is a need to integrate the Foglight notifications as SNMP traps to IBM Tivoli monitoring system. ... How to replace values within the alarms SNMP trap that is being sent by Foglight? ... This issue has to be looked on a cartridge by cartridge basis, to be able to change the data being sent in the SNMP trap message.
After upgrading to Foglight 6.3 or higher users can no longer authenticate using SAML. ... No changes have been made to the SAML configurations on Foglight. ... The URL in the error message may be displayed without a port if Foglight if using the default ports for HTTP (80) or HTTPS (443).
Foglight SAML metadata uses the wrong port when Foglight is behind a proxy or load balancer. ... For example, Foglight and the load balancer are configured to listen for HTTPS on port 8443. ... When accessing Foglight via the load balancer URL (E.g.: https://foglight.yourdomain.com:8443/console/saml2/metadata.xml), the metadata uses the default HTTPS port (443) which can cause problems with SAML authentication due to a mismatch in the ports.
How to modify a rule scope to exclude specific host? ... What is the best method to specify which hosts you wish to limit a particular cloned rule? ... How to scope a rule to specific host(s)? ... Note: Copy a rule and modify the copy as modified rules will not be updated on a subsequent cartridge update.
Foglight 6.3.0.5 and 7.1.4 introduce a new blackout type that allows disabling all alarms during a blackout. ... The system:globalblackout command is available from the Foglight command-line interface with the following options and arguments:
Alerts are being triggered every hour, even though there has been no change in state. ... A multi-severity alarm is being triggered hourly for the same condition. ... The rule behavior remains unchanged.
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"
When looking at the built-in groups on the "User Management" dashboard ,there is the group "Foglight Users". ... This group has no roles assigned but each Foglight user is member of this group. ... It is not allowed to delete the group.
© ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center