ExecuteCommandOnRemoteHostsAction is an action that is used for the Agent Manager to execute a command on remote hosts.
1 |
Add the ExecuteCommandOnRemoteHostsAction action to your rule list. For more information about how to add or edit an action in a rule, refer to the Getting Started: create a new rule or Getting Started: view and edit rule definitions section in the Foglight Administration and Configuration Help. |
• |
AgentManagerName (Mandatory): The Agent Manager name that is delegated to invoke the command on remote hosts. |
• |
CommandLine (Mandatory): The command to be executed remotely. |
• |
RemoteHosts (Mandatory): Target host addresses and platforms map, for example, hostName=Windows!hostIP=Linux. The platform value can be either of the following: Windows or Linux. |
• |
AgentManagerNameUseRegExp (Optional): The flag indicating whether the AgentManagerName parameter should be treated as regular expressions. This value is either true or false. |
• |
MatchAll (Optional): The flag indicating whether to run the command on all Agent Managers that matches the selection criteria. If set to false, the command will be executed only on the first matching Agent Manager. |
• |
Port (Optional): SSH connection port, default is 22. Windows platform does not need to configure this value. |
• |
Timeout (Optional): Command executing timeout value. Default is 0, which will use the Agent Manager default timeout value. |
3 |
Go to the Dashboards > Administration > Credentials > Manage Credentials dashboard, add credentials for those remote hosts. The credentials usage must set to either “Execute Command On Remote Hosts For Windows” or “Execute Command On Remote Hosts For Unix”. |
The files related to the Agent Manager’s run-time state (for example, configuration and log files), are saved in the <fglam_home>/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.
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.
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. See Example: Running multiple instances in a cluster environment for more information.
As described below, you create a new instance (and its associated state sub-directory) by including the --create-state and --location "<state_name>" (or -l "<state_name>") options with the fglam command; you then use the fglam ‑‑location "<state_name>" command to run that new instance.
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. |
1 |
Launch a command shell on the Agent Manager machine, and navigate to the <fglam_home>/bin directory. |
1 |
Launch a command shell on the Agent Manager machine, and navigate to the <fglam_home>/bin directory. |
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.
In this type of installation, there are multiple physical installations of the Agent Manager on different failover nodes. When one node fails and shuts down, the next one starts and its Agent Manager instance accesses the latest changes stored in its state directory on a shared drive.
Begin by installing the Agent Manager on each node in your cluster. See Installing the Agent Manager for installation instructions.
In the following example, <state_dir> is a path to a state directory on a shared network server that is accessible locally from all machines. For example: on Windows clients, the <state_dir> can be f:\cluster_shared_dir\fglam_states\STATENAME_A, while on UNIX® clients, it is /mnt/cluster_shared_dir/fglam_states/STATENAME_A.
fglam --create-state --location <state_dir>
fglam --location <state_dir>
The files related to the Agent Manager instance’s run-time state—for example, configuration and log files—are stored under its remote state directory on the shared drive.
When the Agent Manager is running, you can deploy agents to it and create agent instances. Files related to the run-time state for these agents (including log files) are stored under the remote state directory for this Agent Manager instance. Using the example above, they are stored in <state_dir>.
Ensure that only one instance of the Agent Manager that uses a particular state directory is running at a time. Do not run two instances of the Agent Manager on separate machines (or separate active nodes in the cluster) and cause these instances to use the same shared state directory simultaneously.
The polling rate is controlled by the following properties:
• |
Minimum Polling Interval (seconds): The minimum polling interval, in seconds. |
• |
Maximum Polling Interval (seconds): The maximum polling interval, in seconds. |
• |
Polling Timeout (seconds): A time-out/grace period (in seconds) that the FglAMAdapter waits for a host to respond, before considering it as disconnected. This is used to account for clock skews and changes in timing typically seen on heavily loaded VMware images. |
For more information about the Agent Properties dashboard, see the Administration and Configuration Help.
© ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center