ZABBIX_AGENTD(8)
๐ ZABBIX_AGENTD ๐
okay bestie, gather round, because this is the zabbix_agentd page from the System Manager's Manual and she is that girl ๐
โจ NAME โจ
zabbix_agentd โ the Zabbix agent daemon, aka the little guy who sits on your server and keeps an eye on everything ๐
๐ฆ SYNOPSIS ๐ฆ
zabbix_agentd [-c config-file]
zabbix_agentd [-c config-file] -p
zabbix_agentd [-c config-file] -t item-key
zabbix_agentd [-c config-file] -R runtime-option
zabbix_agentd [-c config-file] -T
zabbix_agentd -h
zabbix_agentd -V
๐ธ DESCRIPTION ๐ธ
So like. zabbix_agentd is a daemon for monitoring various server parameters. that's it, that's the whole job description, and honestly? iconic. it just vibes there, collecting your metrics, minding its business ๐
๐ OPTIONS ๐
the main character options, no skips, we're covering all of them fr fr โจ
-c,--configconfig-file โ use the alternate config-file instead of the default one. like, if you wanna be different, this is your moment ๐ซถ-f,--foregroundโ run Zabbix agent in foreground. no hiding in the background, she wants to be seen ๐-R,--runtime-controlruntime-option โ perform administrative functions according to runtime-option. very "I can do admin stuff too" energy โจ
๐ Runtime control options ๐
userparameter_reloadโ reload user parameters from the configuration file. refresh, reboot the vibes, reload the whole lewk ๐log_level_increase[=target]โ increase log level. affects all processes if target is not specified. turn the volume UP ๐ฅlog_level_decrease[=target]โ decrease log level. affects all processes if target is not specified. and now we're turning it back down, we love a range ๐
๐ Log level control targets ๐
process-typeโ all processes of specified type (active checks,collector,listener). pick a whole squad, not just one girl ๐งprocess-type,Nโ process type and number (e.g.,listener,3). so specific, so precise, we stan a targeted approach โญpidโ process identifier, up to65535. for larger values specify target as"process-type,N". yeah bestie, there's a ceiling on that one, and past65535you gotta go the"process-type,N"route ๐
๐ More options, because we're not done ๐
-p,--printโ print known items and exit. for each item either generic defaults are used, or specific defaults for testing are supplied. these defaults are listed in square brackets as item key parameters. returned values are enclosed in square brackets and prefixed with the type of the returned value, separated by a pipe character. for user parameters type is alwayst, as the agent can not determine all possible return values. items, displayed as working, are not guaranteed to work from the Zabbix server orzabbix_getwhen querying a running agent daemon, as permissions or environment may be different.
bestie listen. just because --print says an item works does NOT mean it'll work from the server side. permissions, environment, all of it can be different. it's giving "works on my machine" and we're not falling for it ๐ญ
returned value types are:
dโ number with a decimal part. decimals, we love a precise queen ๐mโ not supported. this could be caused by querying an item that only works in the active mode like a log monitoring item, or an item that requires multiple collected values. permission issues or incorrect user parameters could also result in the not supported state. sad girl hours, she's just not giving anything today ๐ญsโ text. maximum length not limited. no cap on length, literally none โจtโ text. same ass. twins fr fr ๐ฏuโ unsigned integer. whole numbers only, no decimals allowed, she's got boundaries ๐
-t,--testitem-key โ test a single item and exit. see--printfor output description. one item, one test, in and out, efficient queen โญ-T,--test-configโ validate configuration file and exit. a little vibe check on your config before you commit ๐-h,--helpโ display this help and exit. she's helping! ๐ซถ-V,--versionโ output version information and exit. tell me who you are, bestie ๐
๐ FILES ๐
/usr/local/etc/zabbix_agentd.confโ default location of Zabbix agent configuration file (if not modified during compile time). so if it's not where you expect, blame the compile step, not the agent ๐
๐ซ SEE ALSO ๐ซ
- Documentation
zabbix_get(1),zabbix_proxy(8),zabbix_sender(1),zabbix_server(8),zabbix_js(1),zabbix_agent2(8),zabbix_web_service(8)
the whole friend group, assembled ๐
and that's the page!! brought to you by Zabbix, dated 2022-01-06, and yes she is still serving looks in this manual section ๐
mwah, go monitor something, you got this ๐โจ๐
๐ฆ where this page comes from
- alpine 3.24: zabbix-doc 7.4.12-r2 ยท AGPL-3.0-only
- arch rolling: zabbix-agent 7.4.16-1 ยท GPL-2.0-only
- epel 10: zabbix7.0-agent 7.0.31-1.el10_3 ยท AGPL-3.0-only AND MIT AND GPL-2.0-or-later AND Zlib AND BSD-3-Clause AND BSD-2-Clause AND ISC
- epel 9: zabbix7.0-agent 7.0.31-1.el9 ยท AGPL-3.0-only AND MIT AND GPL-2.0-or-later AND Zlib AND BSD-3-Clause AND BSD-2-Clause AND ISC
- fedora 43: zabbix-agent 1:7.4.15-1.fc43
- fedora 43: zabbix-agent 1:7.4.16-1.fc43 ยท AGPL-3.0-only AND MIT AND GPL-2.0-or-later AND Zlib AND BSD-3-Clause AND BSD-2-Clause AND ISC
- fedora 43: zabbix-agent 1:7.4.2-1.fc43 ยท AGPL-3.0-only AND MIT AND GPL-2.0-or-later AND Zlib AND BSD-3-Clause AND BSD-2-Clause AND ISC
- fedora 44: zabbix-agent 1:7.4.15-1.fc44
- fedora 44: zabbix-agent 1:7.4.16-1.fc44 ยท AGPL-3.0-only AND MIT AND GPL-2.0-or-later AND Zlib AND BSD-3-Clause AND BSD-2-Clause AND ISC
- fedora 44: zabbix-agent 1:7.4.8-1.fc44 ยท AGPL-3.0-only AND MIT AND GPL-2.0-or-later AND Zlib AND BSD-3-Clause AND BSD-2-Clause AND ISC
- nixos 26.05: zabbix-agent 7.4.11
- nixpkgs unstable: zabbix-agent 7.4.16
- ๐ girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms