Both generations of Áú»¢¶Ä²© agents run as a Windows service. For Áú»¢¶Ä²© agent 2, replace agentd with agent2 in the instructions below.
You can run a single instance of Áú»¢¶Ä²© agent or multiple instances of the agent on a Microsoft Windows host. A single instance can use the default configuration file C:\zabbix_agentd.conf
or a configuration file specified in the command line. In case of multiple instances each agent instance must have its own configuration file (one of the instances can use the default configuration file).
An example configuration file is available in Áú»¢¶Ä²© source archive as conf/zabbix_agentd.win.conf
.
See the configuration file options for details on configuring Áú»¢¶Ä²© Windows agent.
Áú»¢¶Ä²© agent for Windows does not support non-standard Windows configurations where CPUs are distributed non-uniformly across NUMA nodes. If logical CPUs are distributed non-uniformly, then CPU performance metrics may not be available for some CPUs. For example, if there are 72 logical CPUs with 2 NUMA nodes, both nodes must have 36 CPUs each.
To perform active checks on a host Áú»¢¶Ä²© agent needs to have the hostname defined. Moreover, the hostname value set on the agent side should exactly match the "Host name" configured for the host in the frontend.
The hostname value on the agent side can be defined by either the Hostname or HostnameItem parameter in the agent configuration file - or the default values are used if any of these parameters are not specified.
The default value for HostnameItem parameter is the value returned by the "system.hostname" agent key. For Windows, it returns result of the gethostname() function, which queries namespace providers to determine the local host name. If no namespace provider responds, the NetBIOS name is returned.
The default value for Hostname is the value returned by the HostnameItem parameter. So, in effect, if both these parameters are unspecified the actual hostname will be the host NetBIOS name; Áú»¢¶Ä²© agent will use NetBIOS host name to retrieve the list of active checks from Áú»¢¶Ä²© server and send results to it.
The "system.hostname" key supports two optional parameters - type and transform.
Type parameter determines the type of the name the item should return. Supported values:
Transform parameter is supported since Áú»¢¶Ä²© 5.4.7 and allows to specify additional transformation rule for the hostname. Supported values:
So, to simplify the configuration of zabbix_agentd.conf file and make it unified, two different approaches could be used.
Host name is also used as part of Windows service name which is used for installing, starting, stopping and uninstalling the Windows service. For example, if Áú»¢¶Ä²© agent configuration file specifies Hostname=Windows_db_server
, then the agent will be installed as a Windows service "Áú»¢¶Ä²© Agent [Windows_db_server]
". Therefore, to have a different Windows service name for each Áú»¢¶Ä²© agent instance, each instance must use a different host name.
To install a single instance of Áú»¢¶Ä²© agent with the default configuration file c:\zabbix_agentd.conf
:
On a 64-bit system, a 64-bit Áú»¢¶Ä²© agent version is required for all checks related to running 64-bit processes to work correctly.
If you wish to use a configuration file other than c:\zabbix_agentd.conf
, you should use the following command for service installation:
A full path to the configuration file should be specified.
Multiple instances of Áú»¢¶Ä²© agent can be installed as services like this:
zabbix_agentd.exe --config <configuration_file_for_instance_1> --install --multiple-agents
zabbix_agentd.exe --config <configuration_file_for_instance_2> --install --multiple-agents
...
zabbix_agentd.exe --config <configuration_file_for_instance_N> --install --multiple-agents
The installed service should now be visible in Control Panel.
To start the agent service, you can use Control Panel or do it from command line.
To start a single instance of Áú»¢¶Ä²© agent with the default configuration file:
To start a single instance of Áú»¢¶Ä²© agent with another configuration file:
To start one of multiple instances of Áú»¢¶Ä²© agent:
To stop the agent service, you can use Control Panel or do it from command line.
To stop a single instance of Áú»¢¶Ä²© agent started with the default configuration file:
To stop a single instance of Áú»¢¶Ä²© agent started with another configuration file:
To stop one of multiple instances of Áú»¢¶Ä²© agent:
To uninstall a single instance of Áú»¢¶Ä²© agent using the default configuration file:
To uninstall a single instance of Áú»¢¶Ä²© agent using a non-default configuration file:
To uninstall multiple instances of Áú»¢¶Ä²© agent from Windows services: