en-us	#### Parameters  |Parameter|Mandatory|Range|Default|Description| |---------|---------|-----|-------|-----------| |AlertScriptsPath|no| |/usr/local/share/zabbix/alertscripts|Location of custom alert scripts (depends on compile-time installation variable *datadir*).| |AllowRoot|no| |0|Allow the server to run as 'root'. If disabled and the server is started by 'root', the server will try to switch to the 'zabbix' user instead. Has no effect if started under a regular user.<br>0 - do not allow<br>1 - allow| |AllowUnsupportedDBVersions|no| |0|Allow the server to work with unsupported database versions.<br>0 - do not allow<br>1 - allow| |CacheSize|no|128K-64G|8M|Size of configuration cache, in bytes.<br>Shared memory size for storing host, item and trigger data.| |CacheUpdateFrequency|no|1-3600|60|How often Zabbix will perform update of configuration cache, in seconds.<br>See also [runtime control](/manual/concepts/server#server_process) options.| |DBHost|no| |localhost|Database host name.<br>In case of MySQL localhost or empty string results in using a socket. In case of PostgreSQL<br>only empty string results in attempt to use socket.<br>In case of [Oracle](/manual/appendix/install/oracle#connection_set_up) empty string results in using the Net Service Name connection method; in this case consider using the TNS\_ADMIN environment variable to specify the directory of the tnsnames.ora file.| |DBName|yes| | |Database name.<br>In case of [Oracle](/manual/appendix/install/oracle#connection_set_up) if the Net Service Name connection method is used, specify the service name from tnsnames.ora or set to empty string; set the TWO\_TASK environment variable if DBName is set to empty string.| |DBPassword|no| | |Database password.<br>Comment this line if no password is used.| |DBPort|no|1024-65535| |Database port when not using local socket.<br>In case of [Oracle](/manual/appendix/install/oracle#connection_set_up) if the Net Service Name connection method is used this parameter will be ignored; the port number from the tnsnames.ora file will be used instead.| |DBSchema|no| | |Schema name. Used for PostgreSQL.| |DBSocket|no| | |Path to MySQL socket file.| |DBUser|no| | |Database user.| |DBTLSConnect|no| | |Setting this option enforces to use TLS connection to database:<br>*required* - connect using TLS<br>*verify\_ca* - connect using TLS and verify certificate<br>*verify\_full* - connect using TLS, verify certificate and verify that database identity specified by DBHost matches its certificate<br><br>On MySQL starting from 5.7.11 and PostgreSQL the following values are supported: "required", "verify\_ca", "verify\_full". On MariaDB starting from version 10.2.6 "required" and "verify\_full" values are supported.<br>By default not set to any option and the behavior depends on database configuration.<br><br>This parameter is supported since Zabbix 5.0.0.| |DBTLSCAFile|no<br>(yes, if DBTLSConnect set to one of: verify\_ca, verify\_full)| | |Full pathname of a file containing the top-level CA(s) certificates for database certificate verification.<br>This parameter is supported since Zabbix 5.0.0.| |DBTLSCertFile|no| | |Full pathname of file containing Zabbix server certificate for authenticating to database.<br>This parameter is supported since Zabbix 5.0.0.| |DBTLSKeyFile|no| | |Full pathname of file containing the private key for authenticating to database.<br>This parameter is supported since Zabbix 5.0.0.| |DBTLSCipher|no| | |The list of encryption ciphers that Zabbix server permits for TLS protocols up through TLSv1.2.<br>Supported only for MySQL.<br>This parameter is supported since Zabbix 5.0.0.| |DBTLSCipher13|no| | |The list of encryption ciphersuites that Zabbix server permits for TLSv1.3 protocol.<br>Supported only for MySQL, starting from version 8.0.16.<br>This parameter is supported since Zabbix 5.0.0.| |DebugLevel|no|0-5|3|Specifies debug level:<br>0 - basic information about starting and stopping of Zabbix processes<br>1 - critical information<br>2 - error information<br>3 - warnings<br>4 - for debugging (produces lots of information)<br>5 - extended debugging (produces even more information)<br>See also [runtime control](/manual/concepts/server#server_process) options.| |ExportDir|no| | |Directory for [real-time export](/manual/appendix/install/real_time_export) of events, history and trends in newline-delimited JSON format. If set, enables real-time export.<br>This parameter is supported since Zabbix 4.0.0.| |ExportFileSize|no|1M-1G|1G|Maximum size per export file in bytes. Only used for rotation if ExportDir is set.<br>This parameter is supported since Zabbix 4.0.0.| |ExportType|no| | |List of comma-delimited entity types (events, history, trends) for [real-time export](/manual/appendix/install/real_time_export) (all types by default). Valid only if ExportDir is set.<br>*Note* that if ExportType is specified, but ExportDir is not, then this is a configuration error and the server will not start.<br>e.g.:<br>ExportType=history,trends - export history and trends only<br>ExportType=events - export events only| |ExternalScripts|no| |/usr/local/share/zabbix/externalscripts|Location of external scripts (depends on compile-time installation variable *datadir*).| |Fping6Location|no| |/usr/sbin/fping6|Location of fping6.<br>Make sure that fping6 binary has root ownership and SUID flag set.<br>Make empty ("Fping6Location=") if your fping utility is capable to process IPv6 addresses.| |FpingLocation|no| |/usr/sbin/fping|Location of fping.<br>Make sure that fping binary has root ownership and SUID flag set!| |HANodeName|no| | |The high availability cluster node name.<br>When empty the server is working in standalone mode and a node with empty name is created.| |HistoryCacheSize|no|128K-2G|16M|Size of history cache, in bytes.<br>Shared memory size for storing history data.| |HistoryIndexCacheSize|no|128K-2G|4M|Size of history index cache, in bytes.<br>Shared memory size for indexing history data stored in history cache.<br>The index cache size needs roughly 100 bytes to cache one item.<br>This parameter is supported since Zabbix 3.0.0.| |HistoryStorageDateIndex|no| |0|Enable preprocessing of history values in history storage to store values in different indices based on date:<br>0 - disable<br>1 - enable| |HistoryStorageURL|no| | |History storage HTTP\[S\] URL.<br>This parameter is used for [Elasticsearch](/manual/appendix/install/elastic_search_setup) setup.| |HistoryStorageTypes|no| |uint,dbl,str,log,text|Comma separated list of value types to be sent to the history storage.<br>This parameter is used for [Elasticsearch](/manual/appendix/install/elastic_search_setup) setup.| |HousekeepingFrequency|no|0-24|1|How often Zabbix will perform housekeeping procedure (in hours).<br>Housekeeping is removing outdated information from the database.<br>*Note*: To prevent housekeeper from being overloaded (for example, when history and trend periods are greatly reduced), no more than 4 times HousekeepingFrequency hours of outdated information are deleted in one housekeeping cycle, for each item. Thus, if HousekeepingFrequency is 1, no more than 4 hours of outdated information (starting from the oldest entry) will be deleted per cycle.<br>*Note*: To lower load on server startup housekeeping is postponed for 30 minutes after server start. Thus, if HousekeepingFrequency is 1, the very first housekeeping procedure after server start will run after 30 minutes, and will repeat with one hour delay thereafter.<br>Since Zabbix 3.0.0 it is possible to disable automatic housekeeping by setting HousekeepingFrequency to 0. In this case the housekeeping procedure can only be started by *housekeeper\_execute* runtime control option and the period of outdated information deleted in one housekeeping cycle is 4 times the period since the last housekeeping cycle, but not less than 4 hours and not greater than 4 days.<br>See also [runtime control](/manual/concepts/server#server_process) options.| |Include|no| | |You may include individual files or all files in a directory in the configuration file.<br>To only include relevant files in the specified directory, the asterisk wildcard character is supported for pattern matching. For example: `/absolute/path/to/config/files/*.conf`.<br>See [special notes](special_notes_include) about limitations.| |JavaGateway|no| | |IP address (or hostname) of Zabbix Java gateway.<br>Only required if Java pollers are started.| |JavaGatewayPort|no|1024-32767|10052|Port that Zabbix Java gateway listens on.| |ListenBacklog|no|0 - INT\_MAX|SOMAXCONN|The maximum number of pending connections in the TCP queue.<br>Default value is a hard-coded constant, which depends on the system.<br>Maximum supported value depends on the system, too high values may be silently truncated to the 'implementation-specified maximum'.| |ListenIP|no| |0.0.0.0|List of comma delimited IP addresses that the trapper should listen on.<br>Trapper will listen on all network interfaces if this parameter is missing.| |ListenPort|no|1024-32767|10051|Listen port for trapper.| |LoadModule|no| | |Module to load at server startup. Modules are used to extend functionality of the server.<br>Formats:<br>LoadModule=<module.so><br>LoadModule=<path/module.so><br>LoadModule=</abs\_path/module.so><br>Either the module must be located in directory specified by LoadModulePath or the path must precede the module name. If the preceding path is absolute (starts with '/') then LoadModulePath is ignored.<br>It is allowed to include multiple LoadModule parameters.| |LoadModulePath|no| | |Full path to location of server modules.<br>Default depends on compilation options.| |LogFile|yes, if LogType is set to *file*, otherwise<br>no| | |Name of log file.| |LogFileSize|no|0-1024|1|Maximum size of log file in MB.<br>0 - disable automatic log rotation.<br>*Note*: If the log file size limit is reached and file rotation fails, for whatever reason, the existing log file is truncated and started anew.| |LogType|no| |file|Log output type:<br>*file* - write log to file specified by LogFile parameter,<br>*system* - write log to syslog,<br>*console* - write log to standard output.<br>This parameter is supported since Zabbix 3.0.0.| |LogSlowQueries|no|0-3600000|0|How long a database query may take before being logged (in milliseconds).<br>0 - don't log slow queries.<br>This option becomes enabled starting with DebugLevel=3.| |MaxHousekeeperDelete|no|0-1000000|5000|No more than 'MaxHousekeeperDelete' rows (corresponding to \[tablename\], \[field\], \[value\]) will be deleted per one task in one housekeeping cycle.<br>If set to 0 then no limit is used at all. In this case you must know what you are doing, so as not to [overload the database!](zabbix_server#footnotes) **^[2](zabbix_server#footnotes)^**<br>This parameter applies only to deleting history and trends of already deleted items.| |NodeAddress|no| | |IP or hostname with optional port to override how the frontend should connect to the server.<br>Format: <address>\[:port\]<br>The priority of addresses used by the frontend to specify the server address is: NodeAddress (1); ListenIP (if not 0.0.0.0 or ::) (2); localhost (default) (3)<br>See also: HANodeName parameter| |PidFile|no| |/tmp/zabbix\_server.pid|Name of PID file.| |ProxyConfigFrequency|no|1-604800|3600|How often Zabbix server sends configuration data to a Zabbix proxy in seconds. Used only for proxies in a passive mode.| |ProxyDataFrequency|no|1-3600|1|How often Zabbix server requests history data from a Zabbix proxy in seconds. Used only for proxies in a passive mode.| |SNMPTrapperFile|no| |/tmp/zabbix\_traps.tmp|Temporary file used for passing data from SNMP trap daemon to the server.<br>Must be the same as in zabbix\_trap\_receiver.pl or SNMPTT configuration file.| |SocketDir|no| |/tmp|Directory to store IPC sockets used by internal Zabbix services.<br>This parameter is supported since Zabbix 3.4.0.| |SourceIP|no| | |Source IP address for:<br>- outgoing connections to Zabbix proxy and Zabbix agent;<br>- agentless connections (VMware, SSH, JMX, SNMP, Telnet and simple checks);<br>- HTTP agent connections;<br>- script item JavaScript HTTP requests;<br>- preprocessing JavaScript HTTP requests;<br>- sending notification emails (connections to SMTP server);<br>- webhook notifications (JavaScript HTTP connections);<br>- connections to the Vault| |SSHKeyLocation|no| | |Location of public and private keys for SSH checks and actions| |SSLCertLocation|no| | |Location of SSL client certificate files for client authentication.<br>This parameter is used in web monitoring only.| |SSLKeyLocation|no| | |Location of SSL private key files for client authentication.<br>This parameter is used in web monitoring only.| |SSLCALocation|no| | |Override the location of certificate authority (CA) files for SSL server certificate verification. If not set, system-wide directory will be used.<br>Note that the value of this parameter will be set as libcurl option CURLOPT\_CAPATH. For libcurl versions before 7.42.0, this only has effect if libcurl was compiled to use OpenSSL. For more information see [cURL web page](http://curl.haxx.se/libcurl/c/CURLOPT_CAPATH.html).<br>This parameter is used in web monitoring since Zabbix 2.4.0 and in SMTP authentication since Zabbix 3.0.0.| |StartAlerters|no|1-100|3|Number of pre-forked instances of [alerters](/manual/concepts/server#server_process_types).<br>This parameter is supported since Zabbix 3.4.0.| |StartDBSyncers|no|1-100|4|Number of pre-forked instances of [history syncers](/manual/concepts/server#server_process_types).<br>*Note*: Be careful when changing this value, increasing it may do more harm than good. Roughly, the default value should be enough to handle up to 4000 NVPS.| |StartDiscoverers|no|0-250|1|Number of pre-forked instances of [discoverers](/manual/concepts/server#server_process_types).| |StartEscalators|no|1-100|1|Number of pre-forked instances of [escalators](/manual/concepts/server#server_process_types).<br>This parameter is supported since Zabbix 3.0.0.| |StartHistoryPollers|no|0-1000|5|Number of pre-forked instances of [history pollers](/manual/concepts/server#server_process_types).<br>This parameter is supported since Zabbix 5.4.0.| |StartHTTPPollers|no|0-1000|1|Number of pre-forked instances of [HTTP pollers](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.| |StartIPMIPollers|no|0-1000|0|Number of pre-forked instances of [IPMI pollers](/manual/concepts/server#server_process_types).| |StartJavaPollers|no|0-1000|0|Number of pre-forked instances of [Java pollers](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.| |StartLLDProcessors|no|1-100|2|Number of pre-forked instances of low-level discovery (LLD) [workers](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.<br>The LLD manager process is automatically started when an LLD worker is started.<br>This parameter is supported since Zabbix 4.2.0.| |StartODBCPollers|no|0-1000|1|Number of pre-forked instances of [ODBC pollers](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.| |StartPingers|no|0-1000|1|Number of pre-forked instances of [ICMP pingers](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.| |StartPollersUnreachable|no|0-1000|1|Number of pre-forked instances of [pollers for unreachable hosts](/manual/concepts/server#server_process_types) (including IPMI and Java)**^[1](zabbix_server#footnotes)^**.<br>At least one poller for unreachable hosts must be running if regular, IPMI or Java pollers are started.| |StartPollers|no|0-1000|5|Number of pre-forked instances of [pollers](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.| |StartPreprocessors|no|1-1000|3|Number of pre-forked instances of preprocessing [workers](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.<br>The preprocessing manager process is automatically started when a preprocessor worker is started.<br>This parameter is supported since Zabbix 3.4.0.| |StartProxyPollers|no|0-250|1|Number of pre-forked instances of [pollers for passive proxies](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.| |StartReportWriters|no|0-100|0|Number of pre-forked instances of [report writers](/manual/concepts/server#server_process_types).<br>If set to 0, scheduled report generation is disabled.<br>The report manager process is automatically started when a report writer is started.<br>This parameter is supported since Zabbix 5.4.0.| |StartSNMPTrapper|no|0-1|0|If set to 1, [SNMP trapper](/manual/concepts/server#server_process_types) process will be started.| |StartTimers|no|1-1000|1|Number of pre-forked instances of [timers](/manual/concepts/server#server_process_types).<br>Timers process maintenance periods.| |StartTrappers|no|0-1000|5|Number of pre-forked instances of [trappers](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.<br>Trappers accept incoming connections from Zabbix sender, active agents and active proxies.| |StartVMwareCollectors|no|0-250|0|Number of pre-forked [VMware collector](/manual/concepts/server#server_process_types) instances.| |StatsAllowedIP|no| | |List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of external Zabbix instances. Stats request will be accepted only from the addresses listed here. If this parameter is not set no stats requests will be accepted.<br>If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address. '0.0.0.0/0' can be used to allow any IPv4 address.<br>Example: StatsAllowedIP=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com<br>This parameter is supported since Zabbix 4.2.0.| |Timeout|no|1-30|3|Specifies how long we wait for agent, SNMP device or external check (in seconds).| |TLSCAFile|no| | |Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCertFile|no| | |Full pathname of a file containing the server certificate or certificate chain, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCipherAll|no| | |GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.<br>Example: TLS\_AES\_256\_GCM\_SHA384:TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherAll13|no| | |Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL::+SIGN-ALL:+CTYPE-X.509<br>Example for OpenSSL: EECDH+aRSA+AES128:RSA+aRSA+AES128:kECDHEPSK+AES128:kPSK+AES128<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherCert|no| | |GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509<br>Example for OpenSSL: EECDH+aRSA+AES128:RSA+aRSA+AES128<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherCert13|no| | |Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate-based encryption.<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherPSK|no| | |GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for PSK-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL<br>Example for OpenSSL: kECDHEPSK+AES128:kPSK+AES128<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherPSK13|no| | |Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for PSK-based encryption.<br>Example: TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>This parameter is supported since Zabbix 4.4.7.| |TLSCRLFile|no| | |Full pathname of a file containing revoked certificates. This parameter is used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSKeyFile|no| | |Full pathname of a file containing the server private key, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TmpDir|no| |/tmp|Temporary directory.| |TrapperTimeout|no|1-300|300|Specifies how many seconds trapper may spend processing new data.| |TrendCacheSize|no|128K-2G|4M|Size of trend cache, in bytes.<br>Shared memory size for storing trends data.| |TrendFunctionCacheSize|no|128K-2G|4M|Size of trend function cache, in bytes.<br>Shared memory size for caching calculated trend function data.| |UnavailableDelay|no|1-3600|60|How often host is checked for availability during the [unavailability](/manual/appendix/items/unreachability#unavailable_host) period, in seconds.| |UnreachableDelay|no|1-3600|15|How often host is checked for availability during the [unreachability](/manual/appendix/items/unreachability#unreachable_host) period, in seconds.| |UnreachablePeriod|no|1-3600|45|After how many seconds of [unreachability](/manual/appendix/items/unreachability#unreachable_host) treat a host as unavailable.| |User|no| |zabbix|Drop privileges to a specific, existing user on the system.<br>Only has effect if run as 'root' and AllowRoot is disabled.| |ValueCacheSize|no|0,128K-64G|8M|Size of history value cache, in bytes.<br>Shared memory size for caching item history data requests.<br>Setting to 0 disables value cache (not recommended).<br>When value cache runs out of the shared memory a warning message is written to the server log every 5 minutes.| |VaultDBPath|no| | |Vault path from where credentials for database will be retrieved by keys 'password' and 'username'.<br>Example: secret/zabbix/database<br>This option can only be used if DBUser and DBPassword are not specified.<br>This parameter is supported since Zabbix 5.2.0.| |VaultToken|no| | |Vault authentication token that should have been generated exclusively for Zabbix server with read-only permission to the paths specified in [Vault macros](/manual/config/macros/user_macros#configuration) and read-only permission to the path specified in the optional VaultDBPath configuration parameter.<br>It is an error if VaultToken and VAULT\_TOKEN environment variable are defined at the same time.<br>This parameter is supported since Zabbix 5.2.0.| |VaultURL|no| |https://127.0.0.1:8200|Vault server HTTP\[S\] URL. System-wide CA certificates directory will be used if SSLCALocation is not specified.<br>This parameter is supported since Zabbix 5.2.0.| |VMwareCacheSize|no|256K-2G|8M|Shared memory size for storing VMware data.<br>A VMware internal check zabbix\[vmware,buffer,...\] can be used to monitor the VMware cache usage (see [Internal checks](/manual/config/items/itemtypes/internal)).<br>Note that shared memory is not allocated if there are no vmware collector instances configured to start.| |VMwareFrequency|no|10-86400|60|Delay in seconds between data gathering from a single VMware service.<br>This delay should be set to the least update interval of any VMware monitoring item.| |VMwarePerfFrequency|no|10-86400|60|Delay in seconds between performance counter statistics retrieval from a single VMware service.<br>This delay should be set to the least update interval of any VMware monitoring [item](/manual/config/items/itemtypes/simple_checks/vmware_keys#footnotes) that uses VMware performance counters.| |VMwareTimeout|no|1-300|10|The maximum number of seconds vmware collector will wait for a response from VMware service (vCenter or ESX hypervisor).| |WebServiceURL|no| | |HTTP\[S\] URL to Zabbix web service in the format `<host:port>/report`. For example: `http://localhost:10053/report`<br>This parameter is supported since Zabbix 5.4.0.|  
ja	#### Parameters  |Parameter|Mandatory|Range|Default|Description| |---------|---------|-----|-------|-----------| |AlertScriptsPath|no|<|/usr/local/share/zabbix/alertscripts|Location of custom alert scripts (depends on compile-time installation variable *datadir*).| |AllowRoot|no|<|0|Allow the server to run as 'root'. If disabled and the server is started by 'root', the server will try to switch to the 'zabbix' user instead. Has no effect if started under a regular user.<br>0 - do not allow<br>1 - allow| |AllowUnsupportedDBVersions|no|<|0|Allow the server to work with unsupported database versions.<br>0 - do not allow<br>1 - allow| |CacheSize|no|128K-64G|8M|Size of configuration cache, in bytes.<br>Shared memory size for storing host, item and trigger data.| |CacheUpdateFrequency|no|1-3600|60|How often Zabbix will perform update of configuration cache, in seconds.<br>See also [runtime control](/manual/concepts/server#server_process) options.| |DBHost|no|<|localhost|Database host name.<br>In case of MySQL localhost or empty string results in using a socket. In case of PostgreSQL<br>only empty string results in attempt to use socket.<br>In case of [Oracle](/manual/appendix/install/oracle#connection_set_up) empty string results in using the Net Service Name connection method; in this case consider using the TNS\_ADMIN environment variable to specify the directory of the tnsnames.ora file.| |DBName|yes|<|<|Database name.<br>In case of [Oracle](/manual/appendix/install/oracle#connection_set_up) if the Net Service Name connection method is used, specify the service name from tnsnames.ora or set to empty string; set the TWO\_TASK environment variable if DBName is set to empty string.| |DBPassword|no|<|<|Database password.<br>Comment this line if no password is used.| |DBPort|no|1024-65535|<|Database port when not using local socket.<br>In case of [Oracle](/manual/appendix/install/oracle#connection_set_up) if the Net Service Name connection method is used this parameter will be ignored; the port number from the tnsnames.ora file will be used instead.| |DBSchema|no|<|<|Schema name. Used for PostgreSQL.| |DBSocket|no|<|<|Path to MySQL socket file.| |DBUser|no|<|<|Database user.| |DBTLSConnect|no|<|<|Setting this option enforces to use TLS connection to database:<br>*required* - connect using TLS<br>*verify\_ca* - connect using TLS and verify certificate<br>*verify\_full* - connect using TLS, verify certificate and verify that database identity specified by DBHost matches its certificate<br><br>On MySQL starting from 5.7.11 and PostgreSQL the following values are supported: "required", "verify\_ca", "verify\_full". On MariaDB starting from version 10.2.6 "required" and "verify\_full" values are supported.<br>By default not set to any option and the behavior depends on database configuration.<br><br>This parameter is supported since Zabbix 5.0.0.| |DBTLSCAFile|no<br>(yes, if DBTLSConnect set to one of: verify\_ca, verify\_full)|<|<|Full pathname of a file containing the top-level CA(s) certificates for database certificate verification.<br>This parameter is supported since Zabbix 5.0.0.| |DBTLSCertFile|no|<|<|Full pathname of file containing Zabbix server certificate for authenticating to database.<br>This parameter is supported since Zabbix 5.0.0.| |DBTLSKeyFile|no|<|<|Full pathname of file containing the private key for authenticating to database.<br>This parameter is supported since Zabbix 5.0.0.| |DBTLSCipher|no|<|<|The list of encryption ciphers that Zabbix server permits for TLS protocols up through TLSv1.2.<br>Supported only for MySQL.<br>This parameter is supported since Zabbix 5.0.0.| |DBTLSCipher13|no|<|<|The list of encryption ciphersuites that Zabbix server permits for TLSv1.3 protocol.<br>Supported only for MySQL, starting from version 8.0.16.<br>This parameter is supported since Zabbix 5.0.0.| |DebugLevel|no|0-5|3|Specifies debug level:<br>0 - basic information about starting and stopping of Zabbix processes<br>1 - critical information<br>2 - error information<br>3 - warnings<br>4 - for debugging (produces lots of information)<br>5 - extended debugging (produces even more information)<br>See also [runtime control](/manual/concepts/server#server_process) options.| |ExportDir|no|<|<|Directory for [real-time export](/manual/appendix/install/real_time_export) of events, history and trends in newline-delimited JSON format. If set, enables real-time export.<br>This parameter is supported since Zabbix 4.0.0.| |ExportFileSize|no|1M-1G|1G|Maximum size per export file in bytes. Only used for rotation if ExportDir is set.<br>This parameter is supported since Zabbix 4.0.0.| |ExportType|no|<|<|List of comma-delimited entity types (events, history, trends) for [real-time export](/manual/appendix/install/real_time_export) (all types by default). Valid only if ExportDir is set.<br>*Note* that if ExportType is specified, but ExportDir is not, then this is a configuration error and the server will not start.<br>e.g.:<br>ExportType=history,trends - export history and trends only<br>ExportType=events - export events only| |ExternalScripts|no|<|/usr/local/share/zabbix/externalscripts|Location of external scripts (depends on compile-time installation variable *datadir*).| |Fping6Location|no|<|/usr/sbin/fping6|Location of fping6.<br>Make sure that fping6 binary has root ownership and SUID flag set.<br>Make empty ("Fping6Location=") if your fping utility is capable to process IPv6 addresses.| |FpingLocation|no|<|/usr/sbin/fping|Location of fping.<br>Make sure that fping binary has root ownership and SUID flag set!| |HANodeName|no|<|<|The high availability cluster node name.<br>When empty the server is working in standalone mode and a node with empty name is created.| |HistoryCacheSize|no|128K-2G|16M|Size of history cache, in bytes.<br>Shared memory size for storing history data.| |HistoryIndexCacheSize|no|128K-2G|4M|Size of history index cache, in bytes.<br>Shared memory size for indexing history data stored in history cache.<br>The index cache size needs roughly 100 bytes to cache one item.<br>This parameter is supported since Zabbix 3.0.0.| |HistoryStorageDateIndex|no|<|0|Enable preprocessing of history values in history storage to store values in different indices based on date:<br>0 - disable<br>1 - enable| |HistoryStorageURL|no|<|<|History storage HTTP\[S\] URL.<br>This parameter is used for [Elasticsearch](/manual/appendix/install/elastic_search_setup) setup.| |HistoryStorageTypes|no|<|uint,dbl,str,log,text|Comma separated list of value types to be sent to the history storage.<br>This parameter is used for [Elasticsearch](/manual/appendix/install/elastic_search_setup) setup.| |HousekeepingFrequency|no|0-24|1|How often Zabbix will perform housekeeping procedure (in hours).<br>Housekeeping is removing outdated information from the database.<br>*Note*: To prevent housekeeper from being overloaded (for example, when history and trend periods are greatly reduced), no more than 4 times HousekeepingFrequency hours of outdated information are deleted in one housekeeping cycle, for each item. Thus, if HousekeepingFrequency is 1, no more than 4 hours of outdated information (starting from the oldest entry) will be deleted per cycle.<br>*Note*: To lower load on server startup housekeeping is postponed for 30 minutes after server start. Thus, if HousekeepingFrequency is 1, the very first housekeeping procedure after server start will run after 30 minutes, and will repeat with one hour delay thereafter.<br>Since Zabbix 3.0.0 it is possible to disable automatic housekeeping by setting HousekeepingFrequency to 0. In this case the housekeeping procedure can only be started by *housekeeper\_execute* runtime control option and the period of outdated information deleted in one housekeeping cycle is 4 times the period since the last housekeeping cycle, but not less than 4 hours and not greater than 4 days.<br>See also [runtime control](/manual/concepts/server#server_process) options.| |Include|no|<|<|You may include individual files or all files in a directory in the configuration file.<br>To only include relevant files in the specified directory, the asterisk wildcard character is supported for pattern matching. For example: `/absolute/path/to/config/files/*.conf`.<br>See [special notes](special_notes_include) about limitations.| |JavaGateway|no|<|<|IP address (or hostname) of Zabbix Java gateway.<br>Only required if Java pollers are started.| |JavaGatewayPort|no|1024-32767|10052|Port that Zabbix Java gateway listens on.| |ListenBacklog|no|0 - INT\_MAX|SOMAXCONN|The maximum number of pending connections in the TCP queue.<br>Default value is a hard-coded constant, which depends on the system.<br>Maximum supported value depends on the system, too high values may be silently truncated to the 'implementation-specified maximum'.| |ListenIP|no|<|0.0.0.0|List of comma delimited IP addresses that the trapper should listen on.<br>Trapper will listen on all network interfaces if this parameter is missing.| |ListenPort|no|1024-32767|10051|Listen port for trapper.| |LoadModule|no|<|<|Module to load at server startup. Modules are used to extend functionality of the server.<br>Formats:<br>LoadModule=<module.so><br>LoadModule=<path/module.so><br>LoadModule=</abs\_path/module.so><br>Either the module must be located in directory specified by LoadModulePath or the path must precede the module name. If the preceding path is absolute (starts with '/') then LoadModulePath is ignored.<br>It is allowed to include multiple LoadModule parameters.| |LoadModulePath|no|<|<|Full path to location of server modules.<br>Default depends on compilation options.| |LogFile|yes, if LogType is set to *file*, otherwise<br>no|<|<|Name of log file.| |LogFileSize|no|0-1024|1|Maximum size of log file in MB.<br>0 - disable automatic log rotation.<br>*Note*: If the log file size limit is reached and file rotation fails, for whatever reason, the existing log file is truncated and started anew.| |LogType|no|<|file|Log output type:<br>*file* - write log to file specified by LogFile parameter,<br>*system* - write log to syslog,<br>*console* - write log to standard output.<br>This parameter is supported since Zabbix 3.0.0.| |LogSlowQueries|no|0-3600000|0|How long a database query may take before being logged (in milliseconds).<br>0 - don't log slow queries.<br>This option becomes enabled starting with DebugLevel=3.| |MaxHousekeeperDelete|no|0-1000000|5000|No more than 'MaxHousekeeperDelete' rows (corresponding to \[tablename\], \[field\], \[value\]) will be deleted per one task in one housekeeping cycle.<br>If set to 0 then no limit is used at all. In this case you must know what you are doing, so as not to [overload the database!](zabbix_server#footnotes) **^[2](zabbix_server#footnotes)^**<br>This parameter applies only to deleting history and trends of already deleted items.| |NodeAddress|no|<|<|IP or hostname with optional port to override how the frontend should connect to the server.<br>Format: <address>\[:port\]<br>The priority of addresses used by the frontend to specify the server address is: NodeAddress (1); ListenIP (if not 0.0.0.0 or ::) (2); localhost (default) (3)<br>See also: HANodeName parameter| |PidFile|no|<|/tmp/zabbix\_server.pid|Name of PID file.| |ProxyConfigFrequency|no|1-604800|3600|How often Zabbix server sends configuration data to a Zabbix proxy in seconds. Used only for proxies in a passive mode.| |ProxyDataFrequency|no|1-3600|1|How often Zabbix server requests history data from a Zabbix proxy in seconds. Used only for proxies in a passive mode.| |SNMPTrapperFile|no|<|/tmp/zabbix\_traps.tmp|Temporary file used for passing data from SNMP trap daemon to the server.<br>Must be the same as in zabbix\_trap\_receiver.pl or SNMPTT configuration file.| |SocketDir|no|<|/tmp|Directory to store IPC sockets used by internal Zabbix services.<br>This parameter is supported since Zabbix 3.4.0.| |SourceIP|no|<|<|Source IP address for:<br>- outgoing connections to Zabbix proxy and Zabbix agent;<br>- agentless connections (VMware, SSH, JMX, SNMP, Telnet and simple checks);<br>- HTTP agent connections;<br>- script item JavaScript HTTP requests;<br>- preprocessing JavaScript HTTP requests;<br>- sending notification emails (connections to SMTP server);<br>- webhook notifications (JavaScript HTTP connections);<br>- connections to the Vault| |SSHKeyLocation|no|<|<|Location of public and private keys for SSH checks and actions| |SSLCertLocation|no|<|<|Location of SSL client certificate files for client authentication.<br>This parameter is used in web monitoring only.| |SSLKeyLocation|no|<|<|Location of SSL private key files for client authentication.<br>This parameter is used in web monitoring only.| |SSLCALocation|no|<|<|Override the location of certificate authority (CA) files for SSL server certificate verification. If not set, system-wide directory will be used.<br>Note that the value of this parameter will be set as libcurl option CURLOPT\_CAPATH. For libcurl versions before 7.42.0, this only has effect if libcurl was compiled to use OpenSSL. For more information see [cURL web page](http://curl.haxx.se/libcurl/c/CURLOPT_CAPATH.html).<br>This parameter is used in web monitoring since Zabbix 2.4.0 and in SMTP authentication since Zabbix 3.0.0.| |StartAlerters|no|1-100|3|Number of pre-forked instances of [alerters](/manual/concepts/server#server_process_types).<br>This parameter is supported since Zabbix 3.4.0.| |StartDBSyncers|no|1-100|4|Number of pre-forked instances of [history syncers](/manual/concepts/server#server_process_types).<br>*Note*: Be careful when changing this value, increasing it may do more harm than good. Roughly, the default value should be enough to handle up to 4000 NVPS.| |StartDiscoverers|no|0-250|1|Number of pre-forked instances of [discoverers](/manual/concepts/server#server_process_types).| |StartEscalators|no|1-100|1|Number of pre-forked instances of [escalators](/manual/concepts/server#server_process_types).<br>This parameter is supported since Zabbix 3.0.0.| |StartHistoryPollers|no|0-1000|5|Number of pre-forked instances of [history pollers](/manual/concepts/server#server_process_types).<br>This parameter is supported since Zabbix 5.4.0.| |StartHTTPPollers|no|0-1000|1|Number of pre-forked instances of [HTTP pollers](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.| |StartIPMIPollers|no|0-1000|0|Number of pre-forked instances of [IPMI pollers](/manual/concepts/server#server_process_types).| |StartJavaPollers|no|0-1000|0|Number of pre-forked instances of [Java pollers](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.| |StartLLDProcessors|no|1-100|2|Number of pre-forked instances of low-level discovery (LLD) [workers](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.<br>The LLD manager process is automatically started when an LLD worker is started.<br>This parameter is supported since Zabbix 4.2.0.| |StartPingers|no|0-1000|1|Number of pre-forked instances of [ICMP pingers](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.| |StartPollersUnreachable|no|0-1000|1|Number of pre-forked instances of [pollers for unreachable hosts](/manual/concepts/server#server_process_types) (including IPMI and Java)**^[1](zabbix_server#footnotes)^**.<br>At least one poller for unreachable hosts must be running if regular, IPMI or Java pollers are started.| |StartPollers|no|0-1000|5|Number of pre-forked instances of [pollers](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.| |StartPreprocessors|no|1-1000|3|Number of pre-forked instances of preprocessing [workers](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.<br>The preprocessing manager process is automatically started when a preprocessor worker is started.<br>This parameter is supported since Zabbix 3.4.0.| |StartProxyPollers|no|0-250|1|Number of pre-forked instances of [pollers for passive proxies](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.| |StartReportWriters|no|0-100|0|Number of pre-forked instances of [report writers](/manual/concepts/server#server_process_types).<br>If set to 0, scheduled report generation is disabled.<br>The report manager process is automatically started when a report writer is started.<br>This parameter is supported since Zabbix 5.4.0.| |StartSNMPTrapper|no|0-1|0|If set to 1, [SNMP trapper](/manual/concepts/server#server_process_types) process will be started.| |StartTimers|no|1-1000|1|Number of pre-forked instances of [timers](/manual/concepts/server#server_process_types).<br>Timers process maintenance periods.| |StartTrappers|no|0-1000|5|Number of pre-forked instances of [trappers](/manual/concepts/server#server_process_types)**^[1](zabbix_server#footnotes)^**.<br>Trappers accept incoming connections from Zabbix sender, active agents and active proxies.| |StartVMwareCollectors|no|0-250|0|Number of pre-forked [VMware collector](/manual/concepts/server#server_process_types) instances.| |StatsAllowedIP|no|<|<|List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of external Zabbix instances. Stats request will be accepted only from the addresses listed here. If this parameter is not set no stats requests will be accepted.<br>If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address. '0.0.0.0/0' can be used to allow any IPv4 address.<br>Example: StatsAllowedIP=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com<br>This parameter is supported since Zabbix 4.2.0.| |Timeout|no|1-30|3|Specifies how long we wait for agent, SNMP device or external check (in seconds).| |TLSCAFile|no|<|<|Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCertFile|no|<|<|Full pathname of a file containing the server certificate or certificate chain, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCipherAll|no|<|<|GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.<br>Example: TLS\_AES\_256\_GCM\_SHA384:TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherAll13|no|<|<|Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL::+SIGN-ALL:+CTYPE-X.509<br>Example for OpenSSL: EECDH+aRSA+AES128:RSA+aRSA+AES128:kECDHEPSK+AES128:kPSK+AES128<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherCert|no|<|<|GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509<br>Example for OpenSSL: EECDH+aRSA+AES128:RSA+aRSA+AES128<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherCert13|no|<|<|Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate-based encryption.<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherPSK|no|<|<|GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for PSK-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL<br>Example for OpenSSL: kECDHEPSK+AES128:kPSK+AES128<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherPSK13|no|<|<|Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for PSK-based encryption.<br>Example: TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>This parameter is supported since Zabbix 4.4.7.| |TLSCRLFile|no|<|<|Full pathname of a file containing revoked certificates. This parameter is used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSKeyFile|no|<|<|Full pathname of a file containing the server private key, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TmpDir|no|<|/tmp|Temporary directory.| |TrapperTimeout|no|1-300|300|Specifies how many seconds trapper may spend processing new data.| |TrendCacheSize|no|128K-2G|4M|Size of trend cache, in bytes.<br>Shared memory size for storing trends data.| |TrendFunctionCacheSize|no|128K-2G|4M|Size of trend function cache, in bytes.<br>Shared memory size for caching calculated trend function data.| |UnavailableDelay|no|1-3600|60|How often host is checked for availability during the [unavailability](/manual/appendix/items/unreachability#unavailable_host) period, in seconds.| |UnreachableDelay|no|1-3600|15|How often host is checked for availability during the [unreachability](/manual/appendix/items/unreachability#unreachable_host) period, in seconds.| |UnreachablePeriod|no|1-3600|45|After how many seconds of [unreachability](/manual/appendix/items/unreachability#unreachable_host) treat a host as unavailable.| |User|no|<|zabbix|Drop privileges to a specific, existing user on the system.<br>Only has effect if run as 'root' and AllowRoot is disabled.| |ValueCacheSize|no|0,128K-64G|8M|Size of history value cache, in bytes.<br>Shared memory size for caching item history data requests.<br>Setting to 0 disables value cache (not recommended).<br>When value cache runs out of the shared memory a warning message is written to the server log every 5 minutes.| |VaultDBPath|no|<|<|Vault path from where credentials for database will be retrieved by keys 'password' and 'username'.<br>Example: secret/zabbix/database<br>This option can only be used if DBUser and DBPassword are not specified.<br>This parameter is supported since Zabbix 5.2.0.| |VaultToken|no|<|<|Vault authentication token that should have been generated exclusively for Zabbix server with read-only permission to the paths specified in [Vault macros](/manual/config/macros/user_macros#configuration) and read-only permission to the path specified in the optional VaultDBPath configuration parameter.<br>It is an error if VaultToken and VAULT\_TOKEN environment variable are defined at the same time.<br>This parameter is supported since Zabbix 5.2.0.| |VaultURL|no|<|https://127.0.0.1:8200|Vault server HTTP\[S\] URL. System-wide CA certificates directory will be used if SSLCALocation is not specified.<br>This parameter is supported since Zabbix 5.2.0.| |VMwareCacheSize|no|256K-2G|8M|Shared memory size for storing VMware data.<br>A VMware internal check zabbix\[vmware,buffer,...\] can be used to monitor the VMware cache usage (see [Internal checks](/manual/config/items/itemtypes/internal)).<br>Note that shared memory is not allocated if there are no vmware collector instances configured to start.| |VMwareFrequency|no|10-86400|60|Delay in seconds between data gathering from a single VMware service.<br>This delay should be set to the least update interval of any VMware monitoring item.| |VMwarePerfFrequency|no|10-86400|60|Delay in seconds between performance counter statistics retrieval from a single VMware service.<br>This delay should be set to the least update interval of any VMware monitoring [item](/manual/config/items/itemtypes/simple_checks/vmware_keys#footnotes) that uses VMware performance counters.| |VMwareTimeout|no|1-300|10|The maximum number of seconds vmware collector will wait for a response from VMware service (vCenter or ESX hypervisor).| |WebServiceURL|no|<|<|HTTP\[S\] URL to Zabbix web service in the format `<host:port>/report`. For example: `http://localhost:10053/report`<br>This parameter is supported since Zabbix 5.4.0.|  

en-us	#### Parameters  |Parameter|Mandatory|Range|Default|Description| |---------|---------|-----|-------|-----------| |Alias|no| | |Sets an alias for an item key. It can be used to substitute long and complex item key with a smaller and simpler one.<br>Multiple *Alias* parameters may be present. Multiple parameters with the same *Alias* key are allowed.<br>Different *Alias* keys may reference the same item key.<br>Aliases can be used in *HostMetadataItem* but not in *HostnameItem* or *PerfCounter* parameters.<br><br>Examples:<br><br>1. Retrieving paging file usage in percents from the server.<br>Alias=pg\_usage:perf\_counter\[\\Paging File(\_Total)\\% Usage\]<br>Now shorthand key **pg\_usage** may be used to retrieve data.<br><br>2. Getting CPU load with default and custom parameters.<br>Alias=cpu.load:system.cpu.load<br>Alias=cpu.load\[\*\]:system.cpu.load\[\*\]<br>This allows use **cpu.load** key to get CPU utilization percentage with default parameters as well as use **cpu.load\[percpu,avg15\]** to get specific data about CPU load.<br><br>3. Running multiple [low-level discovery](/manual/discovery/low_level_discovery) rules processing the same discovery items.<br>Alias=vfs.fs.discovery\[\*\]:vfs.fs.discovery<br>Now it is possible to set up several discovery rules using **vfs.fs.discovery** with different parameters for each rule, e.g., **vfs.fs.discovery\[foo\]**, **vfs.fs.discovery\[bar\]**, etc.| |AllowKey|no| | |Allow execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "\*" character to match any number of any characters.<br>Multiple key matching rules may be defined in combination with DenyKey. The parameters are processed one by one according to their appearance order.<br>This parameter is supported since Zabbix 5.0.0.<br>See also: [Restricting agent checks](/manual/config/items/restrict_checks).| |BufferSend|no|1-3600|5|Do not keep data longer than N seconds in buffer.| |BufferSize|no|2-65535|100|Maximum number of values in a memory buffer. The agent will send<br>all collected data to Zabbix server or proxy if the buffer is full.| |DebugLevel|no|0-5|3|Specifies debug level:<br>0 - basic information about starting and stopping of Zabbix processes<br>1 - critical information<br>2 - error information<br>3 - warnings<br>4 - for debugging (produces lots of information)<br>5 - extended debugging (produces even more information)| |DenyKey|no| | |Deny execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "\*" character to match any number of any characters.<br>Multiple key matching rules may be defined in combination with AllowKey. The parameters are processed one by one according to their appearance order.<br>This parameter is supported since Zabbix 5.0.0.<br>See also: [Restricting agent checks](/manual/config/items/restrict_checks).| |EnableRemoteCommands|no| |0|Whether remote commands from Zabbix server are allowed. This parameter is **deprecated**, use AllowKey=system.run\[\*\] or DenyKey=system.run\[\*\] instead<br>It is internal alias for AllowKey/DenyKey parameters depending on value: 0 - DenyKey=system.run\[\*\]<br>1 - AllowKey=system.run\[\*\].| |HostInterface|no|0-255 characters| |Optional parameter that defines host interface.<br>Host interface is used at host autoregistration process.<br>An agent will issue an error and not start if the value is over the limit of 255 characters.<br>If not defined, value will be acquired from HostInterfaceItem.<br>Supported since Zabbix 4.4.0.| |HostInterfaceItem|no| | |Optional parameter that defines an item used for getting host interface.<br>Host interface is used at host autoregistration process.<br>During an autoregistration request an agent will log a warning message if the value returned by specified item is over limit of 255 characters.<br>This option is only used when HostInterface is not defined.<br>Supported since Zabbix 4.4.0.| |HostMetadata|no|0-255 characters| |Optional parameter that defines host metadata. Host metadata is used only at host autoregistration process (active agent).<br>If not defined, the value will be acquired from HostMetadataItem.<br>An agent will issue an error and not start if the specified value is over the limit or a non-UTF-8 string.| |HostMetadataItem|no| | |Optional parameter that defines a *Zabbix agent* item used for getting host metadata. This option is only used when HostMetadata is not defined.<br>Supports UserParameters, performance counters and aliases. Supports *system.run\[\]* regardless of *EnableRemoteCommands* value.<br>HostMetadataItem value is retrieved on each autoregistration attempt and is used only at host autoregistration process (active agent).<br>During an autoregistration request an agent will log a warning message if the value returned by the specified item is over the limit of 255 characters.<br>The value returned by the item must be a UTF-8 string otherwise it will be ignored.| |Hostname|no| |Set by HostnameItem|List of comma-delimited unique, case-sensitive hostnames.<br>Required for active checks and must match hostnames as configured on the server. Value is acquired from HostnameItem if undefined.<br>Allowed characters: alphanumeric, '.', ' ', '\_' and '-'.<br>Maximum length: 128 characters per hostname, 2048 characters for the entire line.| |HostnameItem|no| |system.hostname|Optional parameter that defines a *Zabbix agent* item used for getting host name. This option is only used when Hostname is not defined.<br>Does not support UserParameters, performance counters or aliases, but does support *system.run\[\]* regardless of *EnableRemoteCommands* value.<br>The output length is limited to 512KB.<br>See also a [more detailed description](/manual/appendix/install/windows_agent#configuration).| |Include|no| | |You may include individual files or all files in a directory in the configuration file.<br>To only include relevant files in the specified directory, the asterisk wildcard character is supported for pattern matching. For example: `/absolute/path/to/config/files/*.conf`.<br>See [special notes](special_notes_include) about limitations.| |ListenBacklog|no|0 - INT\_MAX|SOMAXCONN|The maximum number of pending connections in the TCP queue.<br>Default value is a hard-coded constant, which depends on the system.<br>Maximum supported value depends on the system, too high values may be silently truncated to the 'implementation-specified maximum'.| |ListenIP|no| |0.0.0.0|List of comma-delimited IP addresses that the agent should listen on.| |ListenPort|no|1024-32767|10050|Agent will listen on this port for connections from the server.| |LogFile|yes, if LogType is set to *file*, otherwise<br>no| |C:\\zabbix\_agentd.log|Name of the agent log file.| |LogFileSize|no|0-1024|1|Maximum size of log file in MB.<br>0 - disable automatic log rotation.<br>*Note*: If the log file size limit is reached and file rotation fails, for whatever reason, the existing log file is truncated and started anew.| |LogType|no| |file|Log output type:<br>*file* - write log to file specified by LogFile parameter,<br>*system* - write log Windows Event Log,<br>*console* - write log to standard output.<br>This parameter is supported since Zabbix 3.0.0.| |LogRemoteCommands|no| |0|Enable logging of executed shell commands as warnings.<br>0 - disabled<br>1 - enabled| |MaxLinesPerSecond|no|1-1000|20|Maximum number of new lines the agent will send per second to Zabbix server<br>or proxy processing 'log', 'logrt' and 'eventlog' active checks.<br>The provided value will be overridden by the parameter 'maxlines',<br>provided in 'log', 'logrt' or 'eventlog' item keys.<br>*Note*: Zabbix will process 10 times more new lines than set in *MaxLinesPerSecond* to seek the required string in log items.| |PerfCounter|no| | |Defines a new parameter <parameter\_name> which is an average value for system performance counter <perf\_counter\_path> for the specified time period <period> (in seconds).<br>Syntax: <parameter\_name>,"<perf\_counter\_path>",<period><br>For example, if you wish to receive average number of processor interrupts per second for last minute, you can define a new parameter "interrupts" as the following:<br>PerfCounter = interrupts,"\\Processor(0)\\Interrupts/sec",60<br>Please note double quotes around performance counter path.<br>The parameter name (interrupts) is to be used as the item key when creating an item.<br>Samples for calculating average value will be taken every second.<br>You may run "typeperf -qx" to get list of all performance counters available in Windows.| |PerfCounterEn|no| | |Defines a new parameter <parameter\_name> which is an average value for system performance counter <perf\_counter\_path> for the specified time period <period> (in seconds).<br>Syntax: <parameter\_name>,"<perf\_counter\_path>",<period><br>Compared to PerfCounter, perfcounter paths must be in English.<br>Supported only on **Windows Server 2008/Vista** and above.<br>For example, if you wish to receive average number of processor interrupts per second for last minute, you can define a new parameter "interrupts" as the following:<br>PerfCounterEn = interrupts,"\\Processor(0)\\Interrupts/sec",60<br>Please note double quotes around performance counter path.<br>The parameter name (interrupts) is to be used as the item key when creating an item.<br>Samples for calculating average value will be taken every second.<br>You can find the list of English strings by viewing the following registry key: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009`.<br>This parameter is supported since Zabbix 4.0.13 and 4.2.7.| |RefreshActiveChecks|no|60-3600|120|How often list of active checks is refreshed, in seconds.<br>Note that after failing to refresh active checks the next refresh will be attempted after 60 seconds.| |Server|yes, if StartAgents is not explicitly set to 0| | |List of comma delimited IP addresses, optionally in CIDR notation, or hostnames of Zabbix servers.<br>Incoming connections will be accepted only from the hosts listed here.<br>If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address.<br>'0.0.0.0/0' can be used to allow any IPv4 address.<br>Note, that "IPv4-compatible IPv6 addresses" (0000::/96 prefix) are supported but deprecated by [RFC4291](https://tools.ietf.org/html/rfc4291#section-2.5.5).<br>Example: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.domain<br>Spaces are allowed.|  |   |   |   |   |   | |---|---|---|---|---| |ServerActive|no|(\*)| |List of comma-delimited IP address or DNS name (address:port) pairs or clusters (address:port;address2:port) of Zabbix servers and Zabbix proxies for active checks.<br>Cluster nodes must be separated by a semicolon.<br>Multiple comma-delimited addresses can be provided to use several independent Zabbix servers in parallel. Spaces are allowed.<br>If port is not specified, default port is used.<br>IPv6 addresses must be enclosed in square brackets if port for that host is specified.<br>If port is not specified, square brackets for IPv6 addresses are optional.<br>If this parameter is not specified, active checks are disabled.<br>Example for multiple servers:<br>ServerActive=127.0.0.1:20051,zabbix.domain,\[::1\]:30051,::1,\[12fc::1\]<br>Example for high availability:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051;zabbix.cluster.node3<br>Example for high availability with two clusters and one server:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051,zabbix.cluster2.node1;zabbix.cluster2.node2,zabbix.domain| |SourceIP|no| | |Source IP address for:<br>- outgoing connections to Zabbix server or Zabbix proxy;<br>- making connections while executing some items (web.page.get, net.tcp.port, etc.)| |StartAgents|no|0-63 (\*)|3|Number of pre-forked instances of zabbix\_agentd that process passive checks.<br>If set to 0, disables passive checks and the agent will not listen on any TCP port.| |Timeout|no|1-30|3|Spend no more than Timeout seconds on processing| |TLSAccept|yes, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no| | |What incoming connections to accept. Used for a passive checks. Multiple values can be specified, separated by comma:<br>*unencrypted* - accept connections without encryption (default)<br>*psk* - accept connections with TLS and a pre-shared key (PSK)<br>*cert* - accept connections with TLS and a certificate<br>This parameter is supported since Zabbix 3.0.0.| |TLSCAFile|no| | |Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCertFile|no| | |Full pathname of a file containing the agent certificate or certificate chain, used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSConnect|yes, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no| | |How the agent should connect to Zabbix server or proxy. Used for active checks. Only one value can be specified:<br>*unencrypted* - connect without encryption (default)<br>*psk* - connect using TLS and a pre-shared key (PSK)<br>*cert* - connect using TLS and a certificate<br>This parameter is supported since Zabbix 3.0.0.| |TLSCRLFile|no| | |Full pathname of a file containing revoked certificates. This parameter is used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSKeyFile|no| | |Full pathname of a file containing the agent private key used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSPSKFile|no| | |Full pathname of a file containing the agent pre-shared key used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSPSKIdentity|no| | |Pre-shared key identity string, used for encrypted communications with Zabbix server.<br>This parameter is supported since Zabbix 3.0.0.| |TLSServerCertIssuer|no| | |Allowed server (proxy) certificate issuer.<br>This parameter is supported since Zabbix 3.0.0.| |TLSServerCertSubject|no| | |Allowed server (proxy) certificate subject.<br>This parameter is supported since Zabbix 3.0.0.| |UnsafeUserParameters|no|0-1|0|Allow all characters to be passed in arguments to user-defined parameters.<br>0 - do not allow<br>1 - allow<br>The following characters are not allowed:<br>\\ ' " \` \* ? \[ \] { } \~ $ ! & ; ( ) < > \| \# @<br>Additionally, newline characters are not allowed.| |UserParameter|no| | |User-defined parameter to monitor. There can be several user-defined parameters.<br>Format: UserParameter=<key>,<shell command><br>Note that shell command must not return empty string or EOL only.<br>Shell commands may have relative paths, if UserParameterDir parameter is specified.<br>Examples:<br>UserParameter=system.test,who\|wc -l<br>UserParameter=check\_cpu,./custom\_script.sh| |UserParameterDir|no| | |Default search path for UserParameter commands. If used, the agent will change its working directory to the one specified here before executing a command. Thereby, UserParameter commands can have a relative `./` prefix instead of a full path.<br>Only one entry is allowed.<br>Example: UserParameterDir=/opt/myscripts|  ::: noteclassic  (\*) The number of active servers listed in ServerActive plus the number of pre-forked instances for passive checks specified in StartAgents must be less than 64. :::  
ja	#### Parameters  |Parameter|Mandatory|Range|Default|Description| |---------|---------|-----|-------|-----------| |Alias|no|<|<|Sets an alias for an item key. It can be used to substitute long and complex item key with a smaller and simpler one.<br>Multiple *Alias* parameters may be present. Multiple parameters with the same *Alias* key are allowed.<br>Different *Alias* keys may reference the same item key.<br>Aliases can be used in *HostMetadataItem* but not in *HostnameItem* or *PerfCounter* parameters.<br><br>Examples:<br><br>1. Retrieving paging file usage in percents from the server.<br>Alias=pg\_usage:perf\_counter\[\\Paging File(\_Total)\\% Usage\]<br>Now shorthand key **pg\_usage** may be used to retrieve data.<br><br>2. Getting CPU load with default and custom parameters.<br>Alias=cpu.load:system.cpu.load<br>Alias=cpu.load\[\*\]:system.cpu.load\[\*\]<br>This allows use **cpu.load** key to get CPU utilization percentage with default parameters as well as use **cpu.load\[percpu,avg15\]** to get specific data about CPU load.<br><br>3. Running multiple [low-level discovery](/manual/discovery/low_level_discovery) rules processing the same discovery items.<br>Alias=vfs.fs.discovery\[\*\]:vfs.fs.discovery<br>Now it is possible to set up several discovery rules using **vfs.fs.discovery** with different parameters for each rule, e.g., **vfs.fs.discovery\[foo\]**, **vfs.fs.discovery\[bar\]**, etc.| |AllowKey|no|<|<|Allow execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "\*" character to match any number of any characters.<br>Multiple key matching rules may be defined in combination with DenyKey. The parameters are processed one by one according to their appearance order.<br>This parameter is supported since Zabbix 5.0.0.<br>See also: [Restricting agent checks](/manual/config/items/restrict_checks).| |BufferSend|no|1-3600|5|Do not keep data longer than N seconds in buffer.| |BufferSize|no|2-65535|100|Maximum number of values in a memory buffer. The agent will send<br>all collected data to Zabbix server or proxy if the buffer is full.| |DebugLevel|no|0-5|3|Specifies debug level:<br>0 - basic information about starting and stopping of Zabbix processes<br>1 - critical information<br>2 - error information<br>3 - warnings<br>4 - for debugging (produces lots of information)<br>5 - extended debugging (produces even more information)| |DenyKey|no|<|<|Deny execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "\*" character to match any number of any characters.<br>Multiple key matching rules may be defined in combination with AllowKey. The parameters are processed one by one according to their appearance order.<br>This parameter is supported since Zabbix 5.0.0.<br>See also: [Restricting agent checks](/manual/config/items/restrict_checks).| |EnableRemoteCommands|no|<|0|Whether remote commands from Zabbix server are allowed. This parameter is **deprecated**, use AllowKey=system.run\[\*\] or DenyKey=system.run\[\*\] instead<br>It is internal alias for AllowKey/DenyKey parameters depending on value: 0 - DenyKey=system.run\[\*\]<br>1 - AllowKey=system.run\[\*\].| |HostInterface|no|0-255 characters|<|Optional parameter that defines host interface.<br>Host interface is used at host autoregistration process.<br>An agent will issue an error and not start if the value is over the limit of 255 characters.<br>If not defined, value will be acquired from HostInterfaceItem.<br>Supported since Zabbix 4.4.0.| |HostInterfaceItem|no|<|<|Optional parameter that defines an item used for getting host interface.<br>Host interface is used at host autoregistration process.<br>During an autoregistration request an agent will log a warning message if the value returned by specified item is over limit of 255 characters.<br>This option is only used when HostInterface is not defined.<br>Supported since Zabbix 4.4.0.| |HostMetadata|no|0-255 characters|<|Optional parameter that defines host metadata. Host metadata is used only at host autoregistration process (active agent).<br>If not defined, the value will be acquired from HostMetadataItem.<br>An agent will issue an error and not start if the specified value is over the limit or a non-UTF-8 string.| |HostMetadataItem|no|<|<|Optional parameter that defines a *Zabbix agent* item used for getting host metadata. This option is only used when HostMetadata is not defined.<br>Supports UserParameters, performance counters and aliases. Supports *system.run\[\]* regardless of *EnableRemoteCommands* value.<br>HostMetadataItem value is retrieved on each autoregistration attempt and is used only at host autoregistration process (active agent).<br>During an autoregistration request an agent will log a warning message if the value returned by the specified item is over the limit of 255 characters.<br>The value returned by the item must be a UTF-8 string otherwise it will be ignored.| |Hostname|no|<|Set by HostnameItem|List of comma-delimited unique, case-sensitive hostnames.<br>Required for active checks and must match hostnames as configured on the server. Value is acquired from HostnameItem if undefined.<br>Allowed characters: alphanumeric, '.', ' ', '\_' and '-'.<br>Maximum length: 128 characters per hostname, 2048 characters for the entire line.| |HostnameItem|no|<|system.hostname|Optional parameter that defines a *Zabbix agent* item used for getting host name. This option is only used when Hostname is not defined.<br>Does not support UserParameters, performance counters or aliases, but does support *system.run\[\]* regardless of *EnableRemoteCommands* value.<br>The output length is limited to 512KB.<br>See also a [more detailed description](/manual/appendix/install/windows_agent#configuration).| |Include|no|<|<|You may include individual files or all files in a directory in the configuration file.<br>To only include relevant files in the specified directory, the asterisk wildcard character is supported for pattern matching. For example: `/absolute/path/to/config/files/*.conf`.<br>See [special notes](special_notes_include) about limitations.| |ListenBacklog|no|0 - INT\_MAX|SOMAXCONN|The maximum number of pending connections in the TCP queue.<br>Default value is a hard-coded constant, which depends on the system.<br>Maximum supported value depends on the system, too high values may be silently truncated to the 'implementation-specified maximum'.| |ListenIP|no|<|0.0.0.0|List of comma-delimited IP addresses that the agent should listen on.| |ListenPort|no|1024-32767|10050|Agent will listen on this port for connections from the server.| |LogFile|yes, if LogType is set to *file*, otherwise<br>no|<|C:\\zabbix\_agentd.log|Name of the agent log file.| |LogFileSize|no|0-1024|1|Maximum size of log file in MB.<br>0 - disable automatic log rotation.<br>*Note*: If the log file size limit is reached and file rotation fails, for whatever reason, the existing log file is truncated and started anew.| |LogType|no|<|file|Log output type:<br>*file* - write log to file specified by LogFile parameter,<br>*system* - write log Windows Event Log,<br>*console* - write log to standard output.<br>This parameter is supported since Zabbix 3.0.0.| |LogRemoteCommands|no|<|0|Enable logging of executed shell commands as warnings.<br>0 - disabled<br>1 - enabled| |MaxLinesPerSecond|no|1-1000|20|Maximum number of new lines the agent will send per second to Zabbix server<br>or proxy processing 'log', 'logrt' and 'eventlog' active checks.<br>The provided value will be overridden by the parameter 'maxlines',<br>provided in 'log', 'logrt' or 'eventlog' item keys.<br>*Note*: Zabbix will process 10 times more new lines than set in *MaxLinesPerSecond* to seek the required string in log items.| |PerfCounter|no|<|<|Defines a new parameter <parameter\_name> which is an average value for system performance counter <perf\_counter\_path> for the specified time period <period> (in seconds).<br>Syntax: <parameter\_name>,"<perf\_counter\_path>",<period><br>For example, if you wish to receive average number of processor interrupts per second for last minute, you can define a new parameter "interrupts" as the following:<br>PerfCounter = interrupts,"\\Processor(0)\\Interrupts/sec",60<br>Please note double quotes around performance counter path.<br>The parameter name (interrupts) is to be used as the item key when creating an item.<br>Samples for calculating average value will be taken every second.<br>You may run "typeperf -qx" to get list of all performance counters available in Windows.| |PerfCounterEn|no|<|<|Defines a new parameter <parameter\_name> which is an average value for system performance counter <perf\_counter\_path> for the specified time period <period> (in seconds).<br>Syntax: <parameter\_name>,"<perf\_counter\_path>",<period><br>Compared to PerfCounter, perfcounter paths must be in English.<br>Supported only on **Windows Server 2008/Vista** and above.<br>For example, if you wish to receive average number of processor interrupts per second for last minute, you can define a new parameter "interrupts" as the following:<br>PerfCounterEn = interrupts,"\\Processor(0)\\Interrupts/sec",60<br>Please note double quotes around performance counter path.<br>The parameter name (interrupts) is to be used as the item key when creating an item.<br>Samples for calculating average value will be taken every second.<br>You can find the list of English strings by viewing the following registry key: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009`.<br>This parameter is supported since Zabbix 4.0.13 and 4.2.7.| |RefreshActiveChecks|no|60-3600|120|How often list of active checks is refreshed, in seconds.<br>Note that after failing to refresh active checks the next refresh will be attempted after 60 seconds.| |Server|yes, if StartAgents is not explicitly set to 0|<|<|List of comma delimited IP addresses, optionally in CIDR notation, or hostnames of Zabbix servers.<br>Incoming connections will be accepted only from the hosts listed here.<br>If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address.<br>'0.0.0.0/0' can be used to allow any IPv4 address.<br>Note, that "IPv4-compatible IPv6 addresses" (0000::/96 prefix) are supported but deprecated by [RFC4291](https://tools.ietf.org/html/rfc4291#section-2.5.5).<br>Example: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.domain<br>Spaces are allowed.|  |   |   |   |   |   | |---|---|---|---|---| |ServerActive|no|(\*)|<|List of comma-delimited IP address or DNS name (address:port) pairs or clusters (address:port;address2:port) of Zabbix servers and Zabbix proxies for active checks.<br>Cluster nodes must be separated by a semicolon.<br>Multiple comma-delimited addresses can be provided to use several independent Zabbix servers in parallel. Spaces are allowed.<br>If port is not specified, default port is used.<br>IPv6 addresses must be enclosed in square brackets if port for that host is specified.<br>If port is not specified, square brackets for IPv6 addresses are optional.<br>If this parameter is not specified, active checks are disabled.<br>Example for multiple servers:<br>ServerActive=127.0.0.1:20051,zabbix.domain,\[::1\]:30051,::1,\[12fc::1\]<br>Example for high availability:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051;zabbix.cluster.node3<br>Example for high availability with two clusters and one server:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051,zabbix.cluster2.node1;zabbix.cluster2.node2,zabbix.domain| |SourceIP|no|<|<|Source IP address for:<br>- outgoing connections to Zabbix server or Zabbix proxy;<br>- making connections while executing some items (web.page.get, net.tcp.port, etc.)| |StartAgents|no|0-63 (\*)|3|Number of pre-forked instances of zabbix\_agentd that process passive checks.<br>If set to 0, disables passive checks and the agent will not listen on any TCP port.| |Timeout|no|1-30|3|Spend no more than Timeout seconds on processing| |TLSAccept|yes, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no|<|<|What incoming connections to accept. Used for a passive checks. Multiple values can be specified, separated by comma:<br>*unencrypted* - accept connections without encryption (default)<br>*psk* - accept connections with TLS and a pre-shared key (PSK)<br>*cert* - accept connections with TLS and a certificate<br>This parameter is supported since Zabbix 3.0.0.| |TLSCAFile|no|<|<|Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCertFile|no|<|<|Full pathname of a file containing the agent certificate or certificate chain, used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSConnect|yes, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no|<|<|How the agent should connect to Zabbix server or proxy. Used for active checks. Only one value can be specified:<br>*unencrypted* - connect without encryption (default)<br>*psk* - connect using TLS and a pre-shared key (PSK)<br>*cert* - connect using TLS and a certificate<br>This parameter is supported since Zabbix 3.0.0.| |TLSCRLFile|no|<|<|Full pathname of a file containing revoked certificates. This parameter is used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSKeyFile|no|<|<|Full pathname of a file containing the agent private key used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSPSKFile|no|<|<|Full pathname of a file containing the agent pre-shared key used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSPSKIdentity|no|<|<|Pre-shared key identity string, used for encrypted communications with Zabbix server.<br>This parameter is supported since Zabbix 3.0.0.| |TLSServerCertIssuer|no|<|<|Allowed server (proxy) certificate issuer.<br>This parameter is supported since Zabbix 3.0.0.| |TLSServerCertSubject|no|<|<|Allowed server (proxy) certificate subject.<br>This parameter is supported since Zabbix 3.0.0.| |UnsafeUserParameters|no|0-1|0|Allow all characters to be passed in arguments to user-defined parameters.<br>0 - do not allow<br>1 - allow<br>The following characters are not allowed:<br>\\ ' " \` \* ? \[ \] { } \~ $ ! & ; ( ) < > \| \# @<br>Additionally, newline characters are not allowed.| |UserParameter|no|<|<|User-defined parameter to monitor. There can be several user-defined parameters.<br>Format: UserParameter=<key>,<shell command><br>Note that shell command must not return empty string or EOL only.<br>Shell commands may have relative paths, if UserParameterDir parameter is specified.<br>Examples:<br>UserParameter=system.test,who\|wc -l<br>UserParameter=check\_cpu,./custom\_script.sh| |UserParameterDir|no|<|<|Default search path for UserParameter commands. If used, the agent will change its working directory to the one specified here before executing a command. Thereby, UserParameter commands can have a relative `./` prefix instead of a full path.<br>Only one entry is allowed.<br>Example: UserParameterDir=/opt/myscripts|  ::: noteclassic  (\*) The number of active servers listed in ServerActive plus the number of pre-forked instances for passive checks specified in StartAgents must be less than 64. :::  

en-us	#### Parameters  |Parameter|Mandatory|Range|Default|Description| |--|--|--|--|----------| |Alias|no| | |Sets an alias for an item key. It can be used to substitute long and complex item key with a smaller and simpler one.<br>Multiple *Alias* parameters may be present. Multiple parameters with the same *Alias* key are allowed.<br>Different *Alias* keys may reference the same item key.<br>Aliases can be used in *HostMetadataItem* but not in *HostnameItem* or *PerfCounter* parameters.<br><br>Examples:<br><br>1. Retrieving paging file usage in percents from the server.<br>Alias=pg\_usage:perf\_counter\[\\Paging File(\_Total)\\% Usage\]<br>Now shorthand key **pg\_usage** may be used to retrieve data.<br><br>2. Getting CPU load with default and custom parameters.<br>Alias=cpu.load:system.cpu.load<br>Alias=cpu.load\[\*\]:system.cpu.load\[\*\]<br>This allows use **cpu.load** key to get CPU utilization percentage with default parameters as well as use **cpu.load\[percpu,avg15\]** to get specific data about CPU load.<br><br>3. Running multiple [low-level discovery](/manual/discovery/low_level_discovery) rules processing the same discovery items.<br>Alias=vfs.fs.discovery\[\*\]:vfs.fs.discovery<br>Now it is possible to set up several discovery rules using **vfs.fs.discovery** with different parameters for each rule, e.g., **vfs.fs.discovery\[foo\]**, **vfs.fs.discovery\[bar\]**, etc.| |AllowKey|no| | |Allow execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "\*" character to match any number of any characters.<br>Multiple key matching rules may be defined in combination with DenyKey. The parameters are processed one by one according to their appearance order.<br>This parameter is supported since Zabbix 5.0.0.<br>See also: [Restricting agent checks](/manual/config/items/restrict_checks).| |BufferSend|no|1-3600|5|Do not keep data longer than N seconds in buffer.| |BufferSize|no|2-65535|100|Maximum number of values in a memory buffer. The agent will send<br>all collected data to Zabbix server or proxy if the buffer is full.| |DebugLevel|no|0-5|3|Specifies debug level:<br>0 - basic information about starting and stopping of Zabbix processes<br>1 - critical information<br>2 - error information<br>3 - warnings<br>4 - for debugging (produces lots of information)<br>5 - extended debugging (produces even more information)| |DenyKey|no| | |Deny execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "\*" character to match any number of any characters.<br>Multiple key matching rules may be defined in combination with AllowKey. The parameters are processed one by one according to their appearance order.<br>This parameter is supported since Zabbix 5.0.0.<br>See also: [Restricting agent checks](/manual/config/items/restrict_checks).| |EnableRemoteCommands|no| |0|Whether remote commands from Zabbix server are allowed. This parameter is **deprecated**, use AllowKey=system.run\[\*\] or DenyKey=system.run\[\*\] instead<br>It is internal alias for AllowKey/DenyKey parameters depending on value: 0 - DenyKey=system.run\[\*\]<br>1 - AllowKey=system.run\[\*\].| |HostInterface|no|0-255 characters| |Optional parameter that defines host interface.<br>Host interface is used at host autoregistration process.<br>An agent will issue an error and not start if the value is over the limit of 255 characters.<br>If not defined, value will be acquired from HostInterfaceItem.<br>Supported since Zabbix 4.4.0.| |HostInterfaceItem|no| | |Optional parameter that defines an item used for getting host interface.<br>Host interface is used at host autoregistration process.<br>During an autoregistration request an agent will log a warning message if the value returned by specified item is over limit of 255 characters.<br>This option is only used when HostInterface is not defined.<br>Supported since Zabbix 4.4.0.| |HostMetadata|no|0-255 characters| |Optional parameter that defines host metadata. Host metadata is used only at host autoregistration process (active agent).<br>If not defined, the value will be acquired from HostMetadataItem.<br>An agent will issue an error and not start if the specified value is over the limit or a non-UTF-8 string.| |HostMetadataItem|no| | |Optional parameter that defines a *Zabbix agent* item used for getting host metadata. This option is only used when HostMetadata is not defined.<br>Supports UserParameters, performance counters and aliases. Supports *system.run\[\]* regardless of *EnableRemoteCommands* value.<br>HostMetadataItem value is retrieved on each autoregistration attempt and is used only at host autoregistration process (active agent).<br>During an autoregistration request an agent will log a warning message if the value returned by the specified item is over the limit of 255 characters.<br>The value returned by the item must be a UTF-8 string otherwise it will be ignored.| |Hostname|no| |Set by HostnameItem|List of comma-delimited unique, case-sensitive hostnames.<br>Required for active checks and must match hostnames as configured on the server. Value is acquired from HostnameItem if undefined.<br>Allowed characters: alphanumeric, '.', ' ', '\_' and '-'.<br>Maximum length: 128 characters per hostname, 2048 characters for the entire line.| |HostnameItem|no| |system.hostname|Optional parameter that defines a *Zabbix agent* item used for getting host name. This option is only used when Hostname is not defined.<br>Does not support UserParameters, performance counters or aliases, but does support *system.run\[\]* regardless of *EnableRemoteCommands* value.<br>The output length is limited to 512KB.<br>See also a [more detailed description](/manual/appendix/install/windows_agent#configuration).| |Include|no| | |You may include individual files or all files in a directory in the configuration file.<br>To only include relevant files in the specified directory, the asterisk wildcard character is supported for pattern matching. For example: `/absolute/path/to/config/files/*.conf`.<br>See [special notes](special_notes_include) about limitations.| |ListenBacklog|no|0 - INT\_MAX|SOMAXCONN|The maximum number of pending connections in the TCP queue.<br>Default value is a hard-coded constant, which depends on the system.<br>Maximum supported value depends on the system, too high values may be silently truncated to the 'implementation-specified maximum'.| |ListenIP|no| |0.0.0.0|List of comma-delimited IP addresses that the agent should listen on.| |ListenPort|no|1024-32767|10050|Agent will listen on this port for connections from the server.| |LogFile|yes, if LogType is set to *file*, otherwise<br>no| |C:\\zabbix\_agentd.log|Name of the agent log file.| |LogFileSize|no|0-1024|1|Maximum size of log file in MB.<br>0 - disable automatic log rotation.<br>*Note*: If the log file size limit is reached and file rotation fails, for whatever reason, the existing log file is truncated and started anew.| |LogType|no| |file|Log output type:<br>*file* - write log to file specified by LogFile parameter,<br>*system* - write log Windows Event Log,<br>*console* - write log to standard output.<br>This parameter is supported since Zabbix 3.0.0.| |LogRemoteCommands|no| |0|Enable logging of executed shell commands as warnings.<br>0 - disabled<br>1 - enabled| |MaxLinesPerSecond|no|1-1000|20|Maximum number of new lines the agent will send per second to Zabbix server<br>or proxy processing 'log', 'logrt' and 'eventlog' active checks.<br>The provided value will be overridden by the parameter 'maxlines',<br>provided in 'log', 'logrt' or 'eventlog' item keys.<br>*Note*: Zabbix will process 10 times more new lines than set in *MaxLinesPerSecond* to seek the required string in log items.| |PerfCounter|no| | |Defines a new parameter <parameter\_name> which is an average value for system performance counter <perf\_counter\_path> for the specified time period <period> (in seconds).<br>Syntax: <parameter\_name>,"<perf\_counter\_path>",<period><br>For example, if you wish to receive average number of processor interrupts per second for last minute, you can define a new parameter "interrupts" as the following:<br>PerfCounter = interrupts,"\\Processor(0)\\Interrupts/sec",60<br>Please note double quotes around performance counter path.<br>The parameter name (interrupts) is to be used as the item key when creating an item.<br>Samples for calculating average value will be taken every second.<br>You may run "typeperf -qx" to get list of all performance counters available in Windows.| |PerfCounterEn|no| | |Defines a new parameter <parameter\_name> which is an average value for system performance counter <perf\_counter\_path> for the specified time period <period> (in seconds).<br>Syntax: <parameter\_name>,"<perf\_counter\_path>",<period><br>Compared to PerfCounter, perfcounter paths must be in English.<br>Supported only on **Windows Server 2008/Vista** and above.<br>For example, if you wish to receive average number of processor interrupts per second for last minute, you can define a new parameter "interrupts" as the following:<br>PerfCounterEn = interrupts,"\\Processor(0)\\Interrupts/sec",60<br>Please note double quotes around performance counter path.<br>The parameter name (interrupts) is to be used as the item key when creating an item.<br>Samples for calculating average value will be taken every second.<br>You can find the list of English strings by viewing the following registry key: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009`.<br>This parameter is supported since Zabbix 4.0.13 and 4.2.7.| |RefreshActiveChecks|no|60-3600|120|How often list of active checks is refreshed, in seconds.<br>Note that after failing to refresh active checks the next refresh will be attempted after 60 seconds.| |Server|yes, if StartAgents is not explicitly set to 0| | |List of comma delimited IP addresses, optionally in CIDR notation, or hostnames of Zabbix servers.<br>Incoming connections will be accepted only from the hosts listed here.<br>If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address.<br>'0.0.0.0/0' can be used to allow any IPv4 address.<br>Note, that "IPv4-compatible IPv6 addresses" (0000::/96 prefix) are supported but deprecated by [RFC4291](https://tools.ietf.org/html/rfc4291#section-2.5.5).<br>Example: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.domain<br>Spaces are allowed.| |ServerActive|no|(\*)| |Zabbix server/proxy address or cluster configuration to get active checks from.<br>Server/proxy address is IP address or DNS name and optional port separated by colon.<br>Cluster configuration is one or more server addresses separated by semicolon.<br>Multiple Zabbix servers/clusters and Zabbix proxies can be specified, separated by comma.<br>More than one Zabbix proxy should not be specified from each Zabbix server/cluster.<br>If Zabbix proxy is specified then Zabbix server/cluster for that proxy should not be specified.<br>Multiple comma-delimited addresses can be provided to use several independent Zabbix servers in parallel. Spaces are allowed.<br>If port is not specified, default port is used.<br>IPv6 addresses must be enclosed in square brackets if port for that host is specified.<br>If port is not specified, square brackets for IPv6 addresses are optional.<br>If this parameter is not specified, active checks are disabled.<br>Example for Zabbix proxy:<br>ServerActive=127.0.0.1:10051<br>Example for multiple servers:<br>ServerActive=127.0.0.1:20051,zabbix.domain,\[::1\]:30051,::1,\[12fc::1\]<br>Example for high availability:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051;zabbix.cluster.node3<br>Example for high availability with two clusters and one server:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051,zabbix.cluster2.node1;zabbix.cluster2.node2,zabbix.domain| |SourceIP|no| | |Source IP address for:<br>- outgoing connections to Zabbix server or Zabbix proxy;<br>- making connections while executing some items (web.page.get, net.tcp.port, etc.)| |StartAgents|no|0-63 (\*)|3|Number of pre-forked instances of zabbix\_agentd that process passive checks.<br>If set to 0, disables passive checks and the agent will not listen on any TCP port.| |Timeout|no|1-30|3|Spend no more than Timeout seconds on processing| |TLSAccept|yes, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no| | |What incoming connections to accept. Used for a passive checks. Multiple values can be specified, separated by comma:<br>*unencrypted* - accept connections without encryption (default)<br>*psk* - accept connections with TLS and a pre-shared key (PSK)<br>*cert* - accept connections with TLS and a certificate<br>This parameter is supported since Zabbix 3.0.0.| |TLSCAFile|no| | |Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCertFile|no| | |Full pathname of a file containing the agent certificate or certificate chain, used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSConnect|yes, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no| | |How the agent should connect to Zabbix server or proxy. Used for active checks. Only one value can be specified:<br>*unencrypted* - connect without encryption (default)<br>*psk* - connect using TLS and a pre-shared key (PSK)<br>*cert* - connect using TLS and a certificate<br>This parameter is supported since Zabbix 3.0.0.| |TLSCRLFile|no| | |Full pathname of a file containing revoked certificates. This parameter is used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSKeyFile|no| | |Full pathname of a file containing the agent private key used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSPSKFile|no| | |Full pathname of a file containing the agent pre-shared key used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSPSKIdentity|no| | |Pre-shared key identity string, used for encrypted communications with Zabbix server.<br>This parameter is supported since Zabbix 3.0.0.| |TLSServerCertIssuer|no| | |Allowed server (proxy) certificate issuer.<br>This parameter is supported since Zabbix 3.0.0.| |TLSServerCertSubject|no| | |Allowed server (proxy) certificate subject.<br>This parameter is supported since Zabbix 3.0.0.| |UnsafeUserParameters|no|0-1|0|Allow all characters to be passed in arguments to user-defined parameters.<br>0 - do not allow<br>1 - allow<br>The following characters are not allowed:<br>\\ ' " \` \* ? \[ \] { } \~ $ ! & ; ( ) < > \| \# @<br>Additionally, newline characters are not allowed.| |UserParameter|no| | |User-defined parameter to monitor. There can be several user-defined parameters.<br>Format: UserParameter=<key>,<shell command><br>Note that shell command must not return empty string or EOL only.<br>Shell commands may have relative paths, if UserParameterDir parameter is specified.<br>Examples:<br>UserParameter=system.test,who\|wc -l<br>UserParameter=check\_cpu,./custom\_script.sh| |UserParameterDir|no| | |Default search path for UserParameter commands. If used, the agent will change its working directory to the one specified here before executing a command. Thereby, UserParameter commands can have a relative `./` prefix instead of a full path.<br>Only one entry is allowed.<br>Example: UserParameterDir=/opt/myscripts|  ::: noteclassic  (\*) The number of active servers listed in ServerActive plus the number of pre-forked instances for passive checks specified in StartAgents must be less than 64. :::
ja	#### パラメータ  |パラメータ|必須|範囲|デフォルト|説明| |--|--|--|--|----------| |Alias|no| | |項目キーのエイリアスを設定します。長くて複雑な項目キーを、より短くて単純なものに置き換えるために使用できます。<br>複数の *Alias* パラメータが存在する場合があります。同じ *Alias* キーを持つ複数のパラメーターを使用できます。<br>異なる *Alias* キーで同じアイテム キーを参照できます。<br>*HostMetadataItem* ではエイリアスを使用できますが、*HostnameItem* または *PerfCounter* パラメーターでは使用できません。 <br><br>例:<br><br>1.サーバーからページング ファイルの使用率をパーセントで取得します。<br>Alias=pg\_usage:perf\_counter\[\\Paging File(\_Total)\\% Usage\]<br>これにより短縮キー **pg\_usage**をデータの取得に使用できます。<br><br>2.デフォルトおよびカスタム パラメータで CPU 負荷を取得します。<br>Alias=cpu.load:system.cpu.load<br>Alias=cpu.load\[\*\]:system.cpu.load\[\*\]< br>これにより**cpu.load** キーを使用してデフォルト パラメータの CPU 使用率を取得したり、**cpu.load\[percpu,avg15\]** を使用して CPU 負荷に関する特定のデータを取得したりできます。<br> <br>3.同じディスカバリー アイテムを処理する複数の [ローレベルディスカバリ](/manual/discovery/low_level_discovery) ルールを実行しています。<br>Alias=vfs.fs.discovery\[\*\]:vfs.fs.discovery<br> **vfs.fs.discovery** を使用して、ルールごとに異なるパラメーターを使用して複数の検出ルールを設定できます (例: **vfs.fs.discovery\[foo\]**、**vfs.fs.discovery\)。 [bar\]** など| |AllowKey|no| | |パターンに一致する項目キーの実行を許可します。 キー パターンは"\*"文字をサポートするワイルドカード式で、任意の数の任意の文字に一致します。<br>DenyKey と組み合わせて、複数のキー マッチング ルールを定義できます。 パラメータは出現順に従って1つずつ処理されます。<br>このパラメータはZabbix 5.0.0からサポートされています。<br>参照: [エージェントチェックの制限](/manual/config/items/restrict_checks).| |BufferSend|no|1-3600|5|データを N 秒より長くバッファーに保持しません| |BufferSize|no|2-65535|100|メモリ バッファ内の値の最大数。 バッファがいっぱいの場合、エージェントは<br>収集したすべてのデータを Zabbix サーバーまたはプロキシに送信します。| |DebugLevel|no|0-5|3|デバッグ レベルを指定します。<br>0 - Zabbix プロセスの開始と停止に関する基本情報<br>1 - 重要な情報<br>2 - エラー情報<br>3 - 警告<br>4 - デバッグ用 (多くの情報を生成) )<br>5 - 拡張デバッグ (さらに多くの情報を生成)| |DenyKey|no| | |パターンに一致する項目キーの実行を拒否します。 キー パターンは、任意の数の任意の文字に一致する"\*"文字をサポートするワイルドカード式です。<br>AllowKey と組み合わせて、複数のキー一致ルールを定義できます。 パラメータは出現順に従って1つずつ処理されます。<br>このパラメータはZabbix 5.0.0からサポートされています。<br>参照: [エージェントチェックの制限](/manual/config/items/restrict_checks).| |EnableRemoteCommands|no| |0|Zabbix サーバーからのリモート コマンドを許可するかどうか。 このパラメーターは**非推奨**です。代わりに、AllowKey=system.run\[\*\] または DenyKey=system.run\[\*\] を使用してください<br>これは、値に応じた AllowKey/DenyKey パラメータの内部エイリアスです: 0 - DenyKey=system.run\[\*\]<br>1 - AllowKey=system.run\[\*\]。| |HostInterface|no|0-255 文字| |ホスト インターフェースを定義するオプション パラメータ。<br>ホスト インターフェースは、ホストの自動登録プロセスで使用されます。<br>値が 255 文字の制限を超えると、エージェントはエラーを発行し、起動しません。<br>定義されていない場合、値 HostInterfaceItem から取得されます。<br>Zabbix 4.4.0 以降でサポートされています。| |HostInterfaceItem|no| | |ホスト インターフェースの取得に使用されるアイテムを定義するオプション パラメータ。<br>ホスト インターフェースは、ホストの自動登録プロセスで使用されます。<br>自動登録リクエスト中に、指定されたアイテムによって返される値が 255 の制限を超えている場合、エージェントは警告メッセージを記録します。 <br>このオプションは、HostInterface が定義されていない場合にのみ使用されます。<br>Zabbix 4.4.0 以降でサポートされています。| |HostMetadata|no|0-255 文字| |ホストのメタデータを定義するオプションのパラメーター。 ホストのメタデータは、ホストの自動登録プロセス (アクティブなエージェント) でのみ使用されます。<br>未定義の場合、値は HostMetadataItem から取得されます。<br>指定された値が制限を超えているか、UTF-8 以外の文字列である場合、エージェントはエラーを発行して起動しません。| |HostMetadataItem|no| | |ホスト メタデータの取得に使用される *Zabbix エージェント* アイテムを定義するオプションのパラメーター。 このオプションは、HostMetadata が定義されていない場合にのみ使用されます。<br>UserParameters、パフォーマンス カウンター、およびエイリアスをサポートします。 *EnableRemoteCommands* 値に関係なく、*system.run\[\]* をサポートします。<br>HostMetadataItem 値は、自動登録の試行ごとに取得され、ホスト自動登録プロセス (アクティブなエージェント) でのみ使用されます。<br>自動登録リクエスト中、エージェント 指定されたアイテムによって返された値が 255 文字の制限を超えている場合、警告メッセージがログに記録されます。<br>アイテムによって返された値は UTF-8 文字列である必要があり、それ以外の場合は無視されます。| |Hostname|no| |HostnameItem で設定|カンマ区切りの一意のホスト名のリスト。 未定義の場合は HostnameItem から値を取得します。<br>使用できる文字: 英数字、'.',' ','\_'および'-'<br>最大長: ホスト名ごとに 128 文字、行全体で 2048 文字。| |HostnameItem|no| |system.hostname|ホスト名の取得に使用される *Zabbix エージェント* アイテムを定義するオプションのパラメーター。 このオプションは、ホスト名が定義されていない場合にのみ使用されます。<br>UserParameters、パフォーマンス カウンター、またはエイリアスはサポートされませんが、*EnableRemoteCommands* 値に関係なく *system.run\[\]* はサポートされます。<br>出力の長さは次のとおりです。 512KB に制限されています。<br>[より詳細な説明](/manual/appendix/install/windows_agent#configuration)も参照してください。| |Include|no| | |個々のファイルまたはディレクトリ内のすべてのファイルを構成ファイルに含めることができます。<br>指定したディレクトリに関連ファイルのみを含めるために、パターン マッチングでアスタリスク ワイルドカード文字がサポートされています。 例: `/absolute/path/to/config/files/*.conf`.<br>制限については、[特記事項](special_notes_include)を参照してください。| |ListenBacklog|no|0 - INT\_MAX|SOMAXCONN|TCP キュー内の保留中の接続の最大数。<br>デフォルト値はハードコードされた定数で、システムによって異なります。<br>サポートされている最大値もシステムによって異なります。値が高すぎると'実装で指定された最大値'に切り捨てられる場合があります。| |ListenIP|no| |0.0.0.0|エージェントがリッスンする IP アドレスのカンマ区切りリスト| |ListenPort|no|1024-32767|10050|エージェントは、このポートでサーバーからの接続をリッスンします。| |LogFile|LogType が *file* に設定されている場合:yes<br>それ以外:no| |C:\\zabbix\_agentd.log|エージェントログファイル名| |LogFileSize|no|0-1024|1|ログ ファイルの最大サイズ (MB)。<br>0 - ログの自動ローテーションを無効にします。<br>*注*: ログ ファイルのサイズ制限に達し、ファイルのローテーションが何らかの理由で失敗した場合、既存のログ ファイルは切り捨てられ、新たなファイルで開始されます。| |LogType|no| |file|ログ出力タイプ:<br>*file* - LogFile パラメーターで指定されたファイルにログを書き込みます。<br>*system* - ログを書き込みます。Windows イベント ログ、<br>*console* - ログを標準出力に書き込みます。<br>これ パラメータは Zabbix 3.0.0 以降でサポートされています。| |LogRemoteCommands|no| |0|実行されたシェル コマンドの警告ログを有効にします。<br>0 - 無効<br>1 - 有効| |MaxLinesPerSecond|no|1-1000|20|エージェントが 'log'、'logrt' および 'eventlog' アクティブ チェックを処理する Zabbix サーバーまたはプロキシに 1 秒あたりに送信する新しい行の最大数。<br>指定された値は、パラメータ'maxlines'によって上書きされます。<br>'log','logrt'または'eventlog'項目キーで提供されます。<br>*注*: Zabbix は、*MaxLinesPerSecond* で設定されたよりも 10 倍多くの新しい行を処理して、ログ項目で必要な文字列を検索します。| |PerfCounter|no| | |指定された<期間>(秒単位) のシステム パフォーマンス カウンター <perf\_counter\_path> の平均値である新しいパラメーター <parameter\_name> を定義します。<br>構文: <parameter\_name>," <perf\_counter\_path>",<period><br>たとえば、過去 1 分間の 1 秒あたりの平均プロセッサ割り込み数を取得する場合は、新しいパラメータ"interrupts"を次のように定義できます。<br> PerfCounter = interrupts,"\\Processor(0)\\Interrupts/sec",60<br>パフォーマンス カウンター パスを二重引用符で囲むことに注意してください。<br>パラメーター名 (interrupts) は、作成時にアイテム キーとして使用されます。 <br>平均値を計算するためのサンプルが毎秒取得されます。<br>"typeperf -qx"を実行すると、Windows で使用可能なすべてのパフォーマンス カウンターのリストを取得できます。| |PerfCounterEn|no| | |指定された期間 <期間> (秒単位) のシステム パフォーマンス カウンター <perf\_counter\_path> の平均値である新しいパラメーター <parameter\_name> を定義します。<br>構文: <parameter\_name>," <perf\_counter\_path>",<period><br>PerfCounter と比較して、perfcounter のパスは英語である必要があります。<br>**Windows Server 2008/Vista** 以降でのみサポートされています。<br>例:過去 1 分間の 1 秒あたりのプロセッサ割り込みの平均数を取得する場合は、新しいパラメータ"interrupts"を次のように定義できます。<br>PerfCounterEn = interrupts,"\\Processor(0)\\Interrupts/sec", 60<br>パフォーマンス カウンター パスを二重引用符で囲んでください。<br>パラメーター名 (interrupts) は、アイテムを作成するときにアイテム キーとして使用されます。<br>平均値を計算するためのサンプルは、1 秒ごとに取得されます。< br>次のレジストリ キーを表示すると、英語の文字列のリストを見つけることができます: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009`.<br>このパラメータはZabbix 4.0.13 および 4.2.7 以降でサポートされています。| |RefreshActiveChecks|no|60-3600|120|アクティブなチェックのリストが更新される頻度 (秒単位)。<br>アクティブなチェックの更新に失敗すると、60 秒後に次の更新が試行されることに注意してください。| |Server|StartAgents が明示的に 0 に設定されていない場合:yes| | |カンマ区切りの IP アドレスのリスト (オプションで CIDR 表記、または Zabbix サーバーのホスト名)。<br>着信接続は、ここにリストされているホストからのみ受け入れられます。<br>IPv6 サポートが有効になっている場合は、'127.0.0.1', ': :127.0.0.1'、'::ffff:127.0.0.1' は同等に扱われ、'::/0' は任意の IPv4 または IPv6 アドレスを許可します。<br>'0.0.0.0/0'を使用して、任意の IPv4 アドレスを許可できます。<br>"IPv4 互換の IPv6 アドレス"(0000::/96 プレフィックス) はサポートされていますが、[RFC4291](https://tools.ietf.org/html/rfc4291#section-2.5.5) によって非推奨になっていることに注意してください。<br>例: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.domain<br>スペースを使用できます。| |ServerActive|no|(\*)| |アクティブ チェックを取得する Zabbix サーバー/プロキシ アドレスまたはクラスタ構成。<br>サーバー/プロキシ アドレスは、コロンで区切られた IP アドレスまたは DNS 名とオプションのポートです。<br>クラスタ構成は、セミコロンで区切られた 1 つまたは複数のサーバー アドレスです。<br> br>複数の Zabbix サーバー/クラスタと Zabbix プロキシをカンマで区切って指定できます。<br>各 Zabbix サーバー/クラスタから複数の Zabbix プロキシを指定しないでください。<br>Zabbix プロキシが指定されている場合は、Zabbix サーバー/クラスタそのプロキシには指定しないでください。<br>複数の独立した Zabbix サーバーを並行して使用するために、複数のカンマ区切りのアドレスを指定できます。スペースを使用できます。<br>ポートが指定されていない場合、デフォルトのポートが使用されます。<br>そのホストのポートが指定されている場合、IPv6 アドレスは角括弧で囲む必要があります。<br>ポートが指定されていない場合、IPv6 の角括弧アドレスはオプションです。<br>このパラメータが指定されていない場合、アクティブ チェックは無効になります。<br>Zabbix プロキシの例:<br>ServerActive=127.0.0.1:10051<br>複数のサーバーの例:<br>ServerActive= 127.0.0.1:20051,zabbix.domain,\[::1\]:30051,::1,\[12fc::1\]<br>高可用性の例:<br>ServerActive=zabbix.cluster.node1 ;zabbix.cluster.node2:20051;zabbix.cluster.node3<br>2 つのクラスターと 1 つのサーバーによる高可用性の例:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051,zabbix.cluster2 .node1;zabbix.cluster2.node2,zabbix.domain| |SourceIP|no| | |ソース IP アドレス:<br>- Zabbix サーバーまたは Zabbix プロキシへの発信接続;<br>- いくつかのアイテム (web.page.get、net.tcp.port など) の実行中に接続を確立する| |StartAgents|no|0-63 (\*)|3|パッシブ チェックを処理する事前フォークされた zabbix\_agentd インスタンスの数。<br>0 に設定すると、パッシブ チェックが無効になり、エージェントはどの TCP ポートでもリッスンしません。| |Timeout|no|1-30|3|処理に Timeout 秒を超えないようにします| |TLSAccept|TLS 証明書または PSK パラメータが定義されている場合 (*暗号化されていない* 接続の場合でも):yes、それ以外の場合:no| | |受け入れる着信接続。 パッシブ チェックに使用されます。 コンマで区切って複数の値を指定できます。<br>*unencrypted* - 暗号化なしで接続を受け入れる (デフォルト)<br>*psk* - TLS と事前共有キー (PSK) を使用した接続を受け入れる<br>*cert* - TLS と証明書による接続を受け入れる<br>このパラメータは Zabbix 3.0.0 以降でサポートされています。| |TLSCAFile|no| | |Zabbix コンポーネント間の暗号化された通信に使用される、ピア証明書検証用の最上位 CA 証明書を含むファイルのフル パス名。<br>このパラメータは、Zabbix 3.0.0 以降でサポートされています。| |TLSCertFile|no| | |Zabbix コンポーネントとの暗号化された通信に使用される、エージェント証明書または証明書チェーンを含むファイルのフル パス名。<br>このパラメータは、Zabbix 3.0.0 以降でサポートされています。| |TLSConnect|TLS 証明書または PSK パラメータが定義されている場合 (*暗号化されていない* 接続の場合でも):yes、それ以外の場合:no| | |エージェントが Zabbix サーバーまたはプロキシに接続する方法。 アクティブ チェックに使用されます。 指定できる値は 1 つだけです。<br>*unencrypted* - 暗号化なしで接続 (デフォルト)<br>*psk* - TLS と事前共有キー (PSK) を使用して接続<br>*cert* - TLS と 証明書<br>このパラメータは、Zabbix 3.0.0 以降でサポートされています。| |TLSCRLFile|no| | |失効した証明書を含むファイルのフル パス名。 このパラメータは、Zabbix コンポーネントとの暗号化通信に使用されます。<br>このパラメータは、Zabbix 3.0.0 以降でサポートされています。| |TLSKeyFile|no| | |Zabbix コンポーネントとの暗号化された通信に使用されるエージェントの秘密鍵を含むファイルのフル パス名。<br>このパラメータは、Zabbix 3.0.0 以降でサポートされています。| |TLSPSKFile|no| | |Zabbix コンポーネントとの暗号化通信に使用されるエージェントの事前共有キーを含むファイルのフル パス名。<br>このパラメータは、Zabbix 3.0.0 以降でサポートされています。| |TLSPSKIdentity|no| | |Zabbix サーバーとの暗号化された通信に使用される事前共有キー ID 文字列。<br>このパラメータは Zabbix 3.0.0 以降でサポートされています。| |TLSServerCertIssuer|no| | |許可されたサーバー (プロキシ) 証明書の発行者。<br>このパラメータは Zabbix 3.0.0 以降でサポートされています。| |TLSServerCertSubject|no| | |許可されたサーバー (プロキシ) 証明書のサブジェクト。<br>このパラメータは Zabbix 3.0.0 以降でサポートされています。| |UnsafeUserParameters|no|0-1|0|ユーザー定義パラメータの引数にすべての文字を渡すことができるようにします。<br>0 - 許可しない<br>1 - 許可する<br>ただし次の文字は使用できません:<br>\\ ' " \` \* ? \[ \] { } \~ $ ! & ; ( ) < > \| \# @<br>さらに、改行文字は使用できません。| |UserParameter|no| | |監視するユーザー定義のパラメーター。 複数のユーザー定義パラメータが存在する場合があります。<br>形式: UserParameter=<キー>,<シェル コマンド><br>シェル コマンドは、空の文字列または EOL のみを返してはならないことに注意してください。<br>UserParameterDir パラメータが指定されている場合、シェル コマンドには相対パスが含まれる場合があります。<br>例:<br>UserParameter=system.test,who\|wc -l<br>UserParameter=check\_cpu,./custom\_script .sh| |UserParameterDir|no| | |UserParameter コマンドのデフォルトの検索パス。 使用すると、エージェントはコマンドを実行する前に、ここで指定されたディレクトリに作業ディレクトリを変更します。 これにより、UserParameter コマンドは、フル パスの代わりに相対 `./` プレフィックスを持つことができます。<br>許可されるエントリは 1 つだけです。<br>例: UserParameterDir=/opt/myscripts|  ::: noteclassic (\*) ServerActive にリストされているアクティブなサーバーの数と、StartAgents で指定されたパッシブ チェック用の事前にフォークされたインスタンスの数を加えた数は、64 未満である必要があります。 :::

en-us	#### Parameters  |Parameter|Mandatory|Range|Default|Description| |--|--|--|--|----------| |Alias|no| | |Sets an alias for an item key. It can be used to substitute long and complex item key with a smaller and simpler one.<br>Multiple *Alias* parameters may be present. Multiple parameters with the same *Alias* key are allowed.<br>Different *Alias* keys may reference the same item key.<br>Aliases can be used in *HostMetadataItem* but not in *HostnameItem* parameters.<br><br>Examples:<br><br>1. Retrieving the ID of user 'zabbix'.<br>Alias=zabbix.userid:vfs.file.regexp\[/etc/passwd,"\^zabbix:.:(\[0-9\]+)",,,,\\1\]<br>Now shorthand key **zabbix.userid** may be used to retrieve data.<br><br>2. Getting CPU utilization with default and custom parameters.<br>Alias=cpu.util:system.cpu.util<br>Alias=cpu.util\[\*\]:system.cpu.util\[\*\]<br>This allows use **cpu.util** key to get CPU utilization percentage with default parameters as well as use **cpu.util\[all, idle, avg15\]** to get specific data about CPU utilization.<br><br>3. Running multiple [low-level discovery](/manual/discovery/low_level_discovery) rules processing the same discovery items.<br>Alias=vfs.fs.discovery\[\*\]:vfs.fs.discovery<br>Now it is possible to set up several discovery rules using **vfs.fs.discovery** with different parameters for each rule, e.g., **vfs.fs.discovery\[foo\]**, **vfs.fs.discovery\[bar\]**, etc.| |AllowKey|no| | |Allow execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "\*" character to match any number of any characters.<br>Multiple key matching rules may be defined in combination with DenyKey. The parameters are processed one by one according to their appearance order.<br>This parameter is supported since Zabbix 5.0.0.<br>See also: [Restricting agent checks](/manual/config/items/restrict_checks).| |AllowRoot|no| |0|Allow the agent to run as 'root'. If disabled and the agent is started by 'root', the agent will try to switch to user 'zabbix' instead. Has no effect if started under a regular user.<br>0 - do not allow<br>1 - allow| |BufferSend|no|1-3600|5|Do not keep data longer than N seconds in buffer.| |BufferSize|no|2-65535|100|Maximum number of values in a memory buffer. The agent will send<br>all collected data to Zabbix server or proxy if the buffer is full.| |DebugLevel|no|0-5|3|Specifies debug level:<br>0 - basic information about starting and stopping of Zabbix processes<br>1 - critical information<br>2 - error information<br>3 - warnings<br>4 - for debugging (produces lots of information)<br>5 - extended debugging (produces even more information)| |DenyKey|no| | |Deny execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "\*" character to match any number of any characters.<br>Multiple key matching rules may be defined in combination with AllowKey. The parameters are processed one by one according to their appearance order.<br>This parameter is supported since Zabbix 5.0.0.<br>See also: [Restricting agent checks](/manual/config/items/restrict_checks).| |EnableRemoteCommands|no| |0|Whether remote commands from Zabbix server are allowed. This parameter is **deprecated**, use AllowKey=system.run\[\*\] or DenyKey=system.run\[\*\] instead<br>It is internal alias for AllowKey/DenyKey parameters depending on value: 0 - DenyKey=system.run\[\*\]<br>1 - AllowKey=system.run\[\*\]| |HostInterface|no|0-255 characters| |Optional parameter that defines host interface.<br>Host interface is used at host [autoregistration](/manual/discovery/auto_registration#using_dns_as_default_interface) process.<br>An agent will issue an error and not start if the value is over the limit of 255 characters.<br>If not defined, value will be acquired from HostInterfaceItem.<br>Supported since Zabbix 4.4.0.| |HostInterfaceItem|no| | |Optional parameter that defines an item used for getting host interface.<br>Host interface is used at host [autoregistration](/manual/discovery/auto_registration#using_dns_as_default_interface) process.<br>During an autoregistration request an agent will log a warning message if the value returned by specified item is over limit of 255 characters.<br>This option is only used when HostInterface is not defined.<br>Supported since Zabbix 4.4.0.| |HostMetadata|no|0-255 characters| |Optional parameter that defines host metadata. Host metadata is used only at host autoregistration process (active agent).<br>If not defined, the value will be acquired from HostMetadataItem.<br>An agent will issue an error and not start if the specified value is over the limit or a non-UTF-8 string.| |HostMetadataItem|no| | |Optional parameter that defines a *Zabbix agent* item used for getting host metadata. This option is only used when HostMetadata is not defined.<br>Supports UserParameters and aliases. Supports *system.run\[\]* regardless of AllowKey/DenyKey values.<br>HostMetadataItem value is retrieved on each autoregistration attempt and is used only at host autoregistration process (active agent).<br>During an autoregistration request an agent will log a warning message if the value returned by the specified item is over the limit of 255 characters.<br>The value returned by the item must be a UTF-8 string otherwise it will be ignored.| |Hostname|no| |Set by HostnameItem|List of comma-delimited unique, case-sensitive hostnames.<br>Required for active checks and must match hostnames as configured on the server. Value is acquired from HostnameItem if undefined.<br>Allowed characters: alphanumeric, '.', ' ', '\_' and '-'.<br>Maximum length: 128 characters per hostname, 2048 characters for the entire line.| |HostnameItem|no| |system.hostname|Optional parameter that defines a *Zabbix agent* item used for getting host name. This option is only used when Hostname is not defined.<br>Does not support UserParameters or aliases, but does support *system.run\[\]* regardless of AllowKey/DenyKey values.<br>The output length is limited to 512KB.| |Include|no| | |You may include individual files or all files in a directory in the configuration file.<br>To only include relevant files in the specified directory, the asterisk wildcard character is supported for pattern matching. For example: `/absolute/path/to/config/files/*.conf`.<br>See [special notes](special_notes_include) about limitations.| |ListenBacklog|no|0 - INT\_MAX|SOMAXCONN|The maximum number of pending connections in the TCP queue.<br>Default value is a hard-coded constant, which depends on the system.<br>Maximum supported value depends on the system, too high values may be silently truncated to the 'implementation-specified maximum'.| |ListenIP|no| |0.0.0.0|List of comma delimited IP addresses that the agent should listen on.<br>Multiple IP addresses are supported in version 1.8.3 and higher.| |ListenPort|no|1024-32767|10050|Agent will listen on this port for connections from the server.| |LoadModule|no| | |Module to load at agent startup. Modules are used to extend functionality of the agent.<br>Formats:<br>LoadModule=<module.so><br>LoadModule=<path/module.so><br>LoadModule=</abs\_path/module.so><br>Either the module must be located in directory specified by LoadModulePath or the path must precede the module name. If the preceding path is absolute (starts with '/') then LoadModulePath is ignored.<br>It is allowed to include multiple LoadModule parameters.| |LoadModulePath|no| | |Full path to location of agent modules.<br>Default depends on compilation options.| |LogFile|yes, if LogType is set to *file*, otherwise<br>no| | |Name of log file.| |LogFileSize|no|0-1024|1|Maximum size of log file in MB.<br>0 - disable automatic log rotation.<br>*Note*: If the log file size limit is reached and file rotation fails, for whatever reason, the existing log file is truncated and started anew.| |LogType|no| |file|Log output type:<br>*file* - write log to file specified by LogFile parameter,<br>*system* - write log to syslog,<br>*console* - write log to standard output.<br>This parameter is supported since Zabbix 3.0.0.| |LogRemoteCommands|no| |0|Enable logging of executed shell commands as warnings.<br>0 - disabled<br>1 - enabled<br>Commands will be logged only if executed remotely. Log entries will not be created if system.run\[\] is launched locally by HostMetadataItem, HostInterfaceItem or HostnameItem parameters.| |MaxLinesPerSecond|no|1-1000|20|Maximum number of new lines the agent will send per second to Zabbix server or proxy when processing 'log' and 'eventlog' active checks.<br>The provided value will be overridden by the parameter 'maxlines',<br>provided in 'log' or 'eventlog' item key.<br>*Note*: Zabbix will process 10 times more new lines than set in *MaxLinesPerSecond* to seek the required string in log items.| |PidFile|no| |/tmp/zabbix\_agentd.pid|Name of PID file.| |RefreshActiveChecks|no|60-3600|120|How often list of active checks is refreshed, in seconds.<br>Note that after failing to refresh active checks the next refresh will be attempted after 60 seconds.| |Server|yes, if StartAgents is not explicitly set to 0| | |List of comma delimited IP addresses, optionally in CIDR notation, or hostnames of Zabbix servers and Zabbix proxies.<br>Incoming connections will be accepted only from the hosts listed here.<br>If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address.<br>'0.0.0.0/0' can be used to allow any IPv4 address.<br>Note, that "IPv4-compatible IPv6 addresses" (0000::/96 prefix) are supported but deprecated by [RFC4291](https://tools.ietf.org/html/rfc4291#section-2.5.5).<br>Example: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.domain<br>Spaces are allowed.| |ServerActive|no| | |Zabbix server/proxy address or cluster configuration to get active checks from.<br>Server/proxy address is IP address or DNS name and optional port separated by colon.<br>Cluster configuration is one or more server addresses separated by semicolon.<br>Multiple Zabbix servers/clusters and Zabbix proxies can be specified, separated by comma.<br>More than one Zabbix proxy should not be specified from each Zabbix server/cluster.<br>If Zabbix proxy is specified then Zabbix server/cluster for that proxy should not be specified.<br>Multiple comma-delimited addresses can be provided to use several independent Zabbix servers in parallel. Spaces are allowed.<br>If port is not specified, default port is used.<br>IPv6 addresses must be enclosed in square brackets if port for that host is specified.<br>If port is not specified, square brackets for IPv6 addresses are optional.<br>If this parameter is not specified, active checks are disabled.<br>Example for Zabbix proxy:<br>ServerActive=127.0.0.1:10051<br>Example for multiple servers:<br>ServerActive=127.0.0.1:20051,zabbix.domain,\[::1\]:30051,::1,\[12fc::1\]<br>Example for high availability:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051;zabbix.cluster.node3<br>Example for high availability with two clusters and one server:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051,zabbix.cluster2.node1;zabbix.cluster2.node2,zabbix.domain| |SourceIP|no| | |Source IP address for:<br>- outgoing connections to Zabbix server or Zabbix proxy;<br>- making connections while executing some items (web.page.get, net.tcp.port, etc.)| |StartAgents|no|0-100|3|Number of pre-forked instances of zabbix\_agentd that process passive checks.<br>If set to 0, disables passive checks and the agent will not listen on any TCP port.| |Timeout|no|1-30|3|Spend no more than Timeout seconds on processing.| |TLSAccept|yes, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no| | |What incoming connections to accept. Used for a passive checks. Multiple values can be specified, separated by comma:<br>*unencrypted* - accept connections without encryption (default)<br>*psk* - accept connections with TLS and a pre-shared key (PSK)<br>*cert* - accept connections with TLS and a certificate<br>This parameter is supported since Zabbix 3.0.0.| |TLSCAFile|no| | |Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCertFile|no| | |Full pathname of a file containing the agent certificate or certificate chain, used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCipherAll|no| | |GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.<br>Example: TLS\_AES\_256\_GCM\_SHA384:TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherAll13|no| | |Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL::+SIGN-ALL:+CTYPE-X.509<br>Example for OpenSSL: EECDH+aRSA+AES128:RSA+aRSA+AES128:kECDHEPSK+AES128:kPSK+AES128<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherCert|no| | |GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509<br>Example for OpenSSL: EECDH+aRSA+AES128:RSA+aRSA+AES128<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherCert13|no| | |Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate-based encryption.<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherPSK|no| | |GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for PSK-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL<br>Example for OpenSSL: kECDHEPSK+AES128:kPSK+AES128<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherPSK13|no| | |Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for PSK-based encryption.<br>Example: TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>This parameter is supported since Zabbix 4.4.7.| |TLSConnect|yes, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no| | |How the agent should connect to Zabbix server or proxy. Used for active checks. Only one value can be specified:<br>*unencrypted* - connect without encryption (default)<br>*psk* - connect using TLS and a pre-shared key (PSK)<br>*cert* - connect using TLS and a certificate<br>This parameter is supported since Zabbix 3.0.0.| |TLSCRLFile|no| | |Full pathname of a file containing revoked certificates. This parameter is used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSKeyFile|no| | |Full pathname of a file containing the agent private key used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSPSKFile|no| | |Full pathname of a file containing the agent pre-shared key used for encrypted communications with Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSPSKIdentity|no| | |Pre-shared key identity string, used for encrypted communications with Zabbix server.<br>This parameter is supported since Zabbix 3.0.0.| |TLSServerCertIssuer|no| | |Allowed server (proxy) certificate issuer.<br>This parameter is supported since Zabbix 3.0.0.| |TLSServerCertSubject|no| | |Allowed server (proxy) certificate subject.<br>This parameter is supported since Zabbix 3.0.0.| |UnsafeUserParameters|no|0,1|0|Allow all characters to be passed in arguments to user-defined parameters.<br>0 - do not allow<br>1 - allow<br>The following characters are not allowed:<br>\\ ' " \` \* ? \[ \] { } \~ $ ! & ; ( ) < > \| \# @<br>Additionally, newline characters are not allowed.| |User|no| |zabbix|Drop privileges to a specific, existing user on the system.<br>Only has effect if run as 'root' and AllowRoot is disabled.| |UserParameter|no| | |User-defined parameter to monitor. There can be several user-defined parameters.<br>Format: UserParameter=<key>,<shell command><br>Note that shell command must not return empty string or EOL only.<br>Shell commands may have relative paths, if UserParameterDir parameter is specified.<br>Examples:<br>UserParameter=system.test,who\|wc -l<br>UserParameter=check\_cpu,./custom\_script.sh| |UserParameterDir|no| | |Default search path for UserParameter commands. If used, the agent will change its working directory to the one specified here before executing a command. Thereby, UserParameter commands can have a relative `./` prefix instead of a full path.<br>Only one entry is allowed.<br>Example: UserParameterDir=/opt/myscripts|
ja	#### パラメータ  |パラメータ|必須|範囲|デフォルト|説明| |--|--|--|--|----------| |Alias|no| | |項目キーのエイリアスを設定します。長くて複雑な項目キーを、より小さくて単純なものに置き換えるために使用できます。<br>複数の *Alias* パラメータが存在する場合があります。同じ *Alias* キーを持つ複数のパラメーターを使用できます。<br>異なる *Alias* キーが同じ項目キーを参照する場合があります。<br>*HostMetadataItem* ではエイリアスを使用できますが、*HostnameItem* パラメーターでは使用できません。<br>< br>例:<br><br>1.ユーザー'zabbix'の ID を取得しています。<br>Alias=zabbix.userid:vfs.file.regexp\[/etc/passwd,"\^zabbix:.:(\[0-9\]+)",, ,,\\1\]<br>これで、短縮キー **zabbix.userid** を使用してデータを取得できます。<br><br>2.デフォルトおよびカスタム パラメータで CPU 使用率を取得します。<br>Alias=cpu.util:system.cpu.util<br>Alias=cpu.util\[\*\]:system.cpu.util\[\*\]< br>これにより、**cpu.util** キーを使用してデフォルト パラメータで CPU 使用率を取得したり、**cpu.util\[all, idle, avg15\]** を使用して CPU 使用率に関する特定のデータを取得したりできます。< br><br>3.同じディスカバリー アイテムを処理する複数の [ローレベルディスカバリ](/manual/discovery/low_level_discovery) ルールを実行しています。<br>Alias=vfs.fs.discovery\[\*\]:vfs.fs.discovery<br> **vfs.fs.discovery** を使用して、ルールごとに異なるパラメーターを使用して複数の検出ルールを設定できます (例: **vfs.fs.discovery\[foo\]**、**vfs.fs.discovery\)。 [bar\]** など| |AllowKey|no| | |パターンに一致する項目キーの実行を許可します。 キー パターンは"\*"文字をサポートするワイルドカード式で、任意の数の任意の文字に一致します。<br>DenyKey と組み合わせて、複数のキー マッチング ルールを定義できます。 パラメータは出現順に従って1つずつ処理されます。<br>このパラメータはZabbix 5.0.0からサポートされています。<br>参照: [エージェントチェックの制限](/manual/config/items/restrict_checks)| |AllowRoot|no| |0|エージェントを'root'として開始できるようにします。 許可しない設定でエージェントが'root'によって開始された場合、エージェントは代わりにユーザー'zabbix'で開始しようとします。 通常のユーザーで開始した場合は影響ありません<br>0 - 許可しない<br>1 - 許可する| |BufferSend|no|1-3600|5|データを N 秒より長くバッファーに保持しない| |BufferSize|no|2-65535|100|メモリ バッファ内の値の最大数。 バッファがいっぱいの場合、エージェントは収集したすべてのデータを Zabbix サーバーまたはプロキシに送信します。| |DebugLevel|no|0-5|3|デバッグ レベルを指定します。<br>0 - Zabbix プロセスの開始と停止に関する基本情報<br>1 - 重要な情報<br>2 - エラー情報<br>3 - 警告<br>4 - デバッグ用 (多くの情報を生成) )<br>5 - 拡張デバッグ (さらに多くの情報を生成)| |DenyKey|no| | |パターンに一致する項目キーの実行を拒否します。 キー パターンは、任意の数の任意の文字に一致する'\*'文字をサポートするワイルドカード式です。<br>AllowKey と組み合わせて、複数のキー一致ルールを定義できます。 パラメータは出現順に従って1つずつ処理されます。<br>このパラメータはZabbix 5.0.0からサポートされています。<br>参照: [エージェントチェックの制限](/manual/config/items/restrict_checks).| |EnableRemoteCommands|no| |0|Zabbix サーバーからのリモート コマンドを許可するかどうか。 このパラメーターは**非推奨**です。代わりに、AllowKey=system.run\[\*\] または DenyKey=system.run\[\*\] を使用してください<br>これは、値に応じた AllowKey/DenyKey パラメータの内部エイリアスです: 0 - DenyKey=system.run\[\*\]<br>1 - AllowKey=system.run\[\*\]| |HostInterface|no|0-255 characters| |ホスト インターフェイスを定義するオプションのパラメータ。<br>ホスト インターフェイスは、ホストの [自動登録](/manual/discovery/auto_registration#using_dns_as_default_interface) プロセスで使用されます。<br>値が 255 文字の制限を超えると、エージェントはエラーを発行し、起動しません。<br>未定義の場合、HostInterfaceItem から値を取得します。<br>Zabbix 4.4.0 以降でサポートされています。| |HostInterfaceItem|no| | |ホスト インターフェースの取得に使用される項目を定義するオプションのパラメータ。<br>ホスト インターフェースは、ホストの [autoregistration](/manual/discovery/auto_registration#using_dns_as_default_interface) プロセスで使用されます。<br>自動登録リクエスト中、エージェントは警告メッセージをログに記録します。 <br>このオプションは、HostInterface が定義されていない場合にのみ使用されます。<br>Zabbix 4.4.0 以降でサポートされています。| |HostMetadata|no|0-255 characters| |ホストのメタデータを定義するオプションのパラメーター。 ホストのメタデータは、ホストの自動登録プロセス (アクティブなエージェント) でのみ使用されます。<br>未定義の場合、値は HostMetadataItem から取得されます。<br>指定された値が制限を超えているか、UTF-8 以外の文字列である場合、エージェントはエラーを発行して起動しません。| |HostMetadataItem|no| | |ホスト メタデータの取得に使用される *Zabbix エージェント* アイテムを定義するオプションのパラメーター。 このオプションは、HostMetadata が定義されていない場合にのみ使用されます。<br>UserParameters とエイリアスをサポートします。 AllowKey/DenyKey の値に関係なく、*system.run\[\]* をサポートします。<br>HostMetadataItem の値は、自動登録の試行ごとに取得され、ホストの自動登録プロセス (アクティブなエージェント) でのみ使用されます。<br>自動登録リクエスト中、エージェント 指定されたアイテムによって返された値が 255 文字の制限を超えている場合、警告メッセージがログに記録されます。<br>アイテムによって返された値は UTF-8 文字列である必要があり、それ以外の場合は無視されます。| |Hostname|no| |Set by HostnameItem|コンマで区切られた一意のホスト名のリスト。大文字と小文字が区別されます。<br>アクティブ チェックに必要であり、サーバーで構成されているホスト名と一致する必要があります。 未定義の場合、値は HostnameItem から取得されます。<br>使用できる文字: 英数字、'.'、' '、'\_'、および'-'。<br>最大長: ホスト名ごとに 128 文字、行全体で 2048 文字。| |HostnameItem|no| |system.hostname|ホスト名の取得に使用される *Zabbix エージェント* アイテムを定義するオプションのパラメーター。 このオプションは、ホスト名が定義されていない場合にのみ使用されます。<br>UserParameters またはエイリアスはサポートされていませんが、AllowKey/DenyKey の値に関係なく、*system.run\[\]* はサポートされています。<br>出力の長さは 512 KB に制限されています | |Include|no| | |個々のファイルまたはディレクトリ内のすべてのファイルを構成ファイルに含めることができます。<br>指定したディレクトリに関連ファイルのみを含めるために、パターン マッチングでアスタリスク ワイルドカード文字がサポートされています。 例: `/absolute/path/to/config/files/*.conf`.<br>制限については、[特記事項](special_notes_include)を参照してください。| |ListenBacklog|no|0 - INT\_MAX|SOMAXCONN|TCP キュー内の保留中の接続最大数。<br>デフォルト値はハードコードされた定数で、システムによって異なります。<br>サポートされている最大値はシステムによって異なります。値が高すぎると'実装で指定された最大値'に切り捨てられる場合があります。| |ListenIP|no| |0.0.0.0|エージェントがリッスンする IP アドレスのカンマ区切りのリスト。<br>バージョン 1.8.3 以降では複数の IP アドレスがサポートされています。| |ListenPort|no|1024-32767|10050|エージェントは、このポートでサーバーからの接続をリッスンします。| |LoadModule|no| | |エージェントの起動時にロードするモジュール。 モジュールは、エージェントの機能を拡張するために使用されます。<br>形式:<br>LoadModule=<module.so><br>LoadModule=<path/module.so><br>LoadModule=</abs\_path/module. so><br>モジュールが LoadModulePath で指定されたディレクトリに配置されているか、パスがモジュール名の前にある必要があります。 前のパスが絶対パス ('/'で始まる) の場合、LoadModulePath は無視されます。<br>複数の LoadModule パラメータを含めることができます。| |LoadModulePath|no| | |エージェント モジュールの場所へのフル パス。<br>デフォルトはコンパイル オプションによって異なります。| |LogFile|LogType が *file* に設定されている場合 yes<br>そうでない場合 no| | |ログファイル名| |LogFileSize|no|0-1024|1|ログ ファイルの最大サイズ (MB)<br>0 - 自動ログ ローテーションを無効にします。<br>*注*: ログ ファイルのサイズ制限に達し、ファイルのローテーションが何らかの理由で失敗した場合、既存のログ ファイルは切り捨てられ、新たに開始されます。| |LogType|no| |file|ログ出力タイプ:<br>*file* - LogFile パラメータで指定されたファイルにログを書き込みます。<br>*system* - ログを syslog に書き込みます。<br>*console* - ログを標準出力に書き込みます。<br>このパラメータはZabbix 3.0.0 以降でサポートされています。| |LogRemoteCommands|no| |0|実行されたシェル コマンドの警告としてのログを有効にします。<br>0 - 無効<br>1 - 有効<br>コマンドは、リモートで実行された場合にのみログに記録されます。 System.run\[\] が HostMetadataItem、HostInterfaceItem、または HostnameItem パラメーターによってローカルで起動された場合、ログ エントリは作成されません。| |MaxLinesPerSecond|no|1-1000|20|'ログ'および'イベントログ'のアクティブ チェックを処理するときに、エージェントが Zabbix サーバーまたはプロキシに 1 秒あたりに送信する新しい行の最大数。<br>指定された値は、パラメータ'maxlines'によって上書きされます。<br>'log' または 'eventlog' アイテム キーで提供されます。<br>*注*: Zabbix は、*MaxLinesPerSecond* で設定されたよりも 10 倍多くの新しい行を処理して、ログ項目で必要な文字列を検索します。| |PidFile|no| |/tmp/zabbix\_agentd.pid|PID ファイルの名前| |RefreshActiveChecks|no|60-3600|120|アクティブなチェックのリストが更新される頻度 (秒単位)。<br>アクティブなチェックの更新に失敗すると、60 秒後に次の更新が試行されることに注意してください。| |Server|yes, if StartAgents is not explicitly set to 0| | |カンマ区切りの IP アドレスのリスト。オプションで CIDR 表記、または Zabbix サーバーと Zabbix プロキシのホスト名。<br>着信接続は、ここにリストされているホストからのみ受け入れられます。<br>IPv6 サポートが有効になっている場合は、'127.0.0.1' , '::127.0.0.1', '::ffff:127.0.0.1' は同等に扱われ、'::/0' は任意の IPv4 または IPv6 アドレスを許可します.<br>'0.0.0.0/0' を使用して 任意の IPv4 アドレスを許可します。 -2.5.5).<br>例: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.domain<br>スペースを使用できます。| |ServerActive|no| | |アクティブ チェックを取得する Zabbix サーバー/プロキシ アドレスまたはクラスタ構成。<br>サーバー/プロキシ アドレスは、コロンで区切られた IP アドレスまたは DNS 名とオプションのポートです。<br>クラスタ構成は、セミコロンで区切られた 1 つまたは複数のサーバー アドレスです。<br><br>複数の Zabbix サーバー/クラスタと Zabbix プロキシをカンマで区切って指定できます。<br>各 Zabbix サーバー/クラスタから複数の Zabbix プロキシを指定しないでください。<br>Zabbix プロキシが指定されている場合は、Zabbix サーバー/クラスタそのプロキシには指定しないでください。<br>複数の独立した Zabbix サーバーを並行して使用するために、複数のカンマ区切りのアドレスを指定できます。スペースを使用できます。<br>ポートが指定されていない場合、デフォルトのポートが使用されます。<br>そのホストのポートが指定されている場合、IPv6 アドレスは角括弧で囲む必要があります。<br>ポートが指定されていない場合、IPv6 の角括弧アドレスはオプションです。<br>このパラメータが指定されていない場合、アクティブ チェックは無効になります。<br>Zabbix プロキシの例:<br>ServerActive=127.0.0.1:10051<br>複数のサーバーの例:<br>ServerActive= 127.0.0.1:20051,zabbix.domain,\[::1\]:30051,::1,\[12fc::1\]<br>高可用性の例:<br>ServerActive=zabbix.cluster.node1 ;zabbix.cluster.node2:20051;zabbix.cluster.node3<br>2 つのクラスターと 1 つのサーバーによる高可用性の例:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051,zabbix.cluster2 .node1;zabbix.cluster2.node2,zabbix.domain| |SourceIP|no| | |次の送信元 IP アドレス:<br>- Zabbix サーバーまたは Zabbix プロキシへの発信接続。<br>- 一部のアイテム (web.page.get、net.tcp.port など) の実行中に接続を確立する| |StartAgents|no|0-100|3|パッシブ チェックを処理する事前フォークされた zabbix\_agentd インスタンスの数。<br>0 に設定すると、パッシブ チェックが無効になり、エージェントはどの TCP ポートでもリッスンしません。| |Timeout|no|1-30|3|Timeout 秒の設定| |TLSAccept|TLS 証明書または PSK パラメータが定義されている場合 (*暗号化されていない* 接続の場合でも)はyes、それ以外の場合はno| | |受け入れる着信接続。 パッシブ チェックに使用されます。 コンマで区切って複数の値を指定できます。<br>*unencrypted* - 暗号化なしで接続を受け入れる (デフォルト)<br>*psk* - TLS と事前共有キー (PSK) を使用した接続を受け入れる<br>*cert* - TLS と証明書による接続を受け入れる<br>このパラメータは Zabbix 3.0.0 以降でサポートされています。| |TLSCAFile|no| | |Zabbix コンポーネント間の暗号化された通信に使用される、ピア証明書検証用の最上位 CA 証明書を含むファイルのフル パス名。<br>このパラメータは、Zabbix 3.0.0 以降でサポートされています。| |TLSCertFile|no| | |Zabbix コンポーネントとの暗号化された通信に使用される、エージェント証明書または証明書チェーンを含むファイルのフル パス名。<br>このパラメータは、Zabbix 3.0.0 以降でサポートされています。| |TLSCipherAll|no| | |GnuTLS 優先度文字列または OpenSSL (TLS 1.2) 暗号文字列。 証明書および PSK ベースの暗号化のデフォルトの暗号スイート選択基準をオーバーライドします。<br>例: TLS\_AES\_256\_GCM\_SHA384:TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br> このパラメータは、Zabbix 4.4.7 以降でサポートされています。| |TLSCipherAll13|no| | |TLS 1.3 の OpenSSL 1.1.1 以降の暗号文字列。 証明書および PSK ベースの暗号化のデフォルトの暗号スイート選択基準をオーバーライドします。<br>GnuTLS の例: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+ECDHE-PSK:+PSK:+AES- 128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL::+SIGN-ALL:+CTYPE-X.509<br>OpenSSL の例: EECDH +aRSA+AES128:RSA+aRSA+AES128:kECDHEPSK+AES128:kPSK+AES128<br>このパラメーターは、Zabbix 4.4.7 以降でサポートされています。| |TLSCipherCert|no| | |GnuTLS 優先度文字列または OpenSSL (TLS 1.2) 暗号文字列。 証明書ベースの暗号化のデフォルトの暗号スイート選択基準をオーバーライドします。<br>GnuTLS の例: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+AES-128-GCM:+AES-128-CBC: +AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509<br>OpenSSL の例: EECDH+aRSA+AES128:RSA+aRSA+AES128<br >このパラメーターは、Zabbix 4.4.7 以降でサポートされています。| |TLSCipherCert13|no| | |TLS 1.3 の OpenSSL 1.1.1 以降の暗号文字列。 証明書ベースの暗号化のデフォルトの暗号スイート選択基準をオーバーライドします。<br>このパラメータは、Zabbix 4.4.7 以降でサポートされています。| |TLSCipherPSK|no| | |GnuTLS 優先度文字列または OpenSSL (TLS 1.2) 暗号文字列。 PSK ベースの暗号化のデフォルトの暗号スイート選択基準をオーバーライドします。<br>GnuTLS の例: NONE:+VERS-TLS1.2:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC: +AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL<br>OpenSSLの例: kECDHEPSK+AES128:kPSK+AES128<br>このパラメータはZabbix 4.4.7からサポートされています。| |TLSCipherPSK13|no| | |TLS 1.3 の OpenSSL 1.1.1 以降の暗号文字列。 PSK ベースの暗号化のデフォルトの暗号スイート選択基準をオーバーライドします。<br>例: TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>このパラメータは、Zabbix 4.4.7 以降でサポートされています。| |TLSConnect|TLS 証明書または PSK パラメータが定義されている場合 (*暗号化されていない* 接続の場合でも)はyes<br>それ以外の場合はno| | |エージェントが Zabbix サーバーまたはプロキシに接続する方法。 アクティブ チェックに使用されます。 指定できる値は 1 つだけです。<br>*unencrypted* - 暗号化なしで接続 (デフォルト)<br>*psk* - TLS と事前共有キー (PSK) を使用して接続<br>*cert* - TLS と 証明書<br>このパラメータは、Zabbix 3.0.0 以降でサポートされています。| |TLSCRLFile|no| | |失効した証明書を含むファイルのフル パス名。 このパラメータは、Zabbix コンポーネントとの暗号化通信に使用されます。<br>このパラメータは、Zabbix 3.0.0 以降でサポートされています。| |TLSKeyFile|no| | |Zabbix コンポーネントとの暗号化された通信に使用されるエージェントの秘密鍵を含むファイルのフル パス名。<br>このパラメータは、Zabbix 3.0.0 以降でサポートされています。| |TLSPSKFile|no| | |Zabbix コンポーネントとの暗号化通信に使用されるエージェントの事前共有キーを含むファイルのフル パス名。<br>このパラメータは、Zabbix 3.0.0 以降でサポートされています。| |TLSPSKIdentity|no| | |Zabbix サーバーとの暗号化された通信に使用される事前共有キー ID 文字列。<br>このパラメータは Zabbix 3.0.0 以降でサポートされています。| |TLSServerCertIssuer|no| | |許可されたサーバー (プロキシ) 証明書の発行者。<br>このパラメータは Zabbix 3.0.0 以降でサポートされています。| |TLSServerCertSubject|no| | |許可されたサーバー (プロキシ) 証明書のサブジェクト。<br>このパラメータは Zabbix 3.0.0 以降でサポートされています。| |UnsafeUserParameters|no|0,1|0|ユーザー定義パラメータの引数にすべての文字を渡せるか。<br>0 - 許可しない<br>1 - 許可する<br>次の文字は使用できません:<br>\\ ' " \` \* ? \[ \] { } \~ $ ! & ; ( ) < > \| \# @<br>さらに、改行文字は使用できません。| |User|no| |zabbix|システム上の特定の既存のユーザーに特権をドロップします。<br>'root'として実行し、AllowRoot が無効になっている場合にのみ効果があります。| |UserParameter|no| | |監視するユーザー定義のパラメーター。 複数のユーザー定義パラメータを指定できます。<br>形式: UserParameter=<キー>,<シェル コマンド><br>シェル コマンドは、空の文字列または EOL のみを返してはならないことに注意してください。<br>シェル コマンドには、相対パスを指定できます。 UserParameterDir パラメータが指定されている場合。<br>例:<br>UserParameter=system.test,who\|wc -l<br>UserParameter=check\_cpu,./custom\_script.sh| |UserParameterDir|no| | |UserParameter コマンドのデフォルトの検索パス。 使用すると、エージェントはコマンドを実行する前に、ここで指定されたディレクトリに作業ディレクトリを変更します。 これにより、UserParameter コマンドは、フル パスの代わりに相対 `./` プレフィックスを持つことができます。<br>許可されるエントリは 1 つだけです。<br>例: UserParameterDir=/opt/myscripts|

en-us	#### Parameters  |Parameter|<|Mandatory|Range|Default|Description| |-|----------|----------|----------|----------|--------------------------------------------------| |Alias|<|no| | |Sets an alias for an item key. It can be used to substitute long and complex item key with a smaller and simpler one.<br>Multiple *Alias* parameters may be present. Multiple parameters with the same *Alias* key are allowed.<br>Different *Alias* keys may reference the same item key.<br>Aliases can be used in *HostMetadataItem* but not in *HostnameItem* parameters.<br><br>Examples:<br><br>1. Retrieving the ID of user 'zabbix'.<br>Alias=zabbix.userid:vfs.file.regexp\[/etc/passwd,"\^zabbix:.:(\[0-9\]+)",,,,\\1\]<br>Now shorthand key **zabbix.userid** may be used to retrieve data.<br><br>2. Getting CPU utilization with default and custom parameters.<br>Alias=cpu.util:system.cpu.util<br>Alias=cpu.util\[\*\]:system.cpu.util\[\*\]<br>This allows use **cpu.util** key to get CPU utilization percentage with default parameters as well as use **cpu.util\[all, idle, avg15\]** to get specific data about CPU utilization.<br><br>3. Running multiple [low-level discovery](/manual/discovery/low_level_discovery) rules processing the same discovery items.<br>Alias=vfs.fs.discovery\[\*\]:vfs.fs.discovery<br>Now it is possible to set up several discovery rules using **vfs.fs.discovery** with different parameters for each rule, e.g., **vfs.fs.discovery\[foo\]**, **vfs.fs.discovery\[bar\]**, etc.| |AllowKey|<|no| | |Allow execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "\*" character to match any number of any characters.<br>Multiple key matching rules may be defined in combination with DenyKey. The parameters are processed one by one according to their appearance order.<br>This parameter is supported since Zabbix 5.0.0.<br>See also: [Restricting agent checks](/manual/config/items/restrict_checks).| |BufferSend|<|no|1-3600|5|The time interval in seconds which determines how often values are sent from the buffer to Zabbix server.<br>Note, that if the buffer is full, the data will be sent sooner.| |BufferSize|<|no|2-65535|100|Maximum number of values in a memory buffer. The agent will send all collected data to Zabbix server or proxy if the buffer is full.<br>This parameter should only be used if persistent buffer is disabled (*EnablePersistentBuffer=0*).| |ControlSocket|<|no| |\\\\.\\pipe\\agent.sock|The control socket, used to send runtime commands with '-R' option.| |DebugLevel|<|no|0-5|3|Specifies debug level:<br>0 - basic information about starting and stopping of Zabbix processes<br>1 - critical information<br>2 - error information<br>3 - warnings<br>4 - for debugging (produces lots of information)<br>5 - extended debugging (produces even more information)| |DenyKey|<|no| | |Deny execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "\*" character to match any number of any characters.<br>Multiple key matching rules may be defined in combination with AllowKey. The parameters are processed one by one according to their appearance order.<br>This parameter is supported since Zabbix 5.0.0.<br>See also: [Restricting agent checks](/manual/config/items/restrict_checks).| |EnablePersistentBuffer|<|no|0-1|0|Enable usage of local persistent storage for active items.<br>0 - disabled<br>1 - enabled<br>If persistent storage is disabled, the memory buffer will be used.| |ForceActiveChecksOnStart|<|no|0-1|0 |Perform active checks immediately after restart for the first received configuration.<br>0 - disabled<br>1 - enabled<br>Also available as per plugin configuration parameter, for example: `Plugins.Uptime.System.ForceActiveChecksOnStart=1` <br> Supported since Zabbix 6.0.2. | |HostInterface|<|no|0-255 characters| |Optional parameter that defines host interface.<br>Host interface is used at host autoregistration process.<br>An agent will issue an error and not start if the value is over the limit of 255 characters.<br>If not defined, value will be acquired from HostInterfaceItem.<br>Supported since Zabbix 4.4.0.| |HostInterfaceItem|<|no| | |Optional parameter that defines an item used for getting host interface.<br>Host interface is used at host autoregistration process.<br>During an autoregistration request an agent will log a warning message if the value returned by specified item is over limit of 255 characters.<br>This option is only used when HostInterface is not defined.<br>Supported since Zabbix 4.4.0.| |HostMetadata|<|no|0-255 characters| |Optional parameter that defines host metadata. Host metadata is used at host autoregistration process.<br>An agent will issue an error and not start if the specified value is over the limit or a non-UTF-8 string.<br>If not defined, the value will be acquired from HostMetadataItem.| |HostMetadataItem|<|no| | |Optional parameter that defines an item used for getting host metadata. Host metadata item value is retrieved on each autoregistration attempt for host autoregistration process.<br>During an autoregistration request an agent will log a warning message if the value returned by the specified item is over the limit of 255 characters.<br>This option is only used when HostMetadata is not defined.<br>Supports UserParameters and aliases. Supports *system.run\[\]* regardless of *EnableRemoteCommands* value.<br>The value returned by the item must be a UTF-8 string otherwise it will be ignored.| |Hostname|<|no| |Set by HostnameItem|List of comma-delimited unique, case-sensitive hostnames.<br>Required for active checks and must match hostnames as configured on the server. Value is acquired from HostnameItem if undefined.<br>Allowed characters: alphanumeric, '.', ' ', '\_' and '-'.<br>Maximum length: 128 characters per hostname, 2048 characters for the entire line.| |HostnameItem|<|no| |system.hostname|Item used for generating Hostname if it is not defined. Ignored if Hostname is defined.<br>Does not support UserParameters or aliases, but does support *system.run\[\]* regardless of *EnableRemoteCommands* value.<br>The output length is limited to 512KB.| |Include|<|no| | |You may include individual files or all files in a directory in the configuration file.<br>During the installation Zabbix will create the include directory in /usr/local/etc, unless modified during the compile time.<br>To only include relevant files in the specified directory, the asterisk wildcard character is supported for pattern matching. For example: `/absolute/path/to/config/files/*.conf`.<br>Since Zabbix 6.0.0 a path can be relative to *zabbix\_agent2.win.conf* file location.<br>See [special notes](special_notes_include) about limitations.| |ListenIP|<|no| |0.0.0.0|List of comma-delimited IP addresses that the agent should listen on.<br>The first IP address is sent to Zabbix server, if connecting to it, to retrieve the list of active checks.| |ListenPort|<|no|1024-32767|10050|Agent will listen on this port for connections from the server.| |LogFile|<|yes, if LogType is set to *file*, otherwise<br>no| |c:\\zabbix\_agent2.log|Log file name if LogType is 'file'.| |LogFileSize|<|no|0-1024|1|Maximum size of log file in MB.<br>0 - disable automatic log rotation.<br>*Note*: If the log file size limit is reached and file rotation fails, for whatever reason, the existing log file is truncated and started anew.| |LogType|<|no| |file|Specifies where log messages are written to:<br>*file* - file specified by LogFile parameter,<br>*console* - standard output.| |PersistentBufferFile|<|no| | |The file, where Zabbix Agent2 should keep SQLite database.<br>Must be a full filename.<br>This parameter is only used if persistent buffer is enabled (*EnablePersistentBuffer=1*).| |PersistentBufferPeriod|<|no|1m-365d|1h|The time period for which data should be stored, when there is no connection to the server or proxy. Older data will be lost. Log data will be preserved.<br>This parameter is only used if persistent buffer is enabled (*EnablePersistentBuffer=1*).| |Plugins|<|no| | |Since Zabbix 6.0.0 most of the plugins have their own [configuration files](/manual/appendix/config/zabbix_agent2_plugins). The agent configuration file contains plugin parameters listed below.| | |Plugins.Log.MaxLinesPerSecond|no|1-1000|20|Maximum number of new lines the agent will send per second to Zabbix server or proxy when processing 'log' and 'eventlog' active checks.<br>The provided value will be overridden by the parameter 'maxlines',<br>provided in 'log' or 'eventlog' item key.<br>*Note*: Zabbix will process 10 times more new lines than set in *MaxLinesPerSecond* to seek the required string in log items.<br>This parameter is supported since 4.4.2 and replaces MaxLinesPerSecond.| |^|Plugins.SystemRun.LogRemoteCommands|no| |0|Enable logging of executed shell commands as warnings.<br>0 - disabled<br>1 - enabled<br>Commands will be logged only if executed remotely. Log entries will not be created if system.run\[\] is launched locally by HostMetadataItem, HostInterfaceItem or HostnameItem parameters.<br>This parameter is supported since 4.4.2 and replaces LogRemoteCommands.| |PluginSocket|<|no| |\\\\.\pipe\agent.plugin.sock|Path to unix socket for loadable plugin communications.| |PluginTimeout|<|no|1-30 |Global timeout |Timeout for connections with loadable plugins.| |RefreshActiveChecks|<|no|60-3600|120|How often the list of active checks is refreshed, in seconds.<br>Note that after failing to refresh active checks the next refresh will be attempted after 60 seconds.| |Server|<|yes| | |List of comma-delimited IP addresses, optionally in CIDR notation, or DNS names of Zabbix servers and Zabbix proxies.<br>Incoming connections will be accepted only from the hosts listed here.<br>If IPv6 support is enabled then '127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address.<br>'0.0.0.0/0' can be used to allow any IPv4 address.<br>Example: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com<br>Spaces are allowed.| |ServerActive|<|no| | |Zabbix server/proxy address or cluster configuration to get active checks from.<br>Server/proxy address is IP address or DNS name and optional port separated by colon.<br>Cluster configuration is one or more server addresses separated by semicolon.<br>Multiple Zabbix servers/clusters and Zabbix proxies can be specified, separated by comma.<br>More than one Zabbix proxy should not be specified from each Zabbix server/cluster.<br>If Zabbix proxy is specified then Zabbix server/cluster for that proxy should not be specified.<br>Multiple addresses can be provided to use several independent Zabbix servers in parallel. Spaces are allowed.<br>If port is not specified, default port is used.<br>IPv6 addresses must be enclosed in square brackets if port for that host is specified.<br>If port is not specified, square brackets for IPv6 addresses are optional.<br>If this parameter is not specified, active checks are disabled.<br>Example for Zabbix proxy:<br>ServerActive=127.0.0.1:10051<br>Example for multiple servers:<br>ServerActive=127.0.0.1:20051,zabbix.domain,\[::1\]:30051,::1,\[12fc::1\]<br>Example for high availability:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051;zabbix.cluster.node3<br>Example for high availability with two clusters and one server:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051,zabbix.cluster2.node1;zabbix.cluster2.node2,zabbix.domain| |SourceIP|<|no| | |Source IP address for:<br>- outgoing connections to Zabbix server or Zabbix proxy;<br>- making connections while executing some items (web.page.get, net.tcp.port, etc.)| |StatusPort|<|no|1024-32767| |If set, agent will listen on this port for HTTP status requests (http://localhost:<port>/status).| |Timeout|<|no|1-30|3|Spend no more than Timeout seconds on processing.| |TLSAccept|<|yes, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no| | |What incoming connections to accept. Used for a passive checks. Multiple values can be specified, separated by comma:<br>*unencrypted* - accept connections without encryption (default)<br>*psk* - accept connections with TLS and a pre-shared key (PSK)<br>*cert* - accept connections with TLS and a certificate| |TLSCAFile|<|no| | |Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components.| |TLSCertFile|<|no| | |Full pathname of a file containing the agent certificate or certificate chain, used for encrypted communications with Zabbix components.| |TLSConnect|<|yes, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no| | |How the agent should connect to Zabbix server or proxy. Used for active checks. Only one value can be specified:<br>*unencrypted* - connect without encryption (default)<br>*psk* - connect using TLS and a pre-shared key (PSK)<br>*cert* - connect using TLS and a certificate| |TLSCRLFile|<|no| | |Full pathname of a file containing revoked certificates. This parameter is used for encrypted communications with Zabbix components.| |TLSKeyFile|<|no| | |Full pathname of a file containing the agent private key used for encrypted communications with Zabbix components.| |TLSPSKFile|<|no| | |Full pathname of a file containing the agent pre-shared key used for encrypted communications with Zabbix components.| |TLSPSKIdentity|<|no| | |Pre-shared key identity string, used for encrypted communications with Zabbix server.| |TLSServerCertIssuer|<|no| | |Allowed server (proxy) certificate issuer.| |TLSServerCertSubject|<|no| | |Allowed server (proxy) certificate subject.| |UnsafeUserParameters|<|no|0,1|0|Allow all characters to be passed in arguments to user-defined parameters.<br>The following characters are not allowed:<br>\\ ' " \` \* ? \[ \] { } \~ $ ! & ; ( ) < > \| \# @<br>Additionally, newline characters are not allowed.| |UserParameter|<|no| | |User-defined parameter to monitor. There can be several user-defined parameters.<br>Format: UserParameter=<key>,<shell command><br>Note that shell command must not return empty string or EOL only.<br>Shell commands may have relative paths, if UserParameterDir parameter is specified.<br>Examples:<br>UserParameter=system.test,who\|wc -l<br>UserParameter=check\_cpu,./custom\_script.sh| |UserParameterDir|<|no| | |Default search path for UserParameter commands. If used, the agent will change its working directory to the one specified here before executing a command. Thereby, UserParameter commands can have a relative `./` prefix instead of a full path.<br>Only one entry is allowed.<br>Example: UserParameterDir=/opt/myscripts|
ja	#### パラメータ  |パラメータ|<|必須|範囲|デフォルト|説明| |-|----------|----------|----------|----------|--------------------------------------------------| |Alias|<|no| | |項目キーのエイリアスを設定します。長くて複雑な項目キーを、より短くて単純なものに置き換えるために使用できます。<br>複数の *Alias* パラメータが存在する場合があります。同じ *Alias* キーを持つ複数のパラメーターを使用できます。<br>異なる *Alias* キーが同じ項目キーを参照する場合があります。<br>*HostMetadataItem* ではエイリアスを使用できますが、*HostnameItem* パラメーターでは使用できません。<br>< br>例:<br><br>1.ユーザー`zabbix`の ID を取得します。<br>Alias=zabbix.userid:vfs.file.regexp\[/etc/passwd,"\^zabbix:.:(\[0-9\]+)",, ,,\\1\]<br>これで短縮キー **zabbix.userid** を使用してデータを取得できます。<br><br>2.デフォルトおよびカスタム パラメータで CPU 使用率を取得します。<br>Alias=cpu.util:system.cpu.util<br>Alias=cpu.util\[\*\]:system.cpu.util\[\*\]< br>これにより、**cpu.util** キーを使用してデフォルト パラメータで CPU 使用率を取得したり、**cpu.util\[all, idle, avg15\]** を使用して CPU 使用率に関する特定のデータを取得したりできます。< br><br>3.同じディスカバリー アイテムを処理する複数の [ローレベルディスカバリ](/manual/discovery/low_level_discovery) ルールを実行します。<br>Alias=vfs.fs.discovery\[\*\]:vfs.fs.discovery<br> **vfs.fs.discovery** を使用して、ルールごとに異なるパラメーターを使用して複数のディスカバリルールを設定できます (例: **vfs.fs.discovery\[foo\]**、**vfs.fs.discovery\)。 [bar\]** など| |AllowKey|<|no| | |パターンに一致する項目キーの実行を許可します。 キー パターンは、任意の数の任意の文字に一致する"\*"文字をサポートするワイルドカード式です。<br>DenyKey と組み合わせて、複数のキー マッチング ルールを定義できます。 パラメーターは、出現順序に従って 1 つずつ処理されます。<br>このパラメータは、Zabbix 5.0.0 以降でサポートされています。<br>参照: [エージェント チェックの制限](/manual/config/items/restrict_checks)| |BufferSend|<|no|1-3600|5|値がバッファからZabbixサーバーに送信される時間間隔(秒単位)。<br>バッファがいっぱいの場合、データはより早く送信されることに注意してください。| |BufferSize|<|no|2-65535|100|メモリ バッファ内の値の最大数。 エージェントは、バッファがいっぱいになると、収集されたすべてのデータを Zabbix サーバーまたはプロキシに送信します。<br>このパラメータは、永続バッファが無効になっている場合 (*EnablePersistentBuffer=0*) にのみ使用してください。| |ControlSocket|<|no| |\\\\.\\pipe\\agent.sock|'-R'オプションを使用して実行時コマンドを送信するために使用される制御ソケット。| |DebugLevel|<|no|0-5|3|デバッグ レベルを指定します。<br>0 - Zabbix プロセスの開始と停止に関する基本情報<br>1 - 重要な情報<br>2 - エラー情報<br>3 - 警告<br>4 - デバッグ用 (多くの情報を生成) )<br>5 - 拡張デバッグ (さらに多くの情報を生成)| |DenyKey|<|no| | |パターンに一致する項目キーの実行を拒否します。 キー パターンは、任意の数の任意の文字に一致する"\*"文字をサポートするワイルドカード式です。<br>AllowKey と組み合わせて、複数のキー一致ルールを定義できます。 パラメータは出現順に従って1つずつ処理されます。<br>このパラメータはZabbix 5.0.0からサポートされています。<br>参照: [エージェントチェックの制限](/manual/config/items/restrict_checks).| |EnablePersistentBuffer|<|no|0-1|0|アクティブなアイテムのローカル永続ストレージの使用を有効にします。<br>0 - 無効<br>1 - 有効<br>永続ストレージが無効の場合、メモリ バッファが使用されます。| |ForceActiveChecksOnStart|<|no|0-1|0 |最初に受信した構成の再起動直後にアクティブ チェックを実行します。<br>0 - 無効<br>1 - 有効<br>プラグイン構成パラメーターごとにも利用可能です。例: `Plugins.Uptime.System.ForceActiveChecksOnStart=1` < br> Zabbix 6.0.2 以降でサポートされています。| |HostInterface|<|no|0～255文字| |ホスト インターフェースを定義するオプション パラメータ。<br>ホスト インターフェースは、ホストの自動登録プロセスで使用されます。<br>値が 255 文字の制限を超えると、エージェントはエラーを発行し、起動しません。<br>定義されていない場合、値 HostInterfaceItem から取得されます。<br>Zabbix 4.4.0 以降でサポートされています。| |HostInterfaceItem|<|no| | |ホスト インターフェースの取得に使用されるアイテムを定義するオプション パラメータ。<br>ホスト インターフェースは、ホストの自動登録プロセスで使用されます。<br>自動登録リクエスト中に、指定されたアイテムによって返される値が 255 の制限を超えている場合、エージェントは警告メッセージを記録します。 <br>このオプションは、HostInterface が定義されていない場合にのみ使用されます。<br>Zabbix 4.4.0 以降でサポートされています。| |HostMetadata|<|no|0～255文字| |ホストのメタデータを定義するオプションのパラメーター。 ホスト メタデータは、ホストの自動登録プロセスで使用されます。<br>指定された値が制限を超えているか、UTF-8 以外の文字列である場合、エージェントはエラーを発行し、起動しません。<br>未定義の場合、値は HostMetadataItem から取得されます。| |HostMetadataItem|<|no| | |ホスト メタデータの取得に使用される項目を定義するオプションのパラメーター。 ホスト メタデータ アイテム値は、ホスト自動登録プロセスの各自動登録試行で取得されます。<br>自動登録リクエスト中に、指定されたアイテムによって返される値が 255 文字の制限を超えている場合、エージェントは警告メッセージをログに記録します。<br>このオプション HostMetadata が定義されていない場合にのみ使用されます。<br>UserParameters とエイリアスをサポートします。 *EnableRemoteCommands*の値に関係なく、*system.run\[\]* をサポートします。<br>アイテムによって返される値は、UTF-8 文字列でなければなりません。それ以外の場合は無視されます。| |Hostname|<|no| |HostnameItem で設定|コンマで区切られた一意のホスト名のリスト。大文字と小文字が区別されます。<br>アクティブ チェックに必要であり、サーバーで構成されているホスト名と一致する必要があります。 未定義の場合、値は HostnameItem から取得されます。<br>使用できる文字: 英数字、'.'、' '、'\_'、および'-'。<br>最大長: ホスト名ごとに 128 文字、行全体で 2048 文字。| |HostnameItem|<|no| |system.hostname|ホスト名が定義されていない場合に生成するために使用されるアイテム。 Hostname が定義されている場合は無視されます。<br>UserParameters またはエイリアスはサポートされませんが、*EnableRemoteCommands*の値に関係なく、*system.run\[\]* はサポートされます。<br>出力の長さは 512 KB に制限されています。| |Include|<|no| | |個々のファイルまたはディレクトリ内のすべてのファイルを構成ファイルに含めることができます。<br>コンパイル時に変更されない限り、Zabbix はインストール中に /usr/local/etc にインクルード ディレクトリを作成します。<br>関連するもののみを含めるには 指定したディレクトリ内のファイルの場合、パターン マッチングでアスタリスク ワイルドカード文字がサポートされます。例: `/absolute/path/to/config/files/*.conf`<br>Zabbix 6.0.0以降、パスは*zabbix\_agent2.win.conf*ファイルの場所からの相対パスにすることができます。<br>制限事項については[特記事項](special_notes_include)を参照してください。| |ListenIP|<|no| |0.0.0.0|エージェントがリッスンするカンマ区切りの IP アドレスのリスト。<br>Zabbix サーバーに接続している場合、アクティブなチェックのリストを取得するために、最初の IP アドレスが Zabbix サーバーに送信されます。| |ListenPort|<|no|1024-32767|10050|エージェントは、この番号のポートでサーバーからの接続をリッスンします。| |LogFile|<|LogType が *file* に設定されている場合:yes<br>それ以外の場合:no| |c:\\zabbix\_agent2.log|LogType が'file'の場合のログ ファイル名。| |LogFileSize|<|no|0-1024|1|ログ ファイルの最大サイズ (MB)。<br>0 - ログの自動ローテーションを無効にします。<br>*注*: ログ ファイルのサイズ制限に達し、ファイルのローテーションが何らかの理由で失敗した場合、既存のログ ファイルは切り捨てられ、新たに作成されます。| |LogType|<|no| |file|ログ メッセージが書き込まれる場所を指定します。<br>*file* - LogFile パラメータで指定されたファイル<br>*console* - 標準出力。| |PersistentBufferFile|<|no| | |Zabbix Agent2 が SQLite データベースを保持するファイル。<br>完全なファイル名である必要があります。<br>このパラメータは、永続バッファが有効な場合 (*EnablePersistentBuffer=1*) にのみ使用されます。| |PersistentBufferPeriod|<|no|1m-365d|1h|サーバーまたはプロキシへの接続がない場合に、データを保存する期間。 古いデータは失われます。 ログ データは保持されます。<br>このパラメータは、永続バッファが有効な場合にのみ使用されます (*EnablePersistentBuffer=1*)| |Plugins|<|no| | |Zabbix 6.0.0以降、ほとんどのプラグインには独自の[設定ファイル](/manual/appendix/config/zabbix_agent2_plugins)があります。 エージェント設定ファイルには、以下に示すプラグイン パラメータが含まれています。| | |Plugins.Log.MaxLinesPerSecond|no|1-1000|20|'ログ'および'イベントログ'のアクティブ チェックを処理するときに、エージェントが Zabbix サーバーまたはプロキシに 1 秒あたりに送信する新しい行の最大数。<br>指定された値は、パラメータ'maxlines'によって上書きされます。<br>'log' または 'eventlog' アイテム キーで提供されます。<br>*注*: Zabbix は、*MaxLinesPerSecond* で設定されたよりも 10 倍多くの新しい行を処理して、ログ項目で必要な文字列を検索します。<br>このパラメータは 4.4.2 以降でサポートされており、MaxLinesPerSecond を置き換えます。| |^|Plugins.SystemRun.LogRemoteCommands|no| |0|実行されたシェル コマンドのログを警告として有効にします。<br>0 - 無効<br>1 - 有効<br>コマンドは、リモートで実行された場合にのみログに記録されます。 system.run\[\] が HostMetadataItem、HostInterfaceItem、または HostnameItem パラメータによってローカルで起動された場合、ログ エントリは作成されません。<br>このパラメータは 4.4.2 以降でサポートされ、LogRemoteCommands を置き換えます。| |PluginSocket|<|no| |\\\\.\pipe\agent.plugin.sock|ロード可能なプラグイン通信用の UNIX ソケットへのパス。| |PluginTimeout|<|no|1-30 |Global timeout |ロード可能なプラグインとの接続のタイムアウト。| |RefreshActiveChecks|<|no|60-3600|120|アクティブ チェックのリストを更新する頻度 (秒単位)。<br>アクティブ チェックの更新に失敗すると、60 秒後に次の更新が試行されることに注意してください。| |Server|<|yes| | |カンマ区切りの IP アドレスのリスト (オプションで CIDR 表記、または Zabbix サーバーと Zabbix プロキシの DNS 名)。<br>着信接続は、ここにリストされているホストからのみ受け入れられます。<br>IPv6 サポートが有効になっている場合は、'127.0. 0.1'、'::ffff:127.0.0.1' は同等に扱われ、'::/0' はすべての IPv4 または IPv6 アドレスを許可します。<br>'0.0.0.0/0' はすべての IPv4 アドレスを許可するために使用できます。< br>例: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com<br>スペースを使用できます。| |ServerActive|<|no| | |アクティブ チェックを取得する Zabbix サーバー/プロキシ アドレスまたはクラスタ構成。<br>サーバー/プロキシ アドレスは、コロンで区切られた IP アドレスまたは DNS 名とオプションのポートです。<br>クラスタ構成は、セミコロンで区切られた 1 つまたは複数のサーバー アドレスです。<br> br>複数の Zabbix サーバー/クラスタと Zabbix プロキシをカンマで区切って指定できます。<br>各 Zabbix サーバー/クラスタから複数の Zabbix プロキシを指定しないでください。<br>Zabbix プロキシが指定されている場合は、Zabbix サーバー/クラスタそのプロキシは指定しないでください。<br>複数の独立した Zabbix サーバーを並行して使用するために、複数のアドレスを指定できます。スペースを使用できます。<br>ポートが指定されていない場合、デフォルトのポートが使用されます。<br>そのホストのポートが指定されている場合、IPv6 アドレスは角括弧で囲む必要があります。<br>ポートが指定されていない場合、IPv6 の角括弧アドレスはオプションです。<br>このパラメータが指定されていない場合、アクティブ チェックは無効になります。<br>Zabbix プロキシの例:<br>ServerActive=127.0.0.1:10051<br>複数のサーバーの例:<br>ServerActive= 127.0.0.1:20051,zabbix.domain,\[::1\]:30051,::1,\[12fc::1\]<br>高可用性の例:<br>ServerActive=zabbix.cluster.node1 ;zabbix.cluster.node2:20051;zabbix.cluster.node3<br>2 つのクラスターと 1 つのサーバーによる高可用性の例:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051,zabbix.cluster2 .node1;zabbix.cluster2.node2,zabbix.domain| |SourceIP|<|no| | |次の送信元 IP アドレス:<br>- Zabbix サーバーまたは Zabbix プロキシへの発信接続。<br>- 一部のアイテム (web.page.get、net.tcp.port など) の実行中に接続を確立する| |StatusPort|<|no|1024-32767| |設定されている場合、エージェントはこのポートで HTTP ステータス リクエストをリッスンします (http://localhost:<port>/status)| |Timeout|<|no|1-30|3|処理にかかる時間は Timeout 秒以内です。| |TLSAccept|<|TLS 証明書または PSK パラメータが定義されている場合 (*暗号化されていない* 接続の場合でも):yes、それ以外の場合:no| | |受け入れる着信接続。 パッシブ チェックに使用されます。 コンマで区切って複数の値を指定できます。<br>*unencrypted* - 暗号化なしで接続を受け入れる (デフォルト)<br>*psk* - TLS と事前共有キー (PSK) を使用した接続を受け入れる<br>*cert* - TLS と証明書による接続を受け入れる| |TLSCAFile|<|no| | |Zabbix コンポーネント間の暗号化された通信に使用される、ピア証明書検証用の最上位 CA 証明書を含むファイルのフル パス名。| |TLSCertFile|<|no| | |Zabbix コンポーネントとの暗号化通信に使用される、エージェント証明書または証明書チェーンを含むファイルのフル パス名。| |TLSConnect|<|TLS 証明書または PSK パラメータが定義されている場合 (*暗号化されていない* 接続の場合でも):yes、それ以外の場合:no| | |エージェントが Zabbix サーバーまたはプロキシに接続する方法。 アクティブ チェックに使用されます。 指定できる値は 1 つだけです。<br>*unencrypted* - 暗号化なしで接続 (デフォルト)<br>*psk* - TLS と事前共有キー (PSK) を使用して接続<br>*cert* - TLS と 証明書| |TLSCRLFile|<|no| | |失効した証明書を含むファイルのフル パス名。 このパラメータは、Zabbix コンポーネントとの暗号化通信に使用されます。| |TLSKeyFile|<|no| | |Zabbix コンポーネントとの暗号化された通信に使用されるエージェントの秘密鍵を含むファイルのフル パス名。| |TLSPSKFile|<|no| | |Zabbix コンポーネントとの暗号化された通信に使用されるエージェントの事前共有キーを含むファイルのフル パス名。| |TLSPSKIdentity|<|no| | |Zabbix サーバーとの暗号化された通信に使用される事前共有キー ID 文字列。| |TLSServerCertIssuer|<|no| | |許可されたサーバー (プロキシ) 証明書の発行者。| |TLSServerCertSubject|<|no| | |許可されたサーバー (プロキシ) 証明書のサブジェクト。| |UnsafeUserParameters|<|no|0,1|0|ユーザー定義パラメータの引数にすべての文字を渡すことができます。<br>ただし次の文字は使用できません:<br>\\ ' " \` \* ? \[ \] { } \~ $ ! & ; ( ) < > \| \# @<br>さらに、改行文字は使用できません。| |UserParameter|<|no| | |監視するユーザー定義のパラメーター。 いくつかのユーザー定義パラメーターが存在する場合があります。<br>書式: UserParameter=<キー>,<シェルコマンド><br>シェル コマンドは、空の文字列または EOL のみを返してはならないことに注意してください。<br>UserParameterDir パラメータが指定されている場合、シェル コマンドは相対パスを持つことができます。<br>例:<br>UserParameter=system.test,who\|wc -l<br>UserParameter=check\_cpu,./custom\_script.sh| |UserParameterDir|<|no| | |UserParameter コマンドのデフォルトの検索パス。 使用すると、エージェントはコマンドを実行する前に、ここで指定されたディレクトリに作業ディレクトリを変更します。 これにより、UserParameter コマンドは、フル パスの代わりに相対 `./` プレフィックスを持つことができます。<br>許可されるエントリは 1 つだけです。<br>例: UserParameterDir=/opt/myscripts|

en-us	#### Parameters  |Parameter|<|Mandatory|Range|Default|Description| |-|----------|----------|----------|----------|--------------------------------------------------| |Alias|<|no| | |Sets an alias for an item key. It can be used to substitute long and complex item key with a smaller and simpler one.<br>Multiple *Alias* parameters may be present. Multiple parameters with the same *Alias* key are allowed.<br>Different *Alias* keys may reference the same item key.<br>Aliases can be used in *HostMetadataItem* but not in *HostnameItem* parameters.<br><br>Examples:<br><br>1. Retrieving the ID of user 'zabbix'.<br>Alias=zabbix.userid:vfs.file.regexp\[/etc/passwd,"\^zabbix:.:(\[0-9\]+)",,,,\\1\]<br>Now shorthand key **zabbix.userid** may be used to retrieve data.<br><br>2. Getting CPU utilization with default and custom parameters.<br>Alias=cpu.util:system.cpu.util<br>Alias=cpu.util\[\*\]:system.cpu.util\[\*\]<br>This allows use **cpu.util** key to get CPU utilization percentage with default parameters as well as use **cpu.util\[all, idle, avg15\]** to get specific data about CPU utilization.<br><br>3. Running multiple [low-level discovery](/manual/discovery/low_level_discovery) rules processing the same discovery items.<br>Alias=vfs.fs.discovery\[\*\]:vfs.fs.discovery<br>Now it is possible to set up several discovery rules using **vfs.fs.discovery** with different parameters for each rule, e.g., **vfs.fs.discovery\[foo\]**, **vfs.fs.discovery\[bar\]**, etc.| |AllowKey|<|no| | |Allow execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "\*" character to match any number of any characters.<br>Multiple key matching rules may be defined in combination with DenyKey. The parameters are processed one by one according to their appearance order.<br>This parameter is supported since Zabbix 5.0.0.<br>See also: [Restricting agent checks](/manual/config/items/restrict_checks).| |BufferSend|<|no|1-3600|5|The time interval in seconds which determines how often values are sent from the buffer to Zabbix server.<br>Note, that if the buffer is full, the data will be sent sooner.| |BufferSize|<|no|2-65535|100|Maximum number of values in a memory buffer. The agent will send all collected data to Zabbix server or proxy if the buffer is full.<br>This parameter should only be used if persistent buffer is disabled (*EnablePersistentBuffer=0*).| |ControlSocket| |no| |/tmp/agent.sock|The control socket, used to send runtime commands with '-R' option.| |DebugLevel|<|no|0-5|3|Specifies debug level:<br>0 - basic information about starting and stopping of Zabbix processes<br>1 - critical information<br>2 - error information<br>3 - warnings<br>4 - for debugging (produces lots of information)<br>5 - extended debugging (produces even more information)| |DenyKey|<|no| | |Deny execution of those item keys that match a pattern. Key pattern is a wildcard expression that supports "\*" character to match any number of any characters.<br>Multiple key matching rules may be defined in combination with AllowKey. The parameters are processed one by one according to their appearance order.<br>This parameter is supported since Zabbix 5.0.0.<br>See also: [Restricting agent checks](/manual/config/items/restrict_checks).| |EnablePersistentBuffer|<|no|0-1|0|Enable usage of local persistent storage for active items.<br>0 - disabled<br>1 - enabled<br>If persistent storage is disabled, the memory buffer will be used.| |ForceActiveChecksOnStart|<|no|0-1|0 |Perform active checks immediately after restart for the first received configuration.<br>0 - disabled<br>1 - enabled<br>Also available as per plugin configuration parameter, for example: `Plugins.Uptime.System.ForceActiveChecksOnStart=1` <br> Supported since Zabbix 6.0.2. | |HostInterface| |no|0-255 characters| |Optional parameter that defines host interface.<br>Host interface is used at host autoregistration process.<br>An agent will issue an error and not start if the value is over the limit of 255 characters.<br>If not defined, value will be acquired from HostInterfaceItem.<br>Supported since Zabbix 4.4.0.| |HostInterfaceItem|<|no| | |Optional parameter that defines an item used for getting host interface.<br>Host interface is used at host autoregistration process.<br>During an autoregistration request an agent will log a warning message if the value returned by specified item is over limit of 255 characters.<br>This option is only used when HostInterface is not defined.<br>Supported since Zabbix 4.4.0.| |HostMetadata|<|no|0-255 characters| |Optional parameter that defines host metadata. Host metadata is used at host autoregistration process.<br>An agent will issue an error and not start if the specified value is over the limit or a non-UTF-8 string.<br>If not defined, the value will be acquired from HostMetadataItem.| |HostMetadataItem|<|no| | |Optional parameter that defines an item used for getting host metadata. Host metadata item value is retrieved on each autoregistration attempt for host autoregistration process.<br>During an autoregistration request an agent will log a warning message if the value returned by the specified item is over the limit of 255 characters.<br>This option is only used when HostMetadata is not defined.<br>Supports UserParameters and aliases. Supports *system.run\[\]* regardless of AllowKey/DenyKey values.<br>The value returned by the item must be a UTF-8 string otherwise it will be ignored.| |Hostname|<|no| |Set by HostnameItem|List of comma-delimited unique, case-sensitive hostnames.<br>Required for active checks and must match hostnames as configured on the server. Value is acquired from HostnameItem if undefined.<br>Allowed characters: alphanumeric, '.', ' ', '\_' and '-'.<br>Maximum length: 128 characters per hostname, 2048 characters for the entire line.| |HostnameItem|<|no| |system.hostname|Item used for generating Hostname if it is not defined. Ignored if Hostname is defined.<br>Does not support UserParameters or aliases, but does support *system.run\[\]* regardless of AllowKey/DenyKey values.<br>The output length is limited to 512KB.| |Include| |no| | |You may include individual files or all files in a directory in the configuration file.<br>During the installation Zabbix will create the include directory in /usr/local/etc, unless modified during the compile time.<br>To only include relevant files in the specified directory, the asterisk wildcard character is supported for pattern matching. For example: `/absolute/path/to/config/files/*.conf`.<br>Since Zabbix 6.0.0 a path can be relative to *zabbix\_agent2.conf* file location.<br>See [special notes](special_notes_include) about limitations.| |ListenIP|<|no| |0.0.0.0|List of comma-delimited IP addresses that the agent should listen on.<br>The first IP address is sent to Zabbix server, if connecting to it, to retrieve the list of active checks.| |ListenPort|<|no|1024-32767|10050|Agent will listen on this port for connections from the server.| |LogFile|<|yes, if LogType is set to *file*, otherwise<br>no| |/tmp/zabbix\_agent2.log|Log file name if LogType is 'file'.| |LogFileSize|<|no|0-1024|1|Maximum size of log file in MB.<br>0 - disable automatic log rotation.<br>*Note*: If the log file size limit is reached and file rotation fails, for whatever reason, the existing log file is truncated and started anew.| |LogType|<|no| |file|Specifies where log messages are written to:<br>*system* - syslog,<br>*file* - file specified by LogFile parameter,<br>*console* - standard output.| |PersistentBufferFile|<|no| | |The file, where Zabbix Agent2 should keep SQLite database.<br>Must be a full filename.<br>This parameter is only used if persistent buffer is enabled (*EnablePersistentBuffer=1*).| |PersistentBufferPeriod| |no|1m-365d|1h|The time period for which data should be stored, when there is no connection to the server or proxy. Older data will be lost. Log data will be preserved.<br>This parameter is only used if persistent buffer is enabled (*EnablePersistentBuffer=1*).| |PidFile|<|no| |/tmp/zabbix\_agent2.pid|Name of PID file.| |Plugin|<|no| | |Since Zabbix 6.0.0 most of the plugins have their own [configuration files](/manual/appendix/config/zabbix_agent2_plugins). The agent configuration file contains plugin parameters listed below.| | |Plugins.Log.MaxLinesPerSecond|no|1-1000|20|Maximum number of new lines the agent will send per second to Zabbix server or proxy when processing 'log' and 'eventlog' active checks.<br>The provided value will be overridden by the parameter 'maxlines',<br>provided in 'log' or 'eventlog' item key.<br>*Note*: Zabbix will process 10 times more new lines than set in *MaxLinesPerSecond* to seek the required string in log items.<br>This parameter is supported since 4.4.2 and replaces MaxLinesPerSecond.| |^|Plugins.SystemRun.LogRemoteCommands|no| |0|Enable logging of executed shell commands as warnings.<br>0 - disabled<br>1 - enabled<br>Commands will be logged only if executed remotely. Log entries will not be created if system.run\[\] is launched locally by HostMetadataItem, HostInterfaceItem or HostnameItem parameters.<br>This parameter is supported since 4.4.2 and replaces LogRemoteCommands.| |PluginSocket|<|no| |/tmp/agent.plugin.sock |Path to Unix socket for loadable plugin communications.| |PluginTimeout|<|no|1-30 |Global timeout |Timeout for connections with loadable plugins.| |RefreshActiveChecks|<|no|60-3600|120|How often the list of active checks is refreshed, in seconds.<br>Note that after failing to refresh active checks the next refresh will be attempted after 60 seconds.| |Server|<|yes| | |List of comma-delimited IP addresses, optionally in CIDR notation, or DNS names of Zabbix servers and Zabbix proxies.<br>Incoming connections will be accepted only from the hosts listed here.<br>If IPv6 support is enabled then '127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address.<br>'0.0.0.0/0' can be used to allow any IPv4 address.<br>Example: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com<br>Spaces are allowed.| |ServerActive|<|no| | |Zabbix server/proxy address or cluster configuration to get active checks from.<br>Server/proxy address is IP address or DNS name and optional port separated by colon.<br>Cluster configuration is one or more server addresses separated by semicolon.<br>Multiple Zabbix servers/clusters and Zabbix proxies can be specified, separated by comma.<br>More than one Zabbix proxy should not be specified from each Zabbix server/cluster.<br>If Zabbix proxy is specified then Zabbix server/cluster for that proxy should not be specified.<br>Multiple comma-delimited addresses can be provided to use several independent Zabbix servers in parallel. Spaces are allowed.<br>If port is not specified, default port is used.<br>IPv6 addresses must be enclosed in square brackets if port for that host is specified.<br>If port is not specified, square brackets for IPv6 addresses are optional.<br>If this parameter is not specified, active checks are disabled.<br>Example for Zabbix proxy:<br>ServerActive=127.0.0.1:10051<br>Example for multiple servers:<br>ServerActive=127.0.0.1:20051,zabbix.domain,\[::1\]:30051,::1,\[12fc::1\]<br>Example for high availability:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051;zabbix.cluster.node3<br>Example for high availability with two clusters and one server:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051,zabbix.cluster2.node1;zabbix.cluster2.node2,zabbix.domain| |SourceIP|<|no| | |Source IP address for:<br>- outgoing connections to Zabbix server or Zabbix proxy;<br>- making connections while executing some items (web.page.get, net.tcp.port, etc.)| |StatusPort|<|no|1024-32767| |If set, agent will listen on this port for HTTP status requests (http://localhost:<port>/status).| |Timeout|<|no|1-30|3|Spend no more than Timeout seconds on processing.| |TLSAccept|<|yes, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no| | |What incoming connections to accept. Used for a passive checks. Multiple values can be specified, separated by comma:<br>*unencrypted* - accept connections without encryption (default)<br>*psk* - accept connections with TLS and a pre-shared key (PSK)<br>*cert* - accept connections with TLS and a certificate| |TLSCAFile|<|no| | |Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components.| |TLSCertFile|<|no| | |Full pathname of a file containing the agent certificate or certificate chain, used for encrypted communications with Zabbix components.| |TLSConnect|<|yes, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no| | |How the agent should connect to Zabbix server or proxy. Used for active checks. Only one value can be specified:<br>*unencrypted* - connect without encryption (default)<br>*psk* - connect using TLS and a pre-shared key (PSK)<br>*cert* - connect using TLS and a certificate| |TLSCRLFile|<|no| | |Full pathname of a file containing revoked certificates. This parameter is used for encrypted communications with Zabbix components.| |TLSKeyFile|<|no| | |Full pathname of a file containing the agent private key used for encrypted communications with Zabbix components.| |TLSPSKFile|<|no| | |Full pathname of a file containing the agent pre-shared key used for encrypted communications with Zabbix components.| |TLSPSKIdentity|<|no| | |Pre-shared key identity string, used for encrypted communications with Zabbix server.| |TLSServerCertIssuer|<|no| | |Allowed server (proxy) certificate issuer.| |TLSServerCertSubject|<|no| | |Allowed server (proxy) certificate subject.| |UnsafeUserParameters|<|no|0,1|0|Allow all characters to be passed in arguments to user-defined parameters.<br>The following characters are not allowed:<br>\\ ' " \` \* ? \[ \] { } \~ $ ! & ; ( ) < > \| \# @<br>Additionally, newline characters are not allowed.| |UserParameter|<|no| | |User-defined parameter to monitor. There can be several user-defined parameters.<br>Format: UserParameter=<key>,<shell command><br>Note that shell command must not return empty string or EOL only.<br>Shell commands may have relative paths, if UserParameterDir parameter is specified.<br>Examples:<br>UserParameter=system.test,who\|wc -l<br>UserParameter=check\_cpu,./custom\_script.sh| |UserParameterDir|<|no| | |Default search path for UserParameter commands. If used, the agent will change its working directory to the one specified here before executing a command. Thereby, UserParameter commands can have a relative `./` prefix instead of a full path.<br>Only one entry is allowed.<br>Example: UserParameterDir=/opt/myscripts|
ja	#### パラメータ  |パラメータ|<|必須|範囲|デフォルト|説明| |-|----------|----------|----------|----------|--------------------------------------------------| |Alias|<|no| | |項目キーのエイリアスを設定します。長くて複雑な項目キーを、より短くて単純なものに置き換えるために使用できます。<br>複数の *Alias* パラメータが存在する場合があります。同じ *Alias* キーを持つ複数のパラメーターを使用できます。<br>異なる *Alias* キーが同じ項目キーを参照する場合があります。<br>*HostMetadataItem* ではエイリアスを使用できますが、*HostnameItem* パラメーターでは使用できません。<br>< br>例:<br><br>1.ユーザー`zabbix`の ID を取得します。<br>Alias=zabbix.userid:vfs.file.regexp\[/etc/passwd,"\^zabbix:.:(\[0-9\]+)",, ,,\\1\]<br>これで短縮キー **zabbix.userid** を使用してデータを取得できます。<br><br>2.デフォルトおよびカスタム パラメータで CPU 使用率を取得します。<br>Alias=cpu.util:system.cpu.util<br>Alias=cpu.util\[\*\]:system.cpu.util\[\*\]< br>これにより、**cpu.util** キーを使用してデフォルト パラメータで CPU 使用率を取得したり、**cpu.util\[all, idle, avg15\]** を使用して CPU 使用率に関する特定のデータを取得したりできます。< br><br>3.同じディスカバリー アイテムを処理する複数の [ローレベルディスカバリ](/manual/discovery/low_level_discovery) ルールを実行します。<br>Alias=vfs.fs.discovery\[\*\]:vfs.fs.discovery<br> **vfs.fs.discovery** を使用して、ルールごとに異なるパラメーターを使用して複数のディスカバリルールを設定できます (例: **vfs.fs.discovery\[foo\]**、**vfs.fs.discovery\)。 [bar\]** など| |AllowKey|<|no| | |パターンに一致する項目キーの実行を許可します。 キー パターンは、任意の数の任意の文字に一致する"\*"文字をサポートするワイルドカード式です。<br>DenyKey と組み合わせて、複数のキー マッチング ルールを定義できます。 パラメーターは、出現順序に従って 1 つずつ処理されます。<br>このパラメータは、Zabbix 5.0.0 以降でサポートされています。<br>参照: [エージェント チェックの制限](/manual/config/items/restrict_checks)| |BufferSend|<|no|1-3600|5|値がバッファからZabbixサーバーに送信される時間間隔(秒単位)。<br>バッファがいっぱいの場合、データはより早く送信されることに注意してください。| |BufferSize|<|no|2-65535|100|メモリ バッファ内の値の最大数。 エージェントは、バッファがいっぱいになると、収集されたすべてのデータを Zabbix サーバーまたはプロキシに送信します。<br>このパラメータは、永続バッファが無効になっている場合 (*EnablePersistentBuffer=0*) にのみ使用してください。| |ControlSocket| |no| |/tmp/agent.sock|'-R'オプションを使用して実行時コマンドを送信するために使用される制御ソケット。| |DebugLevel|<|no|0-5|3|デバッグ レベルを指定します。<br>0 - Zabbix プロセスの開始と停止に関する基本情報<br>1 - 重要な情報<br>2 - エラー情報<br>3 - 警告<br>4 - デバッグ用 (多くの情報を生成) )<br>5 - 拡張デバッグ (さらに多くの情報を生成)| |DenyKey|<|no| | |パターンに一致する項目キーの実行を拒否します。 キー パターンは、任意の数の任意の文字に一致する"\*"文字をサポートするワイルドカード式です。<br>AllowKey と組み合わせて、複数のキー一致ルールを定義できます。 パラメータは出現順に従って1つずつ処理されます。<br>このパラメータはZabbix 5.0.0からサポートされています。<br>参照: [エージェントチェックの制限](/manual/config/items/restrict_checks).| |EnablePersistentBuffer|<|no|0-1|0|アクティブなアイテムのローカル永続ストレージの使用を有効にします。<br>0 - 無効<br>1 - 有効<br>永続ストレージが無効の場合、メモリ バッファが使用されます。| |ForceActiveChecksOnStart|<|no|0-1|0 |最初に受信した構成の再起動直後にアクティブ チェックを実行します。<br>0 - 無効<br>1 - 有効<br>プラグイン構成パラメーターごとにも利用可能です。例: `Plugins.Uptime.System.ForceActiveChecksOnStart=1` < br> Zabbix 6.0.2 以降でサポートされています。| |HostInterface| |no|0～255文字| |ホスト インターフェースを定義するオプション パラメータ。<br>ホスト インターフェースは、ホストの自動登録プロセスで使用されます。<br>値が 255 文字の制限を超えると、エージェントはエラーを発行し、起動しません。<br>定義されていない場合、値 HostInterfaceItem から取得されます。<br>Zabbix 4.4.0 以降でサポートされています。| |HostInterfaceItem|<|no| | |ホスト インターフェースの取得に使用されるアイテムを定義するオプション パラメータ。<br>ホスト インターフェースは、ホストの自動登録プロセスで使用されます。<br>自動登録リクエスト中に、指定されたアイテムによって返される値が 255 の制限を超えている場合、エージェントは警告メッセージを記録します。 <br>このオプションは、HostInterface が定義されていない場合にのみ使用されます。<br>Zabbix 4.4.0 以降でサポートされています。| |HostMetadata|<|no|0～255文字| |ホストのメタデータを定義するオプションのパラメーター。 ホスト メタデータは、ホストの自動登録プロセスで使用されます。<br>指定された値が制限を超えているか、UTF-8 以外の文字列である場合、エージェントはエラーを発行し、起動しません。<br>未定義の場合、値は HostMetadataItem から取得されます。| |HostMetadataItem|<|no| | |ホスト メタデータの取得に使用される項目を定義するオプションのパラメーター。 ホスト メタデータ アイテム値は、ホスト自動登録プロセスの各自動登録試行で取得されます。<br>自動登録リクエスト中に、指定されたアイテムによって返される値が 255 文字の制限を超えている場合、エージェントは警告メッセージをログに記録します。<br>このオプション HostMetadata が定義されていない場合にのみ使用されます。<br>UserParameters とエイリアスをサポートします。 AllowKey/DenyKey の値に関係なく、*system.run\[\]* をサポートします。<br>アイテムによって返される値は、UTF-8 文字列でなければなりません。それ以外の場合は無視されます。| |Hostname|<|no| |HostnameItem で設定|コンマで区切られた一意のホスト名のリスト。大文字と小文字が区別されます。<br>アクティブ チェックに必要であり、サーバーで構成されているホスト名と一致する必要があります。 未定義の場合、値は HostnameItem から取得されます。<br>使用できる文字: 英数字、'.'、' '、'\_'、および'-'。<br>最大長: ホスト名ごとに 128 文字、行全体で 2048 文字。| |HostnameItem|<|no| |system.hostname|ホスト名が定義されていない場合に生成するために使用されるアイテム。 Hostname が定義されている場合は無視されます。<br>UserParameters またはエイリアスはサポートされませんが、AllowKey/DenyKey の値に関係なく、*system.run\[\]* はサポートされます。<br>出力の長さは 512 KB に制限されています。| |Include| |no| | |個々のファイルまたはディレクトリ内のすべてのファイルを構成ファイルに含めることができます。<br>コンパイル時に変更されない限り、Zabbix はインストール中に /usr/local/etc にインクルード ディレクトリを作成します。<br>関連するもののみを含めるには 指定したディレクトリ内のファイルの場合、パターン マッチングでアスタリスク ワイルドカード文字がサポートされます。例: `/absolute/path/to/config/files/*.conf`<br>Zabbix 6.0.0以降、パスは*zabbix\_agent2.conf*ファイルの場所からの相対パスにすることができます。<br>制限事項については[特記事項](special_notes_include)を参照してください。| |ListenIP|<|no| |0.0.0.0|エージェントがリッスンするカンマ区切りの IP アドレスのリスト。<br>Zabbix サーバーに接続している場合、アクティブなチェックのリストを取得するために、最初の IP アドレスが Zabbix サーバーに送信されます。| |ListenPort|<|no|1024-32767|10050|エージェントは、この番号のポートでサーバーからの接続をリッスンします。| |LogFile|<|LogType が *file* に設定されている場合:yes<br>それ以外の場合:no| |/tmp/zabbix\_agent2.log|LogType が'file'の場合のログ ファイル名。| |LogFileSize|<|no|0-1024|1|ログ ファイルの最大サイズ (MB)。<br>0 - ログの自動ローテーションを無効にします。<br>*注*: ログ ファイルのサイズ制限に達し、ファイルのローテーションが何らかの理由で失敗した場合、既存のログ ファイルは切り捨てられ、新たに作成されます。| |LogType|<|no| |file|ログ メッセージが書き込まれる場所を指定します。<br>*system* - syslog<br>*file* - LogFile パラメータで指定されたファイル<br>*console* - 標準出力| |PersistentBufferFile|<|no| | |Zabbix Agent2 が SQLite データベースを保持するファイル。<br>完全なファイル名である必要があります。<br>このパラメータは、永続バッファが有効な場合 (*EnablePersistentBuffer=1*) にのみ使用されます。| |PersistentBufferPeriod| |no|1m-365d|1h|サーバーまたはプロキシへの接続がない場合に、データを保存する期間。 古いデータは失われます。 ログ データは保持されます。<br>このパラメータは、永続バッファが有効な場合にのみ使用されます (*EnablePersistentBuffer=1*)| |PidFile|<|no| |/tmp/zabbix\_agent2.pid|PIDファイル名| |Plugin|<|no| | |Zabbix 6.0.0以降、ほとんどのプラグインには独自の[設定ファイル](/manual/appendix/config/zabbix_agent2_plugins)があります。 エージェント設定ファイルには、以下に示すプラグイン パラメータが含まれています。| | |Plugins.Log.MaxLinesPerSecond|no|1-1000|20|'ログ'および'イベントログ'のアクティブ チェックを処理するときに、エージェントが Zabbix サーバーまたはプロキシに 1 秒あたりに送信する新しい行の最大数。<br>指定された値は、パラメータ'maxlines'によって上書きされます。<br>'log' または 'eventlog' アイテム キーで提供されます。<br>*注*: Zabbix は、*MaxLinesPerSecond* で設定されたよりも 10 倍多くの新しい行を処理して、ログ項目で必要な文字列を検索します。<br>このパラメータは 4.4.2 以降でサポートされており、MaxLinesPerSecond を置き換えます。| |^|Plugins.SystemRun.LogRemoteCommands|no| |0|実行されたシェル コマンドのログを警告として有効にします。<br>0 - 無効<br>1 - 有効<br>コマンドは、リモートで実行された場合にのみログに記録されます。 system.run\[\] が HostMetadataItem、HostInterfaceItem、または HostnameItem パラメータによってローカルで起動された場合、ログ エントリは作成されません。<br>このパラメータは 4.4.2 以降でサポートされ、LogRemoteCommands を置き換えます。| |PluginSocket|<|no| |/tmp/agent.plugin.sock |ロード可能なプラグイン通信用の Unix ソケットパス| |PluginTimeout|<|no|1-30 |グローバル タイムアウト|ロード可能なプラグインとの接続のタイムアウト。| |RefreshActiveChecks|<|no|60-3600|120|アクティブ チェックのリストを更新する頻度 (秒単位)。<br>アクティブ チェックの更新に失敗すると、60 秒後に次の更新が試行されることに注意してください。| |Server|<|yes| | |カンマ区切りの IP アドレスのリスト (オプションで CIDR 表記、または Zabbix サーバーと Zabbix プロキシの DNS 名)。<br>着信接続は、ここにリストされているホストからのみ受け入れられます。<br>IPv6 サポートが有効になっている場合は、'127.0. 0.1'、'::ffff:127.0.0.1' は同等に扱われ、'::/0' はすべての IPv4 または IPv6 アドレスを許可します。<br>'0.0.0.0/0' はすべての IPv4 アドレスを許可するために使用できます。< br>例: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com<br>スペースを使用できます。| |ServerActive|<|no| | |アクティブなチェックを取得するZabbixサーバー/プロキシアドレスまたはクラスター構成。<br>サーバー/プロキシ アドレスは、コロンで区切られた IP アドレスまたは DNS 名とオプションのポートです。<br>クラスタ構成は、セミコロンで区切られた 1 つ以上のサーバー アドレスです。<br>複数のZabbixサーバー/クラスタおよびZabbixプロキシをカンマで区切って指定できます。<br>各 Zabbix サーバー/クラスタから複数の Zabbix プロキシを指定しないでください。<br>Zabbix プロキシが指定されている場合、そのプロキシの Zabbix サーバー/クラスタは指定しないでください。<br>カンマ区切りの複数のアドレスを指定して、複数の独立した Zabbix サーバーを並行して使用できます。スペースは使用できます。<br>ポートが指定されていない場合、デフォルトのポートが使用されます。<br>そのホストのポートを指定する場合は、IPv6 アドレスを角括弧で囲む必要があります。<br>ポートが指定されていない場合、IPv6 アドレスの角括弧はオプションです。<br>このパラメータが指定されていない場合、アクティブ チェックは無効になります。<br>Zabbix プロキシの例:<br>ServerActive=127.0.0.1:10051<br>複数のサーバーの例:<br>ServerActive=127.0.0.1:20051,zabbix.domain,\[::1\]:30051,::1,\[12fc::1\]<br>高可用性の例:<br>ServerActive= zabbix.cluster.node1;zabbix.cluster.node2:20051;zabbix.cluster.node3<br>2 つのクラスタと 1 つのサーバーによる高可用性の例:<br>ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051,zabbix.cluster2.node1;zabbix.cluster2.node2,zabbix.domain| |SourceIP|<|no| | |次の送信元 IP アドレス:<br>- Zabbix サーバーまたは Zabbix プロキシへの発信接続。<br>- 一部のアイテム (web.page.get、net.tcp.port など) の実行中に接続を確立する| |StatusPort|<|no|1024-32767| |設定されている場合、エージェントはこのポートで HTTP ステータス リクエストをリッスンします (http://localhost:<port>/status)| |Timeout|<|no|1-30|3|処理にかかる時間は Timeout 秒以内です。| |TLSAccept|<|TLS 証明書または PSK パラメータが定義されている場合 (*暗号化されていない* 接続の場合でも):yes、それ以外の場合:no| | |受け入れる着信接続。 パッシブ チェックに使用されます。 コンマで区切って複数の値を指定できます。<br>*unencrypted* - 暗号化なしで接続を受け入れる (デフォルト)<br>*psk* - TLS と事前共有キー (PSK) を使用した接続を受け入れる<br>*cert* - TLS と証明書による接続を受け入れる| |TLSCAFile|<|no| | |Zabbix コンポーネント間の暗号化された通信に使用される、ピア証明書検証用の最上位 CA 証明書を含むファイルのフル パス名。| |TLSCertFile|<|no| | |Zabbix コンポーネントとの暗号化通信に使用される、エージェント証明書または証明書チェーンを含むファイルのフル パス名。| |TLSConnect|<|TLS 証明書または PSK パラメータが定義されている場合 (*暗号化されていない* 接続の場合でも):yes、それ以外の場合:no| | |エージェントが Zabbix サーバーまたはプロキシに接続する方法。 アクティブ チェックに使用されます。 指定できる値は 1 つだけです。<br>*unencrypted* - 暗号化なしで接続 (デフォルト)<br>*psk* - TLS と事前共有キー (PSK) を使用して接続<br>*cert* - TLS と 証明書| |TLSCRLFile|<|no| | |失効した証明書を含むファイルのフル パス名。 このパラメータは、Zabbix コンポーネントとの暗号化通信に使用されます。| |TLSKeyFile|<|no| | |Zabbix コンポーネントとの暗号化された通信に使用されるエージェントの秘密鍵を含むファイルのフル パス名。| |TLSPSKFile|<|no| | |Zabbix コンポーネントとの暗号化された通信に使用されるエージェントの事前共有キーを含むファイルのフル パス名。| |TLSPSKIdentity|<|no| | |Zabbix サーバーとの暗号化された通信に使用される事前共有キー ID 文字列。| |TLSServerCertIssuer|<|no| | |許可されたサーバー (プロキシ) 証明書の発行者。| |TLSServerCertSubject|<|no| | |許可されたサーバー (プロキシ) 証明書のサブジェクト。| |UnsafeUserParameters|<|no|0,1|0|ユーザー定義パラメータの引数にすべての文字を渡すことができます。<br>ただし次の文字は使用できません:<br>\\ ' " \` \* ? \[ \] { } \~ $ ! & ; ( ) < > \| \# @<br>さらに、改行文字は使用できません。| |UserParameter|<|no| | |監視するユーザー定義のパラメーター。 いくつかのユーザー定義パラメーターが存在する場合があります。<br>書式: UserParameter=<キー>,<シェルコマンド><br>シェル コマンドは、空の文字列または EOL のみを返してはならないことに注意してください。<br>UserParameterDir パラメータが指定されている場合、シェル コマンドは相対パスを持つことができます。<br>例:<br>UserParameter=system.test,who\|wc -l<br>UserParameter=check\_cpu,./custom\_script.sh| |UserParameterDir|<|no| | |UserParameter コマンドのデフォルトの検索パス。 使用すると、エージェントはコマンドを実行する前に、ここで指定されたディレクトリに作業ディレクトリを変更します。 これにより、UserParameter コマンドは、フル パスの代わりに相対 `./` プレフィックスを持つことができます。<br>許可されるエントリは 1 つだけです。<br>例: UserParameterDir=/opt/myscripts|

en-us	#### Parameters  |Parameter|Mandatory|Range|Default|Description| |--|--|--|--|----------| |AllowedIP|yes| | |List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of Zabbix servers and Zabbix proxies.<br>Incoming connections will be accepted only from the hosts listed here.<br>If IPv6 support is enabled then `127.0.0.1`, `::127.0.0.1`, `::ffff:127.0.0.1` are treated equally and `::/0` will allow any IPv4 or IPv6 address.<br>`0.0.0.0/0` can be used to allow any IPv4 address.<br>Example: `127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com`| |DebugLevel|no|0-5|3|Specifies debug level:<br>0 - basic information about starting and stopping of Zabbix processes<br>1 - critical information<br>2 - error information<br>3 - warnings<br>4 - for debugging (produces lots of information)<br>5 - extended debugging (produces even more information)| |ListenPort|no|1024-32767|10053|The port service listens on for connections from the server.| |LogFile|yes, if LogType is set to *file*, otherwise no| | |Log file name for LogType 'file' parameter.<br>Example: `/tmp/zabbix_web_service.log`| |LogFileSize|no|0-1024|1|Maximum size of log file in MB.<br>0 - disable automatic log rotation.| |LogType|no|system / file / console|file|Specifies where log messages are written to:<br>*system* - syslog<br>*file* - file specified with LogFile parameter<br>*console* - standard output| |Timeout|no|1-30|3|Spend no more than Timeout seconds on processing.| |TLSAccept|no|unencrypted / cert|unencrypted|Specifies what type of connection to use:<br>*unencrypted* - accept connections without encryption (default)<br>*cert* - accept connections with TLS and a certificate| |TLSCAFile|no| | |Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components.| |TLSCertFile|no| | |Full pathname of a file containing the service certificate or certificate chain, used for encrypted communications with Zabbix components.| |TLSKeyFile|no| | |Full pathname of a file containing the service private key used for encrypted communications with Zabbix components.|
ja	#### パラメーター  |パラメーター|必須|範囲|デフォルト|説明| |---------|---------|-----|-------|-----------| |AllowedIP|yes|<|<|カンマ区切りのIPアドレスのリスト（オプションでCIDR表記、またはZabbixサーバーとZabbixプロキシのDNS名）<br>着信接続は、ここにリストされているホストからのみ受け入れられます。<br> IPv6サポートが有効になっている場合、`127.0.0.1`, `::127.0.0.1`, `::ffff:127.0.0.1`は同等に扱われ、`::/0`は任意のIPv4またはIPv6アドレスを許可します。<br>`0.0.0.0/0`表記を使用して任意のIPv4アドレスを許可できます。<br>例： `127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com`| |DebugLevel|no|0-5|3|デバッグレベルを指定します<br>0 - Zabbixプロセスの開始と停止に関する基本情報<br>1 - 重要な情報<br>2 - エラー情報<br>3 - 警告<br>4 - デバッグ用（多くの情報を生成します ）<br>5 - 拡張デバッグ（さらに多くの情報を生成します）| |ListenPort|no|1024-32767|10053|接続待機ポート番号| |LogFile|LogTypeが*file*に設定されている場合はyes。それ以外の場合はno。|<|<|LogType'file'パラメータのログファイル名。<br>例:`/tmp/zabbix_web_service.log`| |LogFileSize|no|0-1024|1|ログファイルの最大サイズ（MB単位）<br>0 - 自動ログローテーションを無効にします。| |LogType|no|system / file / console|file|ログメッセージの書き込み先を指定します<br>*system* - syslog<br>*file* - LogFileパラメーターで指定されたファイル<br>*console* - 標準出力| |Timeout|no|1-30|3|タイムアウトするまでの処理士官。秒指定| |TLSAccept|no|unencrypted / cert|unencrypted|使用する接続のタイプを指定します。<br>*unencrypted* - 暗号化せずに接続を受け入れる（デフォルト）<br>*cert* - TLSと証明書を使用した接続を受け入れる| |TLSCAFile|no|<|<|Zabbixコンポーネント間の暗号化された通信に使用される、ピア証明書検証用の最上位CA証明書を含むファイルのフルパス名。| |TLSCertFile|no|<|<|Zabbixコンポーネントとの暗号化された通信に使用される、サービス証明書または証明書チェーンを含むファイルのフルパス名。| |TLSKeyFile|no|<|<|Zabbixコンポーネントとの暗号化された通信に使用されるサービス秘密鍵を含むファイルのフルパス名。|

en-us	#### Parameters  |Parameter|Mandatory|Range|Default|Description| |---------|---------|-----|-------|-----------| |AllowRoot|no| |0|Allow the proxy to run as 'root'. If disabled and the proxy is started by 'root', the proxy will try to switch to the 'zabbix' user instead. Has no effect if started under a regular user.<br>0 - do not allow<br>1 - allow| |AllowUnsupportedDBVersions|no| |0|Allow the proxy to work with unsupported database versions.<br>0 - do not allow<br>1 - allow| |CacheSize|no|128K-64G|8M|Size of configuration cache, in bytes.<br>Shared memory size, for storing host and item data.| |ConfigFrequency|no|1-604800|3600|How often proxy retrieves configuration data from Zabbix server in seconds.<br>Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter).| |DataSenderFrequency|no|1-3600|1|Proxy will send collected data to the server every N seconds. Note that active proxy will still poll Zabbix server every second for remote command tasks.<br>Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter).| |DBHost|no| |localhost|Database host name.<br>In case of MySQL localhost or empty string results in using a socket. In case of PostgreSQL<br>only empty string results in attempt to use socket.<br>In case of Oracle empty string results in using the Net Service Name connection method; in this case consider using the TNS\_ADMIN environment variable to specify the directory of the tnsnames.ora file.| |DBName|yes| | |Database name or path to database file for SQLite3 (multi-process architecture of Zabbix does not allow to use [in-memory database](https://www.sqlite.org/inmemorydb.html), e.g. `:memory:`, `file::memory:?cache=shared` or `file:memdb1?mode=memory&cache=shared`).<br><br>Warning: Do not attempt to use the same database Zabbix server is using.<br>In case of Oracle, if the Net Service Name connection method is used, specify the service name from tnsnames.ora or set to empty string; set the TWO\_TASK environment variable if DBName is set to empty string.| |DBPassword|no| | |Database password. Ignored for SQLite.<br>Comment this line if no password is used.| |DBSchema|no| | |Schema name. Used for PostgreSQL.| |DBSocket|no| |3306|Path to MySQL socket.<br>Database port when not using local socket. Ignored for SQLite.| |DBUser| | | |Database user. Ignored for SQLite.| |DBTLSConnect|no| | |Setting this option enforces to use TLS connection to database:<br>*required* - connect using TLS<br>*verify\_ca* - connect using TLS and verify certificate<br>*verify\_full* - connect using TLS, verify certificate and verify that database identity specified by DBHost matches its certificate<br><br>On MySQL starting from 5.7.11 and PostgreSQL the following values are supported: "required", "verify", "verify\_full". On MariaDB starting from version 10.2.6 "required" and "verify\_full" values are supported.<br>By default not set to any option and the behavior depends on database configuration.<br><br>This parameter is supported since Zabbix 5.0.0.| |DBTLSCAFile|no<br>(yes, if DBTLSConnect set to one of: verify\_ca, verify\_full)| | |Full pathname of a file containing the top-level CA(s) certificates for database certificate verification.<br>This parameter is supported since Zabbix 5.0.0.| |DBTLSCertFile|no| | |Full pathname of file containing Zabbix server certificate for authenticating to database.<br>This parameter is supported since Zabbix 5.0.0.| |DBTLSKeyFile|no| | |Full pathname of file containing the private key for authenticating to database.<br>This parameter is supported since Zabbix 5.0.0.| |DBTLSCipher|no| | |The list of encryption ciphers that Zabbix server permits for TLS protocols up through TLSv1.2.<br>Supported only for MySQL.<br>This parameter is supported since Zabbix 5.0.0.| |DBTLSCipher13|no| | |The list of encryption ciphersuites that Zabbix server permits for TLSv1.3 protocol.<br>Supported only for MySQL, starting from version 8.0.16.<br>This parameter is supported since Zabbix 5.0.0.| |DebugLevel|no|0-5|3|Specifies debug level:<br>0 - basic information about starting and stopping of Zabbix processes<br>1 - critical information<br>2 - error information<br>3 - warnings<br>4 - for debugging (produces lots of information)<br>5 - extended debugging (produces even more information)| |EnableRemoteCommands|no| |0|Whether remote commands from Zabbix server are allowed.<br>0 - not allowed<br>1 - allowed<br>This parameter is supported since Zabbix 3.4.0.| |ExternalScripts|no| |/usr/local/share/zabbix/externalscripts|Location of external scripts (depends on compile-time installation variable *datadir*).| |Fping6Location|no| |/usr/sbin/fping6|Location of fping6.<br>Make sure that fping6 binary has root ownership and SUID flag set.<br>Make empty ("Fping6Location=") if your fping utility is capable to process IPv6 addresses.| |FpingLocation|no| |/usr/sbin/fping|Location of fping.<br>Make sure that fping binary has root ownership and SUID flag set!| |HeartbeatFrequency|no|0-3600|60|Frequency of heartbeat messages in seconds.<br>Used for monitoring availability of proxy on server side.<br>0 - heartbeat messages disabled.<br>Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter).| |HistoryCacheSize|no|128K-2G|16M|Size of history cache, in bytes.<br>Shared memory size for storing history data.| |HistoryIndexCacheSize|no|128K-2G|4M|Size of history index cache, in bytes.<br>Shared memory size for indexing history data stored in history cache.<br>The index cache size needs roughly 100 bytes to cache one item.<br>This parameter is supported since Zabbix 3.0.0.| |Hostname|no| |Set by HostnameItem|Unique, case sensitive Proxy name. Make sure the proxy name is known to the server!<br>Allowed characters: alphanumeric, '.', ' ', '\_' and '-'.<br>Maximum length: 128| |HostnameItem|no| |system.hostname|Item used for setting Hostname if it is undefined (this will be run on the proxy similarly as on an agent).<br>Does not support UserParameters, performance counters or aliases, but does support system.run\[\].<br><br>Ignored if Hostname is set.| |HousekeepingFrequency|no|0-24|1|How often Zabbix will perform housekeeping procedure (in hours).<br>Housekeeping is removing outdated information from the database.<br>*Note*: To prevent housekeeper from being overloaded (for example, when configuration parameters ProxyLocalBuffer or ProxyOfflineBuffer are greatly reduced), no more than 4 times HousekeepingFrequency hours of outdated information are deleted in one housekeeping cycle. Thus, if HousekeepingFrequency is 1, no more than 4 hours of outdated information (starting from the oldest entry) will be deleted per cycle.<br>*Note*: To lower load on proxy startup housekeeping is postponed for 30 minutes after proxy start. Thus, if HousekeepingFrequency is 1, the very first housekeeping procedure after proxy start will run after 30 minutes, and will repeat every hour thereafter.<br>Since Zabbix 3.0.0 it is possible to disable automatic housekeeping by setting HousekeepingFrequency to 0. In this case the housekeeping procedure can only be started by *housekeeper\_execute* runtime control option and the period of outdated information deleted in one housekeeping cycle is 4 times the period since the last housekeeping cycle, but not less than 4 hours and not greater than 4 days.| |Include|no| | |You may include individual files or all files in a directory in the configuration file.<br>To only include relevant files in the specified directory, the asterisk wildcard character is supported for pattern matching. For example: `/absolute/path/to/config/files/*.conf`.<br>See [special notes](special_notes_include) about limitations.| |JavaGateway|no| | |IP address (or hostname) of Zabbix Java gateway.<br>Only required if Java pollers are started.| |JavaGatewayPort|no|1024-32767|10052|Port that Zabbix Java gateway listens on.| |ListenBacklog|no|0 - INT\_MAX|SOMAXCONN|The maximum number of pending connections in the TCP queue.<br>Default value is a hard-coded constant, which depends on the system.<br>Maximum supported value depends on the system, too high values may be silently truncated to the 'implementation-specified maximum'.| |ListenIP|no| |0.0.0.0|List of comma delimited IP addresses that the trapper should listen on.<br>Trapper will listen on all network interfaces if this parameter is missing.| |ListenPort|no|1024-32767|10051|Listen port for trapper.| |LoadModule|no| | |Module to load at proxy startup. Modules are used to extend functionality of the proxy.<br>Formats:<br>LoadModule=<module.so><br>LoadModule=<path/module.so><br>LoadModule=</abs\_path/module.so><br>Either the module must be located in directory specified by LoadModulePath or the path must precede the module name. If the preceding path is absolute (starts with '/') then LoadModulePath is ignored.<br>It is allowed to include multiple LoadModule parameters.| |LoadModulePath|no| | |Full path to location of proxy modules.<br>Default depends on compilation options.| |LogFile|yes, if LogType is set to *file*, otherwise<br>no| | |Name of log file.| |LogFileSize|no|0-1024|1|Maximum size of log file in MB.<br>0 - disable automatic log rotation.<br>*Note*: If the log file size limit is reached and file rotation fails, for whatever reason, the existing log file is truncated and started anew.| |LogRemoteCommands|no| |0|Enable logging of executed shell commands as warnings.<br>0 - disabled<br>1 - enabled<br>This parameter is supported since Zabbix 3.4.0.| |LogType|no| |file|Log output type:<br>*file* - write log to file specified by LogFile parameter,<br>*system* - write log to syslog,<br>*console* - write log to standard output.<br>This parameter is supported since Zabbix 3.0.0.| |LogSlowQueries|no|0-3600000|0|How long a database query may take before being logged (in milliseconds).<br>0 - don't log slow queries.<br>This option becomes enabled starting with DebugLevel=3.| |PidFile|no| |/tmp/zabbix\_proxy.pid|Name of PID file.| |ProxyLocalBuffer|no|0-720|0|Proxy will keep data locally for N hours, even if the data have already been synced with the server.<br>This parameter may be used if local data will be used by third party applications.| |ProxyMode|no|0-1|0|Proxy operating mode.<br>0 - proxy in the active mode<br>1 - proxy in the passive mode<br>*Note* that (sensitive) proxy configuration data may become available to parties having access to the Zabbix server trapper port when using an active proxy. This is possible because anyone may pretend to be an active proxy and request configuration data; authentication does not take place.| |ProxyOfflineBuffer|no|1-720|1|Proxy will keep data for N hours in case of no connectivity with Zabbix server.<br>Older data will be lost.| |ServerPort|no|1024-32767|10051|Port of Zabbix trapper on Zabbix server.<br>Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter).| |Server|yes| | |If ProxyMode is set to *active mode*:<br>Zabbix server IP address or DNS name (address:port) or [cluster](/manual/concepts/server/ha) (address:port;address2:port) to get configuration data from and send data to.<br>If port is not specified, the default port is used.<br>Cluster nodes must be separated by a semicolon.<br><br>If ProxyMode is set to *passive mode*:<br>List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of Zabbix server. Incoming connections will be accepted only from the addresses listed here. If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally.<br>'::/0' will allow any IPv4 or IPv6 address. '0.0.0.0/0' can be used to allow any IPv4 address.<br>*Example*: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com| |SNMPTrapperFile|no| |/tmp/zabbix\_traps.tmp|Temporary file used for passing data from SNMP trap daemon to the proxy.<br>Must be the same as in zabbix\_trap\_receiver.pl or SNMPTT configuration file.| |SocketDir|no| |/tmp|Directory to store IPC sockets used by internal Zabbix services.<br>This parameter is supported since Zabbix 3.4.0.| |SourceIP|no| | |Source IP address for:<br>- outgoing connections to Zabbix server;<br>- agentless connections (VMware, SSH, JMX, SNMP, Telnet and simple checks);<br>- HTTP agent connections;<br>- script item JavaScript HTTP requests;<br>- preprocessing JavaScript HTTP requests;<br>- connections to the Vault| |SSHKeyLocation|no| | |Location of public and private keys for SSH checks and actions| |SSLCertLocation|no| | |Location of SSL client certificate files for client authentication.<br>This parameter is used in web monitoring only.| |SSLKeyLocation|no| | |Location of SSL private key files for client authentication.<br>This parameter is used in web monitoring only.| |SSLCALocation|no| | |Location of certificate authority (CA) files for SSL server certificate verification.<br>Note that the value of this parameter will be set as libcurl option CURLOPT\_CAPATH. For libcurl versions before 7.42.0, this only has effect if libcurl was compiled to use OpenSSL. For more information see [cURL web page](http://curl.haxx.se/libcurl/c/CURLOPT_CAPATH.html).<br>This parameter is used in web monitoring since Zabbix 2.4.0 and in SMTP authentication since Zabbix 3.0.0.| |StartDBSyncers|no|1-100|4|Number of pre-forked instances of [history syncers](/manual/concepts/proxy#proxy_process_types).<br>*Note*: Be careful when changing this value, increasing it may do more harm than good.| |StartDiscoverers|no|0-250|1|Number of pre-forked instances of [discoverers](/manual/concepts/proxy#proxy_process_types).| |StartHistoryPollers|no|0-1000|1|Number of pre-forked instances of [history pollers](/manual/concepts/proxy#proxy_process_types).<br>This parameter is supported since Zabbix 5.4.0.| |StartHTTPPollers|no|0-1000|1|Number of pre-forked instances of [HTTP pollers](/manual/concepts/proxy#proxy_process_types).| |StartIPMIPollers|no|0-1000|0|Number of pre-forked instances of [IPMI pollers](/manual/concepts/proxy#proxy_process_types).| |StartJavaPollers|no|0-1000|0|Number of pre-forked instances of [Java pollers](/manual/concepts/proxy#proxy_process_types).| |StartODBCPollers|no|0-1000|1|Number of pre-forked instances of [ODBC pollers](/manual/concepts/proxy#proxy_process_types).| |StartPingers|no|0-1000|1|Number of pre-forked instances of [ICMP pingers](/manual/concepts/proxy#proxy_process_types).| |StartPollersUnreachable|no|0-1000|1|Number of pre-forked instances of [pollers for unreachable](/manual/concepts/proxy#proxy_process_types) hosts (including IPMI and Java).<br>At least one poller for unreachable hosts must be running if regular, IPMI or Java pollers are started.| |StartPollers|no|0-1000|5|Number of pre-forked instances of [pollers](/manual/concepts/proxy#proxy_process_types).| |StartPreprocessors|no|1-1000|3|Number of pre-forked instances of preprocessing [workers](/manual/concepts/proxy#proxy_process_types)**^[1](zabbix_server#footnotes)^**.<br>The preprocessing manager process is automatically started when a preprocessor worker is started.<br>This parameter is supported since Zabbix 4.2.0.| |StartSNMPTrapper|no|0-1|0|If set to 1, [SNMP trapper](/manual/concepts/proxy#proxy_process_types) process will be started.| |StartTrappers|no|0-1000|5|Number of pre-forked instances of [trappers](/manual/concepts/proxy#proxy_process_types).<br>Trappers accept incoming connections from Zabbix sender and active agents.| |StartVMwareCollectors|no|0-250|0|Number of pre-forked [VMware collector](/manual/concepts/proxy#proxy_process_types) instances.| |StatsAllowedIP|no| | |List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of external Zabbix instances. Stats request will be accepted only from the addresses listed here. If this parameter is not set no stats requests will be accepted.<br>If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address. '0.0.0.0/0' can be used to allow any IPv4 address.<br>Example: StatsAllowedIP=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com<br>This parameter is supported since Zabbix 4.2.0.| |Timeout|no|1-30|3|Specifies how long we wait for agent, SNMP device or external check (in seconds).| |TLSAccept|yes for passive proxy, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no| | |What incoming connections to accept from Zabbix server. Used for a passive proxy, ignored on an active proxy. Multiple values can be specified, separated by comma:<br>*unencrypted* - accept connections without encryption (default)<br>*psk* - accept connections with TLS and a pre-shared key (PSK)<br>*cert* - accept connections with TLS and a certificate<br>This parameter is supported since Zabbix 3.0.0.| |TLSCAFile|no| | |Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCertFile|no| | |Full pathname of a file containing the proxy certificate or certificate chain, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCipherAll|no| | |GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.<br>Example: TLS\_AES\_256\_GCM\_SHA384:TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherAll13|no| | |Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL::+SIGN-ALL:+CTYPE-X.509<br>Example for OpenSSL: EECDH+aRSA+AES128:RSA+aRSA+AES128:kECDHEPSK+AES128:kPSK+AES128<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherCert|no| | |GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509<br>Example for OpenSSL: EECDH+aRSA+AES128:RSA+aRSA+AES128<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherCert13|no| | |Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate-based encryption.<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherPSK|no| | |GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for PSK-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL<br>Example for OpenSSL: kECDHEPSK+AES128:kPSK+AES128<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherPSK13|no| | |Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for PSK-based encryption.<br>Example: TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>This parameter is supported since Zabbix 4.4.7.| |TLSConnect|yes for active proxy, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no| | |How the proxy should connect to Zabbix server. Used for an active proxy, ignored on a passive proxy. Only one value can be specified:<br>*unencrypted* - connect without encryption (default)<br>*psk* - connect using TLS and a pre-shared key (PSK)<br>*cert* - connect using TLS and a certificate<br>This parameter is supported since Zabbix 3.0.0.| |TLSCRLFile|no| | |Full pathname of a file containing revoked certificates.This parameter is used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSKeyFile|no| | |Full pathname of a file containing the proxy private key, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSPSKFile|no| | |Full pathname of a file containing the proxy pre-shared key. used for encrypted communications with Zabbix server.<br>This parameter is supported since Zabbix 3.0.0.| |TLSPSKIdentity|no| | |Pre-shared key identity string, used for encrypted communications with Zabbix server.<br>This parameter is supported since Zabbix 3.0.0.| |TLSServerCertIssuer|no| | |Allowed server certificate issuer.<br>This parameter is supported since Zabbix 3.0.0.| |TLSServerCertSubject|no| | |Allowed server certificate subject.<br>This parameter is supported since Zabbix 3.0.0.| |TmpDir|no| |/tmp|Temporary directory.| |TrapperTimeout|no|1-300|300|Specifies how many seconds trapper may spend processing new data.| |User|no| |zabbix|Drop privileges to a specific, existing user on the system.<br>Only has effect if run as 'root' and AllowRoot is disabled.| |UnavailableDelay|no|1-3600|60|How often host is checked for availability during the [unavailability](/manual/appendix/items/unreachability#unavailable_host) period, in seconds.| |UnreachableDelay|no|1-3600|15|How often host is checked for availability during the [unreachability](/manual/appendix/items/unreachability#unreachable_host) period, in seconds.| |UnreachablePeriod|no|1-3600|45|After how many seconds of [unreachability](/manual/appendix/items/unreachability#unreachable_host) treat a host as unavailable.| |VaultDBPath|no| | |Vault path from where credentials for database will be retrieved by keys 'password' and 'username'.<br>Example: secret/zabbix/database<br>This option can only be used if DBUser and DBPassword are not specified.<br>This parameter is supported since Zabbix 5.2.0.| |VaultToken|no| | |Vault authentication token that should have been generated exclusively for Zabbix proxy with read-only permission to the path specified in the optional VaultDBPath configuration parameter.<br>It is an error if VaultToken and VAULT\_TOKEN environment variable are defined at the same time.<br>This parameter is supported since Zabbix 5.2.0.| |VaultURL|no| |https://127.0.0.1:8200|Vault server HTTP\[S\] URL. System-wide CA certificates directory will be used if SSLCALocation is not specified.<br>This parameter is supported since Zabbix 5.2.0.| |VMwareCacheSize|no|256K-2G|8M|Shared memory size for storing VMware data.<br>A VMware internal check zabbix\[vmware,buffer,...\] can be used to monitor the VMware cache usage (see [Internal checks](/manual/config/items/itemtypes/internal)).<br>Note that shared memory is not allocated if there are no vmware collector instances configured to start.| |VMwareFrequency|no|10-86400|60|Delay in seconds between data gathering from a single VMware service.<br>This delay should be set to the least update interval of any VMware monitoring item.| |VMwarePerfFrequency|no|10-86400|60|Delay in seconds between performance counter statistics retrieval from a single VMware service.<br>This delay should be set to the least update interval of any VMware monitoring [item](/manual/config/items/itemtypes/simple_checks/vmware_keys#footnotes) that uses VMware performance counters.| |VMwareTimeout|no|1-300|10|The maximum number of seconds vmware collector will wait for a response from VMware service (vCenter or ESX hypervisor).|  
ja	#### Parameters  |Parameter|Mandatory|Range|Default|Description| |---------|---------|-----|-------|-----------| |AllowRoot|no|<|0|Allow the proxy to run as 'root'. If disabled and the proxy is started by 'root', the proxy will try to switch to the 'zabbix' user instead. Has no effect if started under a regular user.<br>0 - do not allow<br>1 - allow| |AllowUnsupportedDBVersions|no|<|0|Allow the proxy to work with unsupported database versions.<br>0 - do not allow<br>1 - allow| |CacheSize|no|128K-64G|8M|Size of configuration cache, in bytes.<br>Shared memory size, for storing host and item data.| |ConfigFrequency|no|1-604800|3600|How often proxy retrieves configuration data from Zabbix server in seconds.<br>Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter).| |DataSenderFrequency|no|1-3600|1|Proxy will send collected data to the server every N seconds. Note that active proxy will still poll Zabbix server every second for remote command tasks.<br>Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter).| |DBHost|no|<|localhost|Database host name.<br>In case of MySQL localhost or empty string results in using a socket. In case of PostgreSQL<br>only empty string results in attempt to use socket.<br>In case of Oracle empty string results in using the Net Service Name connection method; in this case consider using the TNS\_ADMIN environment variable to specify the directory of the tnsnames.ora file.| |DBName|yes|<|<|Database name or path to database file for SQLite3 (multi-process architecture of Zabbix does not allow to use [in-memory database](https://www.sqlite.org/inmemorydb.html), e.g. `:memory:`, `file::memory:?cache=shared` or `file:memdb1?mode=memory&cache=shared`).<br><br>Warning: Do not attempt to use the same database Zabbix server is using.<br>In case of Oracle, if the Net Service Name connection method is used, specify the service name from tnsnames.ora or set to empty string; set the TWO\_TASK environment variable if DBName is set to empty string.| |DBPassword|no|<|<|Database password. Ignored for SQLite.<br>Comment this line if no password is used.| |DBSchema|no|<|<|Schema name. Used for PostgreSQL.| |DBSocket|no|<|3306|Path to MySQL socket.<br>Database port when not using local socket. Ignored for SQLite.| |DBUser|<|<|<|Database user. Ignored for SQLite.| |DBTLSConnect|no|<|<|Setting this option enforces to use TLS connection to database:<br>*required* - connect using TLS<br>*verify\_ca* - connect using TLS and verify certificate<br>*verify\_full* - connect using TLS, verify certificate and verify that database identity specified by DBHost matches its certificate<br><br>On MySQL starting from 5.7.11 and PostgreSQL the following values are supported: "required", "verify", "verify\_full". On MariaDB starting from version 10.2.6 "required" and "verify\_full" values are supported.<br>By default not set to any option and the behavior depends on database configuration.<br><br>This parameter is supported since Zabbix 5.0.0.| |DBTLSCAFile|no<br>(yes, if DBTLSConnect set to one of: verify\_ca, verify\_full)|<|<|Full pathname of a file containing the top-level CA(s) certificates for database certificate verification.<br>This parameter is supported since Zabbix 5.0.0.| |DBTLSCertFile|no|<|<|Full pathname of file containing Zabbix server certificate for authenticating to database.<br>This parameter is supported since Zabbix 5.0.0.| |DBTLSKeyFile|no|<|<|Full pathname of file containing the private key for authenticating to database.<br>This parameter is supported since Zabbix 5.0.0.| |DBTLSCipher|no|<|<|The list of encryption ciphers that Zabbix server permits for TLS protocols up through TLSv1.2.<br>Supported only for MySQL.<br>This parameter is supported since Zabbix 5.0.0.| |DBTLSCipher13|no|<|<|The list of encryption ciphersuites that Zabbix server permits for TLSv1.3 protocol.<br>Supported only for MySQL, starting from version 8.0.16.<br>This parameter is supported since Zabbix 5.0.0.| |DebugLevel|no|0-5|3|Specifies debug level:<br>0 - basic information about starting and stopping of Zabbix processes<br>1 - critical information<br>2 - error information<br>3 - warnings<br>4 - for debugging (produces lots of information)<br>5 - extended debugging (produces even more information)| |EnableRemoteCommands|no|<|0|Whether remote commands from Zabbix server are allowed.<br>0 - not allowed<br>1 - allowed<br>This parameter is supported since Zabbix 3.4.0.| |ExternalScripts|no|<|/usr/local/share/zabbix/externalscripts|Location of external scripts (depends on compile-time installation variable *datadir*).| |Fping6Location|no|<|/usr/sbin/fping6|Location of fping6.<br>Make sure that fping6 binary has root ownership and SUID flag set.<br>Make empty ("Fping6Location=") if your fping utility is capable to process IPv6 addresses.| |FpingLocation|no|<|/usr/sbin/fping|Location of fping.<br>Make sure that fping binary has root ownership and SUID flag set!| |HeartbeatFrequency|no|0-3600|60|Frequency of heartbeat messages in seconds.<br>Used for monitoring availability of proxy on server side.<br>0 - heartbeat messages disabled.<br>Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter).| |HistoryCacheSize|no|128K-2G|16M|Size of history cache, in bytes.<br>Shared memory size for storing history data.| |HistoryIndexCacheSize|no|128K-2G|4M|Size of history index cache, in bytes.<br>Shared memory size for indexing history data stored in history cache.<br>The index cache size needs roughly 100 bytes to cache one item.<br>This parameter is supported since Zabbix 3.0.0.| |Hostname|no|<|Set by HostnameItem|Unique, case sensitive Proxy name. Make sure the proxy name is known to the server!<br>Allowed characters: alphanumeric, '.', ' ', '\_' and '-'.<br>Maximum length: 128| |HostnameItem|no|<|system.hostname|Item used for setting Hostname if it is undefined (this will be run on the proxy similarly as on an agent).<br>Does not support UserParameters, performance counters or aliases, but does support system.run\[\].<br><br>Ignored if Hostname is set.| |HousekeepingFrequency|no|0-24|1|How often Zabbix will perform housekeeping procedure (in hours).<br>Housekeeping is removing outdated information from the database.<br>*Note*: To prevent housekeeper from being overloaded (for example, when configuration parameters ProxyLocalBuffer or ProxyOfflineBuffer are greatly reduced), no more than 4 times HousekeepingFrequency hours of outdated information are deleted in one housekeeping cycle. Thus, if HousekeepingFrequency is 1, no more than 4 hours of outdated information (starting from the oldest entry) will be deleted per cycle.<br>*Note*: To lower load on proxy startup housekeeping is postponed for 30 minutes after proxy start. Thus, if HousekeepingFrequency is 1, the very first housekeeping procedure after proxy start will run after 30 minutes, and will repeat every hour thereafter.<br>Since Zabbix 3.0.0 it is possible to disable automatic housekeeping by setting HousekeepingFrequency to 0. In this case the housekeeping procedure can only be started by *housekeeper\_execute* runtime control option and the period of outdated information deleted in one housekeeping cycle is 4 times the period since the last housekeeping cycle, but not less than 4 hours and not greater than 4 days.| |Include|no|<|<|You may include individual files or all files in a directory in the configuration file.<br>To only include relevant files in the specified directory, the asterisk wildcard character is supported for pattern matching. For example: `/absolute/path/to/config/files/*.conf`.<br>See [special notes](special_notes_include) about limitations.| |JavaGateway|no|<|<|IP address (or hostname) of Zabbix Java gateway.<br>Only required if Java pollers are started.| |JavaGatewayPort|no|1024-32767|10052|Port that Zabbix Java gateway listens on.| |ListenBacklog|no|0 - INT\_MAX|SOMAXCONN|The maximum number of pending connections in the TCP queue.<br>Default value is a hard-coded constant, which depends on the system.<br>Maximum supported value depends on the system, too high values may be silently truncated to the 'implementation-specified maximum'.| |ListenIP|no|<|0.0.0.0|List of comma delimited IP addresses that the trapper should listen on.<br>Trapper will listen on all network interfaces if this parameter is missing.| |ListenPort|no|1024-32767|10051|Listen port for trapper.| |LoadModule|no|<|<|Module to load at proxy startup. Modules are used to extend functionality of the proxy.<br>Formats:<br>LoadModule=<module.so><br>LoadModule=<path/module.so><br>LoadModule=</abs\_path/module.so><br>Either the module must be located in directory specified by LoadModulePath or the path must precede the module name. If the preceding path is absolute (starts with '/') then LoadModulePath is ignored.<br>It is allowed to include multiple LoadModule parameters.| |LoadModulePath|no|<|<|Full path to location of proxy modules.<br>Default depends on compilation options.| |LogFile|yes, if LogType is set to *file*, otherwise<br>no|<|<|Name of log file.| |LogFileSize|no|0-1024|1|Maximum size of log file in MB.<br>0 - disable automatic log rotation.<br>*Note*: If the log file size limit is reached and file rotation fails, for whatever reason, the existing log file is truncated and started anew.| |LogRemoteCommands|no|<|0|Enable logging of executed shell commands as warnings.<br>0 - disabled<br>1 - enabled<br>This parameter is supported since Zabbix 3.4.0.| |LogType|no|<|file|Log output type:<br>*file* - write log to file specified by LogFile parameter,<br>*system* - write log to syslog,<br>*console* - write log to standard output.<br>This parameter is supported since Zabbix 3.0.0.| |LogSlowQueries|no|0-3600000|0|How long a database query may take before being logged (in milliseconds).<br>0 - don't log slow queries.<br>This option becomes enabled starting with DebugLevel=3.| |PidFile|no|<|/tmp/zabbix\_proxy.pid|Name of PID file.| |ProxyLocalBuffer|no|0-720|0|Proxy will keep data locally for N hours, even if the data have already been synced with the server.<br>This parameter may be used if local data will be used by third party applications.| |ProxyMode|no|0-1|0|Proxy operating mode.<br>0 - proxy in the active mode<br>1 - proxy in the passive mode<br>*Note* that (sensitive) proxy configuration data may become available to parties having access to the Zabbix server trapper port when using an active proxy. This is possible because anyone may pretend to be an active proxy and request configuration data; authentication does not take place.| |ProxyOfflineBuffer|no|1-720|1|Proxy will keep data for N hours in case of no connectivity with Zabbix server.<br>Older data will be lost.| |ServerPort|no|1024-32767|10051|Port of Zabbix trapper on Zabbix server.<br>Active proxy parameter. Ignored for passive proxies (see ProxyMode parameter).| |Server|yes|<|<|If ProxyMode is set to *active mode*:<br>Zabbix server IP address or DNS name (address:port) or [cluster](/manual/concepts/server/ha) (address:port;address2:port) to get configuration data from and send data to.<br>If port is not specified, the default port is used.<br>Cluster nodes must be separated by a semicolon.<br><br>If ProxyMode is set to *passive mode*:<br>List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of Zabbix server. Incoming connections will be accepted only from the addresses listed here. If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally.<br>'::/0' will allow any IPv4 or IPv6 address. '0.0.0.0/0' can be used to allow any IPv4 address.<br>*Example*: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com| |SNMPTrapperFile|no|<|/tmp/zabbix\_traps.tmp|Temporary file used for passing data from SNMP trap daemon to the proxy.<br>Must be the same as in zabbix\_trap\_receiver.pl or SNMPTT configuration file.| |SocketDir|no|<|/tmp|Directory to store IPC sockets used by internal Zabbix services.<br>This parameter is supported since Zabbix 3.4.0.| |SourceIP|no|<|<|Source IP address for:<br>- outgoing connections to Zabbix server;<br>- agentless connections (VMware, SSH, JMX, SNMP, Telnet and simple checks);<br>- HTTP agent connections;<br>- script item JavaScript HTTP requests;<br>- preprocessing JavaScript HTTP requests;<br>- connections to the Vault| |SSHKeyLocation|no|<|<|Location of public and private keys for SSH checks and actions| |SSLCertLocation|no|<|<|Location of SSL client certificate files for client authentication.<br>This parameter is used in web monitoring only.| |SSLKeyLocation|no|<|<|Location of SSL private key files for client authentication.<br>This parameter is used in web monitoring only.| |SSLCALocation|no|<|<|Location of certificate authority (CA) files for SSL server certificate verification.<br>Note that the value of this parameter will be set as libcurl option CURLOPT\_CAPATH. For libcurl versions before 7.42.0, this only has effect if libcurl was compiled to use OpenSSL. For more information see [cURL web page](http://curl.haxx.se/libcurl/c/CURLOPT_CAPATH.html).<br>This parameter is used in web monitoring since Zabbix 2.4.0 and in SMTP authentication since Zabbix 3.0.0.| |StartDBSyncers|no|1-100|4|Number of pre-forked instances of [history syncers](/manual/concepts/proxy#proxy_process_types).<br>*Note*: Be careful when changing this value, increasing it may do more harm than good.| |StartDiscoverers|no|0-250|1|Number of pre-forked instances of [discoverers](/manual/concepts/proxy#proxy_process_types).| |StartHistoryPollers|no|0-1000|1|Number of pre-forked instances of [history pollers](/manual/concepts/proxy#proxy_process_types).<br>This parameter is supported since Zabbix 5.4.0.| |StartHTTPPollers|no|0-1000|1|Number of pre-forked instances of [HTTP pollers](/manual/concepts/proxy#proxy_process_types).| |StartIPMIPollers|no|0-1000|0|Number of pre-forked instances of [IPMI pollers](/manual/concepts/proxy#proxy_process_types).| |StartJavaPollers|no|0-1000|0|Number of pre-forked instances of [Java pollers](/manual/concepts/proxy#proxy_process_types).| |StartPingers|no|0-1000|1|Number of pre-forked instances of [ICMP pingers](/manual/concepts/proxy#proxy_process_types).| |StartPollersUnreachable|no|0-1000|1|Number of pre-forked instances of [pollers for unreachable](/manual/concepts/proxy#proxy_process_types) hosts (including IPMI and Java).<br>At least one poller for unreachable hosts must be running if regular, IPMI or Java pollers are started.| |StartPollers|no|0-1000|5|Number of pre-forked instances of [pollers](/manual/concepts/proxy#proxy_process_types).| |StartPreprocessors|no|1-1000|3|Number of pre-forked instances of preprocessing [workers](/manual/concepts/proxy#proxy_process_types)**^[1](zabbix_server#footnotes)^**.<br>The preprocessing manager process is automatically started when a preprocessor worker is started.<br>This parameter is supported since Zabbix 4.2.0.| |StartSNMPTrapper|no|0-1|0|If set to 1, [SNMP trapper](/manual/concepts/proxy#proxy_process_types) process will be started.| |StartTrappers|no|0-1000|5|Number of pre-forked instances of [trappers](/manual/concepts/proxy#proxy_process_types).<br>Trappers accept incoming connections from Zabbix sender and active agents.| |StartVMwareCollectors|no|0-250|0|Number of pre-forked [VMware collector](/manual/concepts/proxy#proxy_process_types) instances.| |StatsAllowedIP|no|<|<|List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of external Zabbix instances. Stats request will be accepted only from the addresses listed here. If this parameter is not set no stats requests will be accepted.<br>If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally and '::/0' will allow any IPv4 or IPv6 address. '0.0.0.0/0' can be used to allow any IPv4 address.<br>Example: StatsAllowedIP=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com<br>This parameter is supported since Zabbix 4.2.0.| |Timeout|no|1-30|3|Specifies how long we wait for agent, SNMP device or external check (in seconds).| |TLSAccept|yes for passive proxy, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no|<|<|What incoming connections to accept from Zabbix server. Used for a passive proxy, ignored on an active proxy. Multiple values can be specified, separated by comma:<br>*unencrypted* - accept connections without encryption (default)<br>*psk* - accept connections with TLS and a pre-shared key (PSK)<br>*cert* - accept connections with TLS and a certificate<br>This parameter is supported since Zabbix 3.0.0.| |TLSCAFile|no|<|<|Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCertFile|no|<|<|Full pathname of a file containing the proxy certificate or certificate chain, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSCipherAll|no|<|<|GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.<br>Example: TLS\_AES\_256\_GCM\_SHA384:TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherAll13|no|<|<|Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate- and PSK-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL::+SIGN-ALL:+CTYPE-X.509<br>Example for OpenSSL: EECDH+aRSA+AES128:RSA+aRSA+AES128:kECDHEPSK+AES128:kPSK+AES128<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherCert|no|<|<|GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for certificate-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-RSA:+RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509<br>Example for OpenSSL: EECDH+aRSA+AES128:RSA+aRSA+AES128<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherCert13|no|<|<|Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for certificate-based encryption.<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherPSK|no|<|<|GnuTLS priority string or OpenSSL (TLS 1.2) cipher string. Override the default ciphersuite selection criteria for PSK-based encryption.<br>Example for GnuTLS: NONE:+VERS-TLS1.2:+ECDHE-PSK:+PSK:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+SHA1:+CURVE-ALL:+COMP-NULL:+SIGN-ALL<br>Example for OpenSSL: kECDHEPSK+AES128:kPSK+AES128<br>This parameter is supported since Zabbix 4.4.7.| |TLSCipherPSK13|no|<|<|Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3. Override the default ciphersuite selection criteria for PSK-based encryption.<br>Example: TLS\_CHACHA20\_POLY1305\_SHA256:TLS\_AES\_128\_GCM\_SHA256<br>This parameter is supported since Zabbix 4.4.7.| |TLSConnect|yes for active proxy, if TLS certificate or PSK parameters are defined (even for *unencrypted* connection), otherwise no|<|<|How the proxy should connect to Zabbix server. Used for an active proxy, ignored on a passive proxy. Only one value can be specified:<br>*unencrypted* - connect without encryption (default)<br>*psk* - connect using TLS and a pre-shared key (PSK)<br>*cert* - connect using TLS and a certificate<br>This parameter is supported since Zabbix 3.0.0.| |TLSCRLFile|no|<|<|Full pathname of a file containing revoked certificates.This parameter is used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSKeyFile|no|<|<|Full pathname of a file containing the proxy private key, used for encrypted communications between Zabbix components.<br>This parameter is supported since Zabbix 3.0.0.| |TLSPSKFile|no|<|<|Full pathname of a file containing the proxy pre-shared key. used for encrypted communications with Zabbix server.<br>This parameter is supported since Zabbix 3.0.0.| |TLSPSKIdentity|no|<|<|Pre-shared key identity string, used for encrypted communications with Zabbix server.<br>This parameter is supported since Zabbix 3.0.0.| |TLSServerCertIssuer|no|<|<|Allowed server certificate issuer.<br>This parameter is supported since Zabbix 3.0.0.| |TLSServerCertSubject|no|<|<|Allowed server certificate subject.<br>This parameter is supported since Zabbix 3.0.0.| |TmpDir|no|<|/tmp|Temporary directory.| |TrapperTimeout|no|1-300|300|Specifies how many seconds trapper may spend processing new data.| |User|no|<|zabbix|Drop privileges to a specific, existing user on the system.<br>Only has effect if run as 'root' and AllowRoot is disabled.| |UnavailableDelay|no|1-3600|60|How often host is checked for availability during the [unavailability](/manual/appendix/items/unreachability#unavailable_host) period, in seconds.| |UnreachableDelay|no|1-3600|15|How often host is checked for availability during the [unreachability](/manual/appendix/items/unreachability#unreachable_host) period, in seconds.| |UnreachablePeriod|no|1-3600|45|After how many seconds of [unreachability](/manual/appendix/items/unreachability#unreachable_host) treat a host as unavailable.| |VaultDBPath|no|<|<|Vault path from where credentials for database will be retrieved by keys 'password' and 'username'.<br>Example: secret/zabbix/database<br>This option can only be used if DBUser and DBPassword are not specified.<br>This parameter is supported since Zabbix 5.2.0.| |VaultToken|no|<|<|Vault authentication token that should have been generated exclusively for Zabbix proxy with read-only permission to the path specified in the optional VaultDBPath configuration parameter.<br>It is an error if VaultToken and VAULT\_TOKEN environment variable are defined at the same time.<br>This parameter is supported since Zabbix 5.2.0.| |VaultURL|no|<|https://127.0.0.1:8200|Vault server HTTP\[S\] URL. System-wide CA certificates directory will be used if SSLCALocation is not specified.<br>This parameter is supported since Zabbix 5.2.0.| |VMwareCacheSize|no|256K-2G|8M|Shared memory size for storing VMware data.<br>A VMware internal check zabbix\[vmware,buffer,...\] can be used to monitor the VMware cache usage (see [Internal checks](/manual/config/items/itemtypes/internal)).<br>Note that shared memory is not allocated if there are no vmware collector instances configured to start.| |VMwareFrequency|no|10-86400|60|Delay in seconds between data gathering from a single VMware service.<br>This delay should be set to the least update interval of any VMware monitoring item.| |VMwarePerfFrequency|no|10-86400|60|Delay in seconds between performance counter statistics retrieval from a single VMware service.<br>This delay should be set to the least update interval of any VMware monitoring [item](/manual/config/items/itemtypes/simple_checks/vmware_keys#footnotes) that uses VMware performance counters.| |VMwareTimeout|no|1-300|10|The maximum number of seconds vmware collector will wait for a response from VMware service (vCenter or ESX hypervisor).|  

en-us	#### Parameters  |Parameter|Mandatory|Range|Default|Description| |--|--|--|--|----------| |Plugins.Ceph.Default.ApiKey|no| | |Default API key for connecting to Ceph; used if no value is specified in an item key or named session.<br> Supported since version 6.0.18| |Plugins.Ceph.Default.User|no| | |Default username for connecting to Ceph; used if no value is specified in an item key or named session.<br> Supported since version 6.0.18| |Plugins.Ceph.Default.Uri|no| |https://localhost:8003 |Default URI for connecting to Ceph; used if no value is specified in an item key or named session. <br><br>Should not include embedded credentials (they will be ignored).<br>Must match the URI format.<br>Only `https` scheme is supported; a scheme can be omitted.<br>A port can be omitted (default=8003).<br>Examples: `https://127.0.0.1:8003`<br>`localhost`<br> Supported since version 6.0.18| |Plugins.Ceph.InsecureSkipVerify|no|false / true|false|Determines whether an http client should verify the server's certificate chain and host name.<br>If *true*, TLS accepts any certificate presented by the server and any host name in that certificate. In this mode, TLS is susceptible to man-in-the-middle attacks (should be used only for testing).| |Plugins.Ceph.KeepAlive|no|60-900|300|The maximum time of waiting (in seconds) before unused plugin connections are closed.| |Plugins.Ceph.Sessions.<SessionName>.ApiKey|no| | |Named session API key.<br>**<SessionName>** - define name of a session for using in item keys.| |Plugins.Ceph.Sessions.<SessionName>.User|no| | |Named session username.<br>**<SessionName>** - define name of a session for using in item keys.| |Plugins.Ceph.Sessions.<SessionName>.Uri|no| | |Connection string of a named session.<br>**<SessionName>** - define name of a session for using in item keys.<br><br>Should not include embedded credentials (they will be ignored).<br>Must match the URI format.<br>Only `https` scheme is supported; a scheme can be omitted.<br>A port can be omitted (default=8003).<br>Examples: `https://127.0.0.1:8003`<br>`localhost`| |Plugins.Ceph.Timeout|no|1-30|global timeout|Request execution timeout (how long to wait for a request to complete before shutting it down).|  See also:  -   Description of general Zabbix agent 2 configuration parameters:     [Zabbix agent 2 (UNIX)](/manual/appendix/config/zabbix_agent2) /     [Zabbix agent 2     (Windows)](/manual/appendix/config/zabbix_agent2_win) -   Instructions for configuring [plugins](/manual/config/items/plugins)
ja	#### パラメータ  |パラメータ|必須|範囲|デフォルト|説明| |--|--|--|--|----------| |Plugins.Ceph.Default.ApiKey|no| | |Ceph に接続するためのデフォルトの API キー。アイテム キーまたは名前付きセッションに値が指定されていない場合に使用されます。<br> バージョン 6.0.18 以降でサポートされています| |Plugins.Ceph.Default.User|no| | |Ceph に接続するためのデフォルトのユーザー名。アイテム キーまたは名前付きセッションに値が指定されていない場合に使用されます。<br> バージョン 6.0.18 以降でサポートされています| |Plugins.Ceph.Default.Uri|no| |https://localhost:8003 |Ceph に接続するためのデフォルトの URI。項目キーまたは名前付きセッションに値が指定されていない場合に使用されます。<br><br>埋め込まれた資格情報を含めないでください (無視されます)。<br>URI 形式と一致する必要があります。<br>サポートされているのは `https` スキームのみです。スキームは省略できます。<br>ポートは省略できます (デフォルト = 8003)。<br>例: `https://127.0.0.1:8003`<br>`localhost`<br> バージョン 6.0.18 以降でサポートされています| |Plugins.Ceph.InsecureSkipVerify|no|false / true|false|httpクライアントがサーバーの証明書チェーンとホスト名を確認する必要があるかどうかを決定します。<br>*true*の場合、TLSはサーバーによって提示された証明書とその証明書内のホスト名を受け入れます。 このモードでは、TLSは中間者攻撃の影響を受けやすくなります（テストにのみ使用してください）| |Plugins.Ceph.KeepAlive|no|60-900|300|未使用のプラグイン接続が閉じられるまでの最大待機時間（秒単位）| |Plugins.Ceph.Sessions.<SessionName>.ApiKey|no| | |名前付きセッションAPIキー<br>**<SessionName>** - アイテムキーで使用するセッションの名前| |Plugins.Ceph.Sessions.<SessionName>.User|no| | |名前付きセッションのユーザー名<br>**<SessionName>** - アイテムキーで使用するセッションの名前| |Plugins.Ceph.Sessions.<SessionName>.Uri|no| |https://localhost:8003|名前付きセッションの接続文字列<br>**<SessionName>** - アイテムキーで使用するセッション名<br><br>IDやパスワードといった認証情報を含めないでください（無視されます）<br>必須 URI形式と一致します<br>サポートされているのは`https`スキームのみです。 スキームは省略できます（バージョン5.2.3以降）<br>ポートは省略できます（デフォルト= 8003）<br>例: `https://127.0.0.1:8003`<br>`localhost`| |Plugins.Ceph.Timeout|no|1-30|global timeout|リクエストの実行タイムアウト（リクエストが完了するのを待ってからシャットダウンするまでの時間）|  参考情報:  -   一般的なZabbixエージェント2の設定パラメータの説明 : [Zabbix agent 2 (UNIX)](/manual/appendix/config/zabbix_agent2) / [Zabbix agent 2 (Windows)](/manual/appendix/config/zabbix_agent2_win) -   [プラグイン](/manual/config/items/plugins)の設定手順

en-us	#### Parameters  |Parameter|Mandatory|Range|Default|Description| |--|--|--|--|----------| |Plugins.Memcached.KeepAlive|no|60-900|300|The maximum time of waiting (in seconds) before unused plugin connections are closed.| |Plugins.Memcached.Sessions.<SessionName>.Password|no|<|<|Named session password.<br>**<SessionName>** - name of a session for using in item keys.| |Plugins.Memcached.Sessions.<SessionName>.Uri|no|<|tcp://localhost:11211|Connection string of a named session.<br>**<SessionName>** - name of a session for using in item keys.<br><br>Should not include embedded credentials (they will be ignored).<br>Must match the URI format.<br>Supported schemes: `tcp`, `unix`; a scheme can be omitted (since version 5.2.3).<br>A port can be omitted (default=11211).<br>Examples: `tcp://localhost:11211`<br>`localhost`<br>`unix:/var/run/memcached.sock`| |Plugins.Memcached.Sessions.<SessionName>.User|no|<|<|Named session username.<br>**<SessionName>** - name of a session for using in item keys.| |Plugins.Memcached.Timeout|no|1-30|global timeout|Request execution timeout (how long to wait for a request to complete before shutting it down).|  See also:  -   Description of general Zabbix agent 2 configuration parameters:     [Zabbix agent 2 (UNIX)](/manual/appendix/config/zabbix_agent2) /     [Zabbix agent 2     (Windows)](/manual/appendix/config/zabbix_agent2_win) -   Instructions for configuring [plugins](/manual/config/items/plugins)
ja	#### パラメータ  |パラメータ|必須|範囲|デフォルト|説明| |--|--|--|--|----------| |Plugins.Memcached.KeepAlive|no|60-900|300|未使用のプラグイン接続が閉じられるまでの最大待機時間（秒単位）| |Plugins.Memcached.Sessions.<SessionName>.Password|no|<|<|名前付きセッションパスワード<br>**<SessionName>** - アイテムキーで使用するセッションの名前| |Plugins.Memcached.Sessions.<SessionName>.Uri|no|<|tcp://localhost:11211|名前付きセッションの接続文字列<br>**<SessionName>** - アイテムキーで使用するセッション名<br><br>埋め込みクレデンシャルを含めないでください（無視されます）<br>必須 URI形式に一致します<br>サポートされているスキーム：`tcp`、` unix`  スキームは省略できます（バージョン5.2.3以降）<br>ポートは省略できます（デフォルト= 11121）<br>例: `tcp://localhost:11211`<br>`localhost`<br>`unix:/var/run/memcached.sock`| |Plugins.Memcached.Sessions.<SessionName>.User|no|<|<|名前付きセッションのユーザー名<br> **<SessionName>** - アイテムキーで使用するセッション名| |Plugins.Memcached.Timeout|no|1-30|global timeout|リクエストの実行タイムアウト（リクエストが完了するのを待ってからシャットダウンするまでの時間）|  参考情報:  -   一般的なZabbixエージェント2の設定パラメータの説明 : [Zabbix agent 2 (UNIX)](/manual/appendix/config/zabbix_agent2)/[Zabbix agent 2 (Windows)](/manual/appendix/config/zabbix_agent2_win) -   [プラグイン](/manual/config/items/plugins)の設定手順

en-us	#### Parameters  |Parameter|Mandatory|Range|Default|Description| |--|--|--|--|----------| |Plugins.Modbus.Sessions.<SessionName>.Endpoint|no|<|<|Endpoint is a connection string consisting of a protocol scheme, a host address and a port or seral port name and attributes.<br>**<SessionName>** - name of a session for using in item keys.| |Plugins.Modbus.Sessions.<SessionName>.SlaveID|no|<|<|Slave ID of a named session.<br>**<SessionName>** - name of a session for using in item keys.<br>Example: `Plugins.Modbus.Sessions.MB1.SlaveID=20`<br>*Note* that this named session parameter is checked only if the value provided in the [item key](/manual/config/items/itemtypes/zabbix_agent) slave ID parameter is empty.| |Plugins.Modbus.Sessions.<SessionName>.Timeout|no|<|<|Timeout of a named session.<br>**<SessionName>** - name of a session for using in item keys.<br>Example: `Plugins.Modbus.Sessions.MB1.Timeout=2`| |Plugins.Modbus.Timeout|no|1-30|global timeout|Request execution timeout (how long to wait for a request to complete before shutting it down).|  See also:  -   Description of general Zabbix agent 2 configuration parameters:     [Zabbix agent 2 (UNIX)](/manual/appendix/config/zabbix_agent2) /     [Zabbix agent 2     (Windows)](/manual/appendix/config/zabbix_agent2_win) -   Instructions for configuring [plugins](/manual/config/items/plugins)
ja	#### パラメータ  |パラメータ|必須|範囲|デフォルト|説明| |--|--|--|--|----------| |Plugins.Modbus.Sessions.<SessionName>.Endpoint|no|<|<|エンドポイントは、プロトコルスキーム、ホストアドレス、ポートまたはシリアルポートの名前と属性で構成される接続文字列です<br>**<SessionName>** - アイテムキーで使用するセッション名| |Plugins.Modbus.Sessions.<SessionName>.SlaveID|no|<|<|名前付きセッションのスレーブID<br>**<SessionName>** - アイテムキーで使用するセッション名<br>例: `Plugins.Modbus.Sessions.MB1.SlaveID=20`<br>*注* この名前付きセッションパラメータは[アイテムキー](/manual/config/items/itemtypes/zabbix_agent)スレーブIDパラメータで指定された値が空の場合にのみチェックされます。| |Plugins.Modbus.Sessions.<SessionName>.Timeout|no|<|<|名前付きセッションのタイムアウト<br>**<SessionName>** - アイテムキーで使用するセッション名<br>例: `Plugins.Modbus.Sessions.MB1.Timeout=2`| |Plugins.Modbus.Timeout|no|1-30|global timeout|リクエストの実行タイムアウト（リクエストが完了するのを待ってからシャットダウンするまでの時間）|  参考情報:  -   一般的なZabbixエージェント2の設定パラメータの説明 : [Zabbix agent 2 (UNIX)](/manual/appendix/config/zabbix_agent2)/[Zabbix agent 2 (Windows)](/manual/appendix/config/zabbix_agent2_win) -   [プラグイン](/manual/config/items/plugins)の設定手順

en-us	#### Parameters  |Parameter|Mandatory|Range|Default|Description| |--|--|--|--|----------| |Plugins.Mysql.CallTimeout|no|1-30|global timeout|The maximum amount of time in seconds to wait for a request to be done.| |Plugins.Mysql.KeepAlive|no|60-900|300|The maximum time of waiting (in seconds) before unused plugin connections are closed.| |Plugins.Mysql.Sessions.<SessionName>.Password|no|<|<|Named session password.<br>**<SessionName>** - name of a session for using in item keys.| |Plugins.Mysql.Sessions.<SessionName>.TLSCAFile|no|<|<|Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix agent 2 and monitored databases.<br>**<SessionName>** - name of a session for using in item keys.| |Plugins.Mysql.Sessions.<SessionName>.TLSCertFile|no|<|<|Full pathname of a file containing the agent certificate or certificate chain, used for encrypted communications between Zabbix agent 2 and monitored databases.<br>**<SessionName>** - name of a session for using in item keys.| |Plugins.Mysql.Sessions.<SessionName>.TLSConnect|no|<|<|Encryption type for communications between Zabbix agent 2 and monitored databases.<br>**<SessionName>** - name of a session for using in item keys.<br><br>Accepted values:<br>*required* - require TLS connection;<br>*verify\_ca* - verify certificates;<br>*verify\_full* - verify certificates and IP address.| |Plugins.Mysql.Sessions.<SessionName>.TLSKeyFile|no|<|<|Full pathname of a file containing the database private key used for encrypted communications between Zabbix agent 2 and monitored databases.<br>**<SessionName>** - name of a session for using in item keys.| |Plugins.Mysql.Sessions.<SessionName>.Uri|no|<|tcp://localhost:3306|Connection string of a named session.<br>**<SessionName>** - name of a session for using in item keys.<br><br>Should not include embedded credentials (they will be ignored).<br>Must match the URI format.<br>Supported schemes: `tcp`, `unix`; a scheme can be omitted (since version 5.2.3).<br>A port can be omitted (default=3306).<br>Examples: `tcp://localhost:3306`<br>`localhost`<br>`unix:/var/run/mysql.sock`| |Plugins.Mysql.Sessions.<SessionName>.User|no|<|<|Named session username.<br>**<SessionName>** - name of a session for using in item keys.| |Plugins.Mysql.Timeout|no|1-30|global timeout|Request execution timeout (how long to wait for a request to complete before shutting it down).|  See also:  -   Description of general Zabbix agent 2 configuration parameters:     [Zabbix agent 2 (UNIX)](/manual/appendix/config/zabbix_agent2) /     [Zabbix agent 2     (Windows)](/manual/appendix/config/zabbix_agent2_win) -   Instructions for configuring [plugins](/manual/config/items/plugins)
ja	#### パラメータ  |パラメータ|必須|範囲|デフォルト|説明| |--|--|--|--|----------| |Plugins.Mysql.CallTimeout|no|1-30|global timeout|要求が実行されるのを待機する最大時間（秒単位）| |Plugins.Mysql.KeepAlive|no|60-900|300|未使用のプラグイン接続が閉じられるまでの最大待機時間（秒単位）| |Plugins.Mysql.Sessions.<SessionName>.Password|no|<|<|名前付きセッションパスワード<br>**<SessionName>** - アイテムキーで使用するセッションの名前| |Plugins.Mysql.Sessions.<SessionName>.TLSCAFile|no|<|<|Zabbixエージェント2と監視対象データベース間の暗号化された通信に使用される、ピア証明書検証用の最上位CA証明書を含むファイルのフルパス名<br>**<SessionName>** - アイテムキーで使用するセッションの名前| |Plugins.Mysql.Sessions.<SessionName>.TLSCertFile|no|<|<|Zabbixエージェント2と監視対象データベース間の暗号化された通信に使用される、エージェント証明書または証明書チェーンを含むファイルのフルパス名<br> **<SessionName>** - アイテムキーで使用するセッションの名前| |Plugins.Mysql.Sessions.<SessionName>.TLSConnect|no|<|<|Zabbixエージェント2と監視対象データベース間の通信の暗号化タイプ<br>**<SessionName>** - アイテムキーで使用するセッション名<br><br>使用可能な値:<br>*required* - require TLS接続;<br>*verify\_ca* - 証明書を検証します<br>*verify\_full* - 証明書とIPアドレスを検証します| |Plugins.Mysql.Sessions.<SessionName>.TLSKeyFile|no|<|<|Zabbixエージェント2と監視対象データベース間の暗号化された通信に使用されるデータベース秘密鍵を含むファイルの絶対パス名<br>**<SessionName>** - アイテム鍵で使用するセッション名| |Plugins.Mysql.Sessions.<SessionName>.Uri|no|<|tcp://localhost:3306|名前付きセッションの接続文字列<br>**<SessionName>** - アイテムキーで使用するセッション名<br><br>埋め込みクレデンシャルを含めないでください（無視されます）<br>必須 URI形式に一致します<br>サポートされているスキーム：`tcp`,` unix`  スキームは省略できます（バージョン5.2.3以降）<br>ポートは省略できます（デフォルト= 3306）<br>例: `tcp://localhost:3306`<br>`localhost`<br>`unix:/var/run/mysql.sock`| |Plugins.Mysql.Sessions.<SessionName>.User|no|<|<|名前付きセッションパスワード<br>**<SessionName>** - アイテムキーで使用するセッションの名前| |Plugins.Mysql.Timeout|no|1-30|global timeout|リクエストの実行タイムアウト（リクエストが完了するのを待ってからシャットダウンするまでの時間）|  参考情報:  -   一般的なZabbixエージェント2の設定パラメータの説明 : [Zabbix agent 2 (UNIX)](/manual/appendix/config/zabbix_agent2)/[Zabbix agent 2 (Windows)](/manual/appendix/config/zabbix_agent2_win) -   [プラグイン](/manual/config/items/plugins)の設定手順