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>
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'
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?
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.
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
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).
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.
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:
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.
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.
Chrome browser give following security warning when access FMS console via SSL. ... Subject Alternative Name Missing ... The certificate for this site does not contain a Subject Alternative Name extension containing a domain name or IP address.
QUESTION: We gathered an example CPU utilization report where a high data point was shown in one report, but was not shown in a subsequent report that included the same date. ... We modified the retention policy to keep raw data so data roll up is not a factor.
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.
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.
How to list the cartridges which have been installed on the Foglight Management Server (FMS)? ... Method 1: ... Click "Next" 5. ... The cartridge list will be on "Appendix | Installed cartridges" section on this report
When the winrm/config/service/auth/cbtHardeningLevel is set to "Strict" (especially for the environments that apply strict secure policy), only WinRM HTTPS connections that have configured channel binding correctly will be accepted by the host.
Is there a way to retrieve the units for a metric from a groovy script? ... If the topology object type and the metric names are known, then it is possible to get the units. ... For example, to get the unit of "Available Paging Space" from a "Host" object, please use the following groovy line in Script Console:
How can we move or migrate a Foglight Agent Manager (FglAM) with agents from one FMS server to another one? ... This is currently not available. ... When you have a client with agents running on it, and you reconfigure it to point to a brand new FMS that doesn't know anything about those agents, the first thing that will happen when the client connects to the new FMS is that the agents it had been running will be deleted, because the FMS doesn't know about them.
What are the steps required to use an external signed certificate in the Foglight Management Server (FMS) so user and Foglight Agent Manager (FGLAM) can connect FMS via HTTPS? ... Here are all required steps to use an external signed certificate in the FMS and connect FGLAM clients to FMS via HTTPS:
When using the Foglight command line interface "fglcmd" in Foglight 7.3 error "Unable to connect to remote server" is displayed when using HTTPS with username/password and "status code: 400" when enabling debug output.
A high interrupt rate @var2 count/second can indicate a bad disk controller or network interface. ... <p>The excessive interrupts alarm does not detect the cause of the interrupts, the text suggests the possibility of a bad disk controller or network interface issue as a general description based on previous customer experience to help provide some guidance where to begin investigating an issue.</p>
After upgrading to Foglight 7.1 a downstream Foglight Agent Manager (FglAM) is not able to connect to the concentrator FglAM. ... The following message is present in the FglAM logs: ... ERROR [Quartz[0]-0] com.quest.glue.core.comms.transport.http.Client - Error transmitting message to upstream server https://concentrator_hostname:15872. com.quest.glue.common.comms.CommunicationException: Could not send request to remote host https://concentrator_hostname:15872
© ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center