Welcome to the Foglight® High Availability Field Guide. This Field Guide provides step-by-step instructions on how to configure your Foglight 5 environment to use High Availability (HA) Mode. Use it to enable, configure, and tune Foglight Management Server(s) in HA Mode.
Configuring multiple servers using HA mode offers the following capabilities:
• |
Automatic restart: The restart process (FoglightHA Daemon) runs on the same host that the Foglight® Management Server it is monitoring and monitors the state of the server. If the server stops responding or has a fatal error, then the restart process stops and restarts the server automatically. The process can also send out email notifications about the server condition. |
NOTE: The default value for the restart process is ten minutes (600 seconds). Machines with a slower processing speed take longer to reboot. You can modify the default time by editing the startup.grace variable in the <foglight_home>/config/restart_monitor.config file. |
• |
Redundancy: To reduce outage times, a standby server instance is created (for a particular Management Server). One server becomes the primary server and communicates with the agents, receives and processes data, and processes rules. All other servers are standby servers. If a primary server stops responding, one of the standby servers resumes service and becomes the primary server. |
High Availability is a Foglight® feature that addresses the needs of customers to ensure that a Management Server is always available, even in the event of a primary server failure.
HA mode has been tested in the following Common configuration scenarios:
Foglight® has the following known issues with respect to High Availability mode:
• |
• |
There is a JDK issue with IPv6 on Linux® that affects both HA and standalone server. For more information, see JDK with IPv6 on Linux. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center