Return
-
Title
How to configure multiple Agent Manager instances -
Description
The files related to the Agent Manager’s run-time state (for example, configuration and log files), are saved in the /state/ directory tree. Under the state directory, there is a sub-directory for each available Agent Manager instance.
You can run multiple instances of the Agent Manager using a single Agent Manager bin directory
CAUTION: Running multiple instances of the Agent Manager on the same host is intended for cluster and failover support only and is not intended to be used for any other purposes. Installing separate instances of the Agent Manager on the same system is therefore neither recommended nor supported.
In this type of configuration, you create multiple instances and each instance uses a different state directory but runs from a single Agent Manager bin directory. One example 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 Agent Manager instances share one bin directory, each time you deploy agents, upgrade agents, or deploy Agent Manager upgrades to one instance, all other instances are also updated.
You can also configure multiple physical installations of the Agent Manager to use a corresponding state directory that exists on a single shared drive. One example use of this functionality is running the 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.
CAUTION: The --create-state and --location command-line options are not recommended for use with the embedded Agent Manager, because the embedded Agent Manager does not include its own JRE. Instead, it is configured by the Management Server to use the same JRE that the Management Server uses.Since the Management Server is not aware of additional state directories that you may have created, it cannot properly configure them. Instead, you need to manually configure and maintain the JVM location in the Management Server installation.
If you do not create multiple instances (by following the instructions below), the Agent Manager creates an instance called default and stores the state files in the state/default directory.
IMPORTANT: On UNIX® platforms, the entire Agent Manager installation — including all state directories — must be owned by the same system user. -
Resolution
To create a new Agent Manager instance:
1. Launch a command shell on the Agent Manager machine, and navigate to the /bin directory.
2. Issue the following command:
fglam --create-state --location "{STATE_NAME}"
Where is the name of the new instance. A new state directory is created in {FGLAM_HOME}/state/{STATE_NAME}.
1. Launch a command shell on the Agent Manager machine, and navigate to the /bin directory.
To run an Agent Manager instance:
2. Issue the following command:
fglam --location "{STATE_NAME}"
Where is the same instance name you specified above. When you deploy agents to the instance, files related to the run-time state for these agents (including log files) are stored under the {FGLAM_HOME}/state/{STATE_NAME}/agents directory for that instance.
NOTE: Refer to the Foglight Agent Manager Guide for an example of running multiple instances in a cluster environment