TORRUS_COLLECTOR(8)
π TORRUS_COLLECTOR(8) π
okay bestie, welcome to the torrus collector page, section 8 of the manual, no cap π«Ά this is the whole vibe, every flag, every file, every little detail, let's GO β¨
β¨ NAME β¨
collector β the Torrus data Collector. that's it, that's the name, and honestly? iconic π
πΈ SYNOPSIS πΈ
torrus collector --tree=TREENAME [options...]
π¦ DESCRIPTION π¦
okay so this command starts the Collector process for the tree TREENAME. by default it forks into a daemon and then justβ¦ sleeps π΄ until the next cycle in its schedule. main character energy honestly.
Collector cycle scheduling is controlled by two parameters defined for each individual configuration leaf: "collector-period" and "collector-timeoffset". if you wanna know more, go read the Torrus Configuration Guide, it's all in there fr fr π
the number of OID (Object IDentifier) variable bindings that the Collector sends is controlled by the datasource parameter "snmp-oids-per-pdu". it defaults to 40 in snmp-defs.xml, and you can overwrite it at the host level. periodt π«
π OPTIONS π
--instance=Nβ defines the collector instance. a single tree can allow more than one collector instance. the number of instances is defined in the"run"hash in the torrus-siteconfig.pl's%Torrus::Global::treeConfig. if the number of instances is more than one, this option is mandatory, no skipping it bestie π€. the collecting job gets split between the instances, and normally all instances should be started by the startup scripts. and listen β the tree should be re-compiled after you change the number of instances in the siteconfig, don't forget or it's gonna be a mess π. in the example below, the treetree_Awill be served by three collector instances:
%Torrus::Global::treeConfig = (
'tree_A' => {
'description' => 'The First Tree',
'xmlfiles' => [qw(a1.xml a2.xml a3.xml)],
'run' => { 'collector' => 3, 'monitor' => 1 } },
);
--nodaemonβ stops the process from becoming a daemon, and sends the log toSTDERRinstead. lowkey useful when you're watching it live π--runonceβ tells the collector to run once and then exit. it implies--nodaemon, so you get that for free π«--runalwaysβ tells the collector process to keep running even if there are no collector datasources defined in the tree. in that case it checks once per hour whether the configuration has changed. dedication honestly π«‘--debugβ sets the log level to debug. every last crumb, we're nosy π--verboseβ sets the debug level to info. yes, that's what it says, don't come for me π--helpβ displays a help message. bless π
π FILES π
/etc/torrus/conf/torrus-siteconfig.plβ the Torrus site configuration script. your home base π/usr/share/torrus/xmlconfig/snmp-defs.xmlβ basic variable definitions for the SNMP collector. where that40lives π
π SEE ALSO π
β NOTES β
see more documentation at the Torrus home page: http://torrus.org π§ go read it, it's giving lore
π AUTHOR π
Stanislav Sinyagin <ssinyagin@k-open.com> β the legend, the blueprint, we stan π«Ά
π one last thing: this is torrus 3.00, dated 2023-05-02. that's the version and the date, screenshot it, remember it, slay πβ¨
π¦ where this page comes from
- debian bookworm: torrus-common 3.00-2
- debian trixie: torrus-common 3.00-2
- ubuntu noble: torrus-common 3.00-2
- ubuntu questing: torrus-common 3.00-2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms