-
Title
Configuring Multiple Foglight Agent Manager Instances -
Description
Can a single FglAM run multiple instances?
How to install multiple Fglam's on a single host?
-
Cause
The files related to the Foglight Agent Manager's runtime state—for example, configuration and log files—are saved in the /state/ directory hierarchy. Under the state directory, there is a subdirectory for each instance you create.
You can run multiple instances of the Foglight Agent Manager using a single Foglight Agent Manager bin directory. In this type of configuration, you create multiple instances and each instance uses a different state directory but runs from a single Foglight Agent Manager bin directory. One example use of this type of configuration is to test new agent settings without making changes to the agents you are currently using to monitor your production environment.
Caution: In a configuration where multiple Foglight Agent Manager instances share one bin directory, each time you deploy agents, upgrade agents, or deploy Foglight Agent Manager upgrades to one instance, all other instances are updated with it.
You can also configure multiple physical installations of the Foglight Agent Manager to use a corresponding state directory that exists on a single shared drive. One example use of this functionality is running the Foglight Agent Manager in cluster environments.
As described below, you create a new instance (and its associated state sub-directory) by including the --create-state and --location "" (or -l "") options with the fglam command; you then use the fglam --location "" command to run that new instance.
Note: If you do not create multiple instances (by following the instructions below), the Foglight Agent Manager creates an instance called default and stores the state files in the state/default directory.
-
Resolution
IMPORTANT: The feature "Multiple states of FglAM" will be desupported within Foglight version 5.6.11.
NOTE: We generally do not recommend multiple FglAM installs on a single host. This really does not provide much in the way of performance and can actually cause a bit of topology churn when FglAM does its self reporting.If you must do this, make sure to disable the FglAM self-metrics per the following procedure.- Open the $FGLAM_STATE/config/baseline.jvmargs.config file for editing.
- Add the following entry to the vmparameter. properties section of the file:
vmparameter.= "-Dquest.glue.disable.performancemonitor=true";
Important. You must replace with the next numeric sequence number. - Save the file.
- Disable system ID collection for all agents hosted on all FglAM instances.
- Restart the Agent Manager
STATUS: FAM-5832 has been logged as a know issue in the Foglight Agent Manager release notes.To create a new Foglight Agent Manager instance:
Navigate to /bin and run the following command:
fglam --create-state --location ""
- Where is the name of the new instance.
- A new state directory is created in %FglAM_HOME/state/.
NOTE: The target directory must NOT exist when running the '--create-state argument to fglam. The command creates the folder with the specified --location parameter.
To run a Foglight Agent Manager instance:
- Navigate to /bin and run the following command:
fglam --location ""
- Where is the same instance name you specified above.
- When you deploy agents to the instance, files related to the runtime state for these agents (including log files) are stored under the /state//agents directory for that instance.
-
Defect ID
FAM-5832