ZABBIXを使ってみる　その２

こんばんは、かーでぃです。
仕事でZABBIXを使うかもしれないので、個人でも使ってみようと思いまして、ZABBIXネタで暫くブログを書こうと思います。
一応、全8話の予定です。

STEP1　ZABBIX AGENTのインストール
STEP2　ZABBIX AGENTの設定　←　本記事はココ
STEP3　DockerでZABBIX Serverを立てる
STEP4　Server設定
STEP5　監視が始まる瞬間を監視する
STEP6　トリガーの定義
STEP7　アラート設定＆通知
STEP8　総括？

コンフィグファイル

ZABBIXの設定は、コンフィグファイルを編集します。
ということで、コンフィグファイルの場所ですが、Windowsだとこちらになります。

C:\Program Files\Zabbix Agent 2\zabbix_agent2.conf

テキストファイルなので、メモ帳で開けます。

コンフィグファイルの中身

デフォルトだと、下記のようになっています。
#から始まる行はコメント行ですね。

# This is a configuration file for Zabbix agent 2 (Windows)
# To get more information about Zabbix, visit https://www.zabbix.com

############ GENERAL PARAMETERS #################

### Option: LogType
#	Specifies where log messages are written to:
#		file    - file specified with LogFile parameter
#		console - standard output
#
# Mandatory: no
# Default:
# LogType=file


### Option: LogFile
#	Log file name for LogType 'file' parameter.
#
# Mandatory: yes, if LogType is set to file, otherwise no
# Default:
LogFile=C:\Program Files\Zabbix Agent 2\zabbix_agent2.log

### Option: LogFileSize
#	Maximum size of log file in MB.
#	0 - disable automatic log rotation.
#
# Mandatory: no
# Range: 0-1024
# Default:
# LogFileSize=1

### Option: DebugLevel
#	Specifies debug level:
#	0 - basic information about starting and stopping of Zabbix processes
#	1 - critical information
#	2 - error information
#	3 - warnings
#	4 - for debugging (produces lots of information)
#	5 - extended debugging (produces even more information)
#
# Mandatory: no
# Range: 0-5
# Default:
# DebugLevel=3

### Option: SourceIP
#	Source IP address for outgoing connections.
#
# Mandatory: no
# Default:
# SourceIP=


##### Passive checks related

### Option: Server
#	List of comma delimited IP addresses, optionally in CIDR notation, or DNS names of Zabbix servers and Zabbix proxies.
#	Incoming connections will be accepted only from the hosts listed here.
#	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.
#	Example: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.example.com
#
#   If left empty or not set will disable passive checks, and Zabbix agent 2 will not listen on the ListenPort.
#
# Mandatory: no
# Default:
# Server=

Server=127.0.0.1

### Option: ListenPort
#	Agent will listen on this port for connections from the server.
#
# Mandatory: no
# Range: 1024-32767
# Default:
# ListenPort=10050


### Option: ListenIP
#	List of comma delimited IP addresses that the agent should listen on.
#	First IP address is sent to Zabbix server if connecting to it to retrieve list of active checks.
#
# Mandatory: no
# Default:
# ListenIP=0.0.0.0


### Option: StatusPort
#	Agent will listen on this port for HTTP status requests.
#
# Mandatory: no
# Range: 1024-32767
# Default:
# StatusPort=


##### Active checks related

### Option: ServerActive
#	Zabbix server/proxy address or cluster configuration to get active checks from.
#	Server/proxy address is IP address or DNS name and optional port separated by colon.
#	Cluster configuration is one or more server addresses separated by semicolon.
#	Multiple Zabbix servers/clusters and Zabbix proxies can be specified, separated by comma.
#	More than one Zabbix proxy should not be specified from each Zabbix server/cluster.
#	If Zabbix proxy is specified then Zabbix server/cluster for that proxy should not be specified.
#	Multiple comma-delimited addresses can be provided to use several independent Zabbix servers in parallel. Spaces are allowed.
#	If port is not specified, default port is used.
#	IPv6 addresses must be enclosed in square brackets if port for that host is specified.
#	If port is not specified, square brackets for IPv6 addresses are optional.
#	If this parameter is not specified, active checks are disabled.
#	Example for Zabbix proxy:
#		ServerActive=127.0.0.1:10051
#	Example for multiple servers:
#		ServerActive=127.0.0.1:20051,zabbix.domain,[::1]:30051,::1,[12fc::1]
#	Example for high availability:
#		ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051;zabbix.cluster.node3
#	Example for high availability with two clusters and one server:
#		ServerActive=zabbix.cluster.node1;zabbix.cluster.node2:20051,zabbix.cluster2.node1;zabbix.cluster2.node2,zabbix.domain
#
# Mandatory: no
# Default:
# ServerActive=

ServerActive=127.0.0.1

### Option: Hostname
#	List of comma delimited unique, case sensitive hostnames.
#	Required for active checks and must match hostnames as configured on the server.
#	Value is acquired from HostnameItem if undefined.
#
# Mandatory: no
# Default:
# Hostname=

Hostname=TOTTENHAM

### Option: HostnameItem
#	Item used for generating Hostname if it is undefined. Ignored if Hostname is defined.
#	Does not support UserParameters or aliases.
#
# Mandatory: no
# Default:
# HostnameItem=system.hostname


### Option: HostMetadata
#	Optional parameter that defines host metadata.
#	Host metadata is used at host auto-registration process.
#	An agent will issue an error and not start if the value is over limit of 2034 bytes.
#	If not defined, value will be acquired from HostMetadataItem.
#
# Mandatory: no
# Range: 0-2034 bytes
# Default:
# HostMetadata=


### Option: HostMetadataItem
#	Optional parameter that defines an item used for getting host metadata.
#	Host metadata is used at host auto-registration process.
#	During an auto-registration request an agent will log a warning message if
#	the value returned by specified item is over limit of 65535 characters.
#	This option is only used when HostMetadata is not defined.
#
# Mandatory: no
# Default:
# HostMetadataItem=


### Option: HostInterface
#	Optional parameter that defines host interface.
#	Host interface is used at host auto-registration process.
#	An agent will issue an error and not start if the value is over limit of 255 characters.
#	If not defined, value will be acquired from HostInterfaceItem.
#
# Mandatory: no
# Range: 0-255 characters
# Default:
# HostInterface=


### Option: HostInterfaceItem
#	Optional parameter that defines an item used for getting host interface.
#	Host interface is used at host auto-registration process.
#	During an auto-registration request an agent will log a warning message if
#	the value returned by specified item is over limit of 255 characters.
#	This option is only used when HostInterface is not defined.
#
# Mandatory: no
# Default:
# HostInterfaceItem=

### Option: RefreshActiveChecks
#	How often list of active checks is refreshed, in seconds.
#
# Mandatory: no
# Range: 60-3600
# Default:
# RefreshActiveChecks=120

### Option: BufferSend
#	Do not keep data longer than N seconds in buffer.
#
# Mandatory: no
# Range: 1-3600
# Default:
# BufferSend=5

### Option: BufferSize
#	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.
#	Option is not valid if EnablePersistentBuffer=1
#
# Mandatory: no
# Range: 2-65535
# Default:
# BufferSize=1000

### Option: EnablePersistentBuffer
#	Enable usage of local persistent storage for active items.
#	0 - disabled, in-memory buffer is used (default); 1 - use persistent buffer
# Mandatory: no
# Range: 0-1
# Default:
# EnablePersistentBuffer=0


### Option: PersistentBufferPeriod
#	Zabbix Agent2 will keep data for this time period in case of no
#	connectivity with Zabbix server or proxy. Older data will be lost. Log data will be preserved.
#	Option is valid if EnablePersistentBuffer=1
#
# Mandatory: no
# Range: 1m-365d
# Default:
# PersistentBufferPeriod=1h


### Option: PersistentBufferFile
#	Full filename. Zabbix Agent2 will keep SQLite database in this file.
#	Option is valid if EnablePersistentBuffer=1
#
# Mandatory: no
# Default:
# PersistentBufferFile=


### Option: HeartbeatFrequency
#	Frequency of heartbeat messages in seconds.
#	Used for monitoring availability of active checks.
#	0 - heartbeat messages disabled.
#
# Mandatory: no
# Range: 0-3600
# Default: 60
# HeartbeatFrequency=

############ ADVANCED PARAMETERS #################

### Option: Alias
#	Sets an alias for an item key. It can be used to substitute long and complex item key with a smaller and simpler one.
#	Multiple Alias parameters may be present. Multiple parameters with the same Alias key are not allowed.
#	Different Alias keys may reference the same item key.
#	For example, to retrieve the ID of user 'zabbix':
#	Alias=zabbix.userid:vfs.file.regexp[/etc/passwd,^zabbix:.:([0-9]+),,,,\1]
#	Now shorthand key zabbix.userid may be used to retrieve data.
#	Aliases can be used in HostMetadataItem but not in HostnameItem parameters.
#
# Mandatory: no
# Range:
# Default:

### Option: Timeout
#	Specifies how long to wait (in seconds) for establishing connection and exchanging data with Zabbix proxy or server.
#
# Mandatory: no
# Range: 1-30
# Default:
# Timeout=3


### Option:PluginTimeout
#	Timeout for connections with external plugins.
#
# Mandatory: no
# Range: 1-30
# Default: <Global timeout>
# PluginTimeout=

### Option:PluginSocket
#	Path to unix socket for external plugin communications.
#
# Mandatory: no
# Default:\\.\pipe\agent.plugin.sock
# PluginSocket=

####### USER-DEFINED MONITORED PARAMETERS #######

### Option: UnsafeUserParameters
#	Allow all characters to be passed in arguments to user-defined parameters.
#	The following characters are not allowed:
#	\ ' " ` * ? [ ] { } ~ $ ! & ; ( ) < > | # @
#	Additionally, newline characters are not allowed.
#	0 - do not allow
#	1 - allow
#
# Mandatory: no
# Range: 0-1
# Default:
# UnsafeUserParameters=0


### Option: UserParameter
#	User-defined parameter to monitor. There can be several user-defined parameters.
#	Format: UserParameter=<key>,<shell command>
#	See 'zabbix_agentd' directory for examples.
#
# Mandatory: no
# Default:
# UserParameter=

### Option: UserParameterDir
#	Directory to execute UserParameter commands from. Only one entry is allowed.
#	When executing UserParameter commands the agent will change the working directory to the one
#	specified in the UserParameterDir option.
#	This way UserParameter commands can be specified using the relative ./ prefix.
#
# Mandatory: no
# Default:
# UserParameterDir=

### Option: ControlSocket
#	The control socket, used to send runtime commands with '-R' option.
#
# Mandatory: no
# Default:
# ControlSocket=

ControlSocket=\\.\pipe\agent.sock

####### TLS-RELATED PARAMETERS #######

### Option: TLSConnect
#	How the agent should connect to server or proxy. Used for active checks.
#	Only one value can be specified:
#		unencrypted - connect without encryption
#		psk         - connect using TLS and a pre-shared key
#		cert        - connect using TLS and a certificate
#
# Mandatory: yes, if TLS certificate or PSK parameters are defined (even for 'unencrypted' connection)
# Default:
# TLSConnect=unencrypted


### Option: TLSAccept
#	What incoming connections to accept.
#	Multiple values can be specified, separated by comma:
#		unencrypted - accept connections without encryption
#		psk         - accept connections secured with TLS and a pre-shared key
#		cert        - accept connections secured with TLS and a certificate
#
# Mandatory: yes, if TLS certificate or PSK parameters are defined (even for 'unencrypted' connection)
# Default:
# TLSAccept=unencrypted


### Option: TLSCAFile
#	Full pathname of a file containing the top-level CA(s) certificates for
#	peer certificate verification.
#
# Mandatory: no
# Default:
# TLSCAFile=


### Option: TLSCRLFile
#	Full pathname of a file containing revoked certificates.
#
# Mandatory: no
# Default:
# TLSCRLFile=


### Option: TLSServerCertIssuer
#		Allowed server certificate issuer.
#
# Mandatory: no
# Default:
# TLSServerCertIssuer=


### Option: TLSServerCertSubject
#		Allowed server certificate subject.
#
# Mandatory: no
# Default:
# TLSServerCertSubject=


### Option: TLSCertFile
#	Full pathname of a file containing the agent certificate or certificate chain.
#
# Mandatory: no
# Default:
# TLSCertFile=


### Option: TLSKeyFile
#	Full pathname of a file containing the agent private key.
#
# Mandatory: no
# Default:
# TLSKeyFile=


### Option: TLSPSKIdentity
#	Unique, case sensitive string used to identify the pre-shared key.
#
# Mandatory: no
# Default:
# TLSPSKIdentity=


### Option: TLSPSKFile
#	Full pathname of a file containing the pre-shared key.
#
# Mandatory: no
# Default:
# TLSPSKFile=


####### PLUGIN-SPECIFIC PARAMETERS #######

### Option: Plugins
#	A plugin can have one or more plugin specific configuration parameters in format:
#     Plugins.<PluginName>.<Parameter1>=<value1>
#     Plugins.<PluginName>.<Parameter2>=<value2>
#
# Mandatory: no
# Range:
# Default:

### Option: Plugins.Log.MaxLinesPerSecond
#	Maximum number of new lines the agent will send per second to Zabbix Server
#	or Proxy processing 'log' and 'logrt' checks.
#	The provided value will be overridden by the parameter 'maxlines',
#	provided in 'log' or 'logrt' item keys.
#
# Mandatory: no
# Range: 1-1000
# Default:
# Plugins.Log.MaxLinesPerSecond=20

### Option: Plugins.WindowsEventlog.MaxLinesPerSecond
#	Maximum number of new lines the agent will send per second to Zabbix Server
#	or Proxy processing 'eventlog' checks.
#	The provided value will be overridden by the parameter 'maxlines',
#	provided in 'eventlog' item keys.
#
# Mandatory: no
# Range: 1-1000
# Default:
# Plugins.WindowsEventlog.MaxLinesPerSecond=20

### Option: AllowKey
#	Allow execution of item keys matching pattern.
#	Multiple keys matching rules may be defined in combination with DenyKey.
#	Key pattern is wildcard expression, which support "*" character to match any number of any characters in certain position. It might be used in both key name and key arguments.
#	Parameters are processed one by one according their appearance order.
#	If no AllowKey or DenyKey rules defined, all keys are allowed.
#
# Mandatory: no

### Option: DenyKey
#	Deny execution of items keys matching pattern.
#	Multiple keys matching rules may be defined in combination with AllowKey.
#	Key pattern is wildcard expression, which support "*" character to match any number of any characters in certain position. It might be used in both key name and key arguments.
#	Parameters are processed one by one according their appearance order.
#	If no AllowKey or DenyKey rules defined, all keys are allowed.
#       Unless another system.run[*] rule is specified DenyKey=system.run[*] is added by default.
#
# Mandatory: no
# Default:
# DenyKey=system.run[*]



### Option: Plugins.SystemRun.LogRemoteCommands
#	Enable logging of executed shell commands as warnings.
#	0 - disabled
#	1 - enabled
#
# Mandatory: no
# Default:
# Plugins.SystemRun.LogRemoteCommands=0

### Option: ForceActiveChecksOnStart
#	Perform active checks immediately after restart for first received configuration.
#	Also available as per plugin configuration, example: Plugins.Uptime.System.ForceActiveChecksOnStart=1
#
# Mandatory: no
# Range: 0-1
# Default:
# ForceActiveChecksOnStart=0

# Include configuration files for plugins
Include=.\zabbix_agent2.d\plugins.d\*.conf

####### For advanced users - TLS ciphersuite selection criteria #######

### Option: TLSCipherCert13
#	Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3.
#	Override the default ciphersuite selection criteria for certificate-based encryption.
#
# Mandatory: no
# Default:
# TLSCipherCert13=

### Option: TLSCipherPSK13
#	Cipher string for OpenSSL 1.1.1 or newer in TLS 1.3.
#	Override the default ciphersuite selection criteria for PSK-based encryption.
#	Example:
#		TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256
#
# Mandatory: no
# Default:
# TLSCipherPSK13=

### Option: TLSCipherAll13
#	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.
#	Example:
#		TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256
#
# Mandatory: no
# Default:
# TLSCipherAll13=

####### Additional configuration files  #######

### Option: Include
#	You may include individual files or all files in a directory in the configuration file.
#	Installing Zabbix will create include directory in /usr/local/etc, unless modified during the compile time.
#
# Mandatory: no
# Default:
# Include=
Include=C:\Program Files\Zabbix Agent 2\zabbix_agent2.d\

# Include=c:\zabbix\zabbix_agent2.userparams.conf
# Include=c:\zabbix\zabbix_agent2.conf.d\
# Include=c:\zabbix\zabbix_agent2.conf.d\*.conf

コメント行になってないのは、以下の設定だけでした。

LogFile=C:\Program Files\Zabbix Agent 2\zabbix_agent2.log
Server=127.0.0.1
ServerActive=127.0.0.1
Hostname=TOTTENHAM
ControlSocket=\\.\pipe\agent.sock
Include=.\zabbix_agent2.d\plugins.d\*.conf
Include=C:\Program Files\Zabbix Agent 2\zabbix_agent2.d\

Server / ServerActive / Hostnameは、インストール時に設定した内容ですね。テキストファイルなのでメモ帳で編集できます。

現時点は、まだサーバを立てていませんが、サーバを立てたら、下記の項目を変更します。

• Server

• ServerActive

Serverには、サーバのIPアドレスを指定します。ActiveServerにも同じくサーバのIPアドレスを設定するのですが、厳密には意味合いがことなります。

Serverは、サーバがエージェントに情報を取得する際に使います。エージェント側に指定するのは、指定されたIPアドレス以外からの取得要請には応えません（つまり、IPアドレスが間違っていると、サーバがデータ収集できません）。

一方、ActiveServerは、エージェント側がサーバに情報をプッシュします。その際に、どのサーバにプッシュするのかを指定するアドレスが、こちらになります。

また、設定値を変更した場合は、サービスの再起動が必要です。やりがちなのが、設定を変更したまま再起動せずに、設定が反映さずに、おかしい？！設定が間違ってる→何度コンフィグを見ても間違っておらず、「なぜだーーー！！」となるコース💦（いやぁ、、昔はよくやった気がするなぁ）

再起動には、ＰＣをリセットするのが一番確実ですが、時間が掛かるのと面倒なので……スタートメニューから検索で「サービス」と入力して、サービスを起動

Zabbix Agent2を探して…

コンテキストメニューから再起動でOK

これで設定値が反映されます。

ログファイルはこちら

ちなみに、エージェントが収集したログは、こちらのファイルに蓄積されていきます。

C:\Program Files\Zabbix Agent 2\zabbix_agent2.log

こんな感じでログが溜まっていきます。

2026/01/05 18:57:16.629383 Starting Zabbix Agent 2 (7.4.6)
2026/01/05 18:57:16.837627 OpenSSL library (OpenSSL 3.5.1 1 Jul 2025) initialized
2026/01/05 18:57:16.837627 using configuration file: C:\Program Files\Zabbix Agent 2\zabbix_agent2.conf
2026/01/05 18:57:16.837627 using plugin 'Agent' (built-in) providing following interfaces: exporter, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.838155 using plugin 'Ceph' (built-in) providing following interfaces: exporter, runner, configurator, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.838155 using plugin 'Cpu' (built-in) providing following interfaces: exporter, runner, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.838678 using plugin 'DNS' (built-in) providing following interfaces: exporter, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.838678 using plugin 'File' (built-in) providing following interfaces: exporter, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.838678 using plugin 'Log' (built-in) providing following interfaces: exporter, configurator, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.838678 using plugin 'MQTT' (built-in) providing following interfaces: watcher, configurator, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.838678 using plugin 'Memcached' (built-in) providing following interfaces: exporter, runner, configurator, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.838678 using plugin 'Memory' (built-in) providing following interfaces: exporter, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.839218 using plugin 'Modbus' (built-in) providing following interfaces: exporter, configurator, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.839218 using plugin 'Mysql' (built-in) providing following interfaces: exporter, runner, configurator, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.839218 using plugin 'NetIf' (built-in) providing following interfaces: exporter, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.839218 using plugin 'Oracle' (built-in) providing following interfaces: exporter, runner, configurator, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.839218 using plugin 'Proc' (built-in) providing following interfaces: exporter, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.839218 using plugin 'Redis' (built-in) providing following interfaces: exporter, runner, configurator, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.839218 using plugin 'Registry' (built-in) providing following interfaces: exporter, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.839758 using plugin 'Smart' (built-in) providing following interfaces: exporter, configurator, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.839758 using plugin 'Sw' (built-in) providing following interfaces: exporter, configurator, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.839758 using plugin 'Swap' (built-in) providing following interfaces: exporter, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.839758 using plugin 'SystemRun' (built-in) providing following interfaces: exporter, configurator, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.839758 using plugin 'TCP' (built-in) providing following interfaces: exporter, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.839758 using plugin 'UDP' (built-in) providing following interfaces: exporter, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.840315 using plugin 'Uname' (built-in) providing following interfaces: exporter, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.840315 using plugin 'Uptime' (built-in) providing following interfaces: exporter, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.840315 using plugin 'Users' (built-in) providing following interfaces: exporter, configurator, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.840315 using plugin 'VFSDir' (built-in) providing following interfaces: exporter, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.840315 using plugin 'VMemory' (built-in) providing following interfaces: exporter, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.840315 using plugin 'VfsFs' (built-in) providing following interfaces: exporter, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.840834 using plugin 'WebCertificate' (built-in) providing following interfaces: exporter, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.840834 using plugin 'WebPage' (built-in) providing following interfaces: exporter, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.840834 using plugin 'WindowsEventlog' (built-in) providing following interfaces: exporter, configurator, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.840834 using plugin 'WindowsPerfInstance' (built-in) providing following interfaces: exporter, maximum capacity: 1, active checks on start enabled: false
2026/01/05 18:57:16.841370 using plugin 'WindowsPerfMon' (built-in) providing following interfaces: exporter, runner, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.841370 using plugin 'WindowsServices' (built-in) providing following interfaces: exporter, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.841370 using plugin 'Wmi' (built-in) providing following interfaces: exporter, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.841370 using plugin 'ZabbixAsync' (built-in) providing following interfaces: exporter, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.841370 using plugin 'ZabbixStats' (built-in) providing following interfaces: exporter, configurator, maximum capacity: 1000, active checks on start enabled: false
2026/01/05 18:57:16.841898 using plugin 'ZabbixSync' (built-in) providing following interfaces: exporter, maximum capacity: 1, active checks on start enabled: false
2026/01/05 18:57:19.707001 Plugin communication protocol version is 6.4.0
2026/01/05 18:57:19.707521 Zabbix Agent2 hostname: [TOTTENHAM]
2026/01/05 18:57:21.002607 [101] cannot connect to [127.0.0.1:10051]: dial tcp :0->127.0.0.1:10051: connectex: No connection could be made because the target machine actively refused it.
2026/01/05 18:57:21.002607 [101] active check configuration update from host [TOTTENHAM] started to fail
2026/01/05 18:57:21.003143 [101] cannot connect to [127.0.0.1:10051]: dial tcp :0->127.0.0.1:10051: connectex: No connection could be made because the target machine actively refused it.
2026/01/05 18:57:21.003695 [101] sending of heartbeat message for [TOTTENHAM] started to fail
2026/01/05 23:20:23.515718 detected 35 time difference between queue checks, rescheduling tasks
2026/01/05 23:22:14.982594 detected 110 time difference between queue checks, rescheduling tasks
2026/01/05 23:23:10.846619 detected 55 time difference between queue checks, rescheduling tasks
2026/01/05 23:25:14.811774 detected 123 time difference between queue checks, rescheduling tasks
2026/01/05 23:28:14.882876 detected 179 time difference between queue checks, rescheduling tasks
2026/01/05 23:31:15.205339 detected 180 time difference between queue checks, rescheduling tasks
2026/01/05 23:34:15.229667 detected 179 time difference between queue checks, rescheduling tasks
2026/01/05 23:37:15.320493 detected 179 time difference between queue checks, rescheduling tasks
2026/01/05 23:40:15.406543 detected 179 time difference between queue checks, rescheduling tasks
2026/01/05 23:43:15.414302 detected 179 time difference between queue checks, rescheduling tasks
2026/01/05 23:46:15.470439 detected 173 time difference between queue checks, rescheduling tasks
2026/01/05 23:49:15.560737 detected 174 time difference between queue checks, rescheduling tasks
2026/01/05 23:52:15.845437 detected 179 time difference between queue checks, rescheduling tasks

ですが、現時点でログは下記のメッセージが出力されているだけです。
"detected 20 time difference between queue checks, rescheduling tasks"

これは、エージェントが持っているタスクの実行スケジュールが遅れたために、リスケしましたわ。という感じのようです（ので、気にする必要なし）

今後、サーバの設定をすることで、エージェント側がログを蓄積していくようになります。

ここまでで「できた」状態

✅ エージェントの設定ファイルの場所がわかった
✅ 設定変更後、再起動が必要
✅ サーバを設定することで、ログがたまるようになる

今回の記事はココまで。
次回は、STEP3の「DockerでZABBIX Serverを立てる」になります。