Federation is a Foglight feature that addresses the needs of customers who monitor large-scale environments that are naturally partitioned into logical units. Each partition is traditionally served by one Foglight Management Server instance and its distributed clients/agents.
Things to take into consideration:
The Federation Master does not store data. It queries data, on demand, from the Federated Children.
If one or more of the Federated Children are not available, the affected data charts will be empty (“No data” may be displayed). Metrics and complex observations (pulled data) are not stored or cached on the Federation Master.
Administration of Federated Children from a single Federation Master is not supported.
In most cases, data-driven rules are ineffective in the Federation Master, because this server does not receive data from agents. Only data-driven rules that rely on internal Management Server metrics work in the Federation Master.
If the source event originates on the Federation Master, then associated event-driven rules work well. If the source event originates on a Federated Child, associated event-driven rules do not fire.
Agents are not able to connect to Federation Masters directly. If an agent is configured to attempt a direct connection, it will receive errors similar to the errors that agents normally receive when the server is not running.
Running the Federation Master in High Availability (HA) mode is not supported. Only the Federated Children can be run in High Availability mode.
Only a single layer of federation is supported (that is, no federation of Federation Masters is provided).
There is a potential time-delay for agents. There is no time delay for data once the topology model is synchronized.
Custom dashboards are not propagated from Federated Children to the Federation Master. Customers must manually push custom dashboards to the Federation Master.
The Foglight Cartridge for Automation is not supported in a Foglight federation environment.
Configuration Example:
1. Enable the federation mode by setting the server.federation variable to TRUE in Federation Master’s server.config:
server.federation = "true";
2. Add the URL of each Federated Child on the federation.config file on the Foglight Federation Master Server:
#
FederationURLs = (
"rmi://childfms1.test.local:1099",
"rmi://childfms2.test.local:1099",
);
Note 1:
Notice that server.conf has defined by default the federation port like this:
server.federation.port = "1099";
This port must be open on the Foglight Master server and the Child.
Note 2:
Firewall Configuration
1). On Linux the firewall can be turned off using the following commands:
systemctl status firewalld
systemctl disable firewalld
iptables-save
systemctl reboot –i
2). Also remember to check the Windows Firewall if needed.
Note 3:
When installing a Management Server, federation is by default disabled. When you install a Management Server, the server does not know if it is going to operate as a Federation Master or as a normal server. The server identifies this only on startup, by checking the server.federation variable in the server.config file. If this variable is set to TRUE, the server makes a number of changes that are necessary for it to run efficiently (given a certain load).
CAUTION : If you accidentally start the server with this variable set to FALSE, you must then either restore from a backup (if you have one), or completely re-install the Federation Master and database.
In order to remove Federation, please undo above changes.
Related Links:
Foglight 5.9.x and later:
Foglight 5.7.x and lower versions:
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center