ZABBIX_AGENT2(8)

📦
version 7.4.16 · 4 versions
, in arch rolling

✨ NAME ✨

Okay bestie, this is zabbix_agent2 — literally Zabbix agent 2. The manual page name is ZABBIX_AGENT2(8), straight from the System Manager's Manual. 🩷

🌸 SYNOPSIS 🌸

zabbix_agent2 [-c config-file]
zabbix_agent2 [-c config-file] [-v] -p
zabbix_agent2 [-c config-file] [-v] -t item-key
zabbix_agent2 [-c config-file] -R runtime-option [parameters...]
zabbix_agent2 [-c config-file] -T
zabbix_agent2 -h
zabbix_agent2 -V

🦋 DESCRIPTION 🦋

zabbix_agent2 is an application for monitoring parameters of various services. That's the whole main-character job, no cap. 💅

💅 OPTIONS 💅

  • -c, --config config-file — Use the alternate config-file instead of the default one. Custom config? Obsessed. Periodt.
  • -R, --runtime-control runtime-option [parameters...] — Perform administrative functions according to runtime-option and any parameters it accepts. It's giving admin mode.

🛠️ Runtime control options 🛠️

These are the runtime-option values -R takes, and yes, they're iconic:

  • userparameter_reload — Reload user parameters from the configuration file.
  • periodic_prof_enable — Enable periodic profiling.

Periodic CPU data is collected into a hidden temporary file. When an interval ends, the file is published as a CPU profile and the configured number of completed files is retained. The temporary file does not count toward ProfilerMaxFilesPerProfile.

  • periodic_prof_disable — Disable periodic profiling.
  • periodic_prof_execute — Write profiles after a 5-second sample.

When periodic profiling is enabled, this command finishes the current CPU interval, writes a separate 5-second CPU profile, and starts a new periodic CPU file. Explicitly requested profiles are rotated according to ProfilerMaxFilesPerProfile when the command completes. While this command is collecting profiles, all profiler runtime commands are rejected with "profiler is busy".

  • periodic_prof_set_interval seconds — Set profiling interval.
  • log_level_increase — Increase log level.
  • log_level_decrease — Decrease log level.
  • help — List available runtime control options.
  • metrics — List available metrics.
  • version — Display version.
  • -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 always t, as the agent can not determine all possible return values. Items, displayed as working, are not guaranteed to work from the Zabbix server or zabbix_get when querying a running agent daemon as permissions or environment may be different. Returned value types are:
    • d — Number with a decimal part.
    • 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.
    • s — Text. Maximum length not limited.
    • t — Text. Same as s.
    • u — Unsigned integer.
  • -t, --test item-key — Test single item and exit. See --print for output description.
  • -v, --verbose — Enable verbose output when test item or print known items.
  • -T, --test-config — Validate configuration file and exit.
  • -h, --help — Display this help and exit.
  • -V, --version — Output version information and exit.

🍓 FILES 🍓

  • /usr/local/etc/zabbix_agent2.conf — Default location of Zabbix agent 2 configuration file (if not modified during compile time).

👑 SEE ALSO 👑

Okay bestie, that's the whole vibe. 💖 This page comes from Zabbix, dated 2022-01-06, and it lives under ZABBIX_AGENT2(8). Go be iconic with your monitoring. 💅✨

📦 where this page comes from