XYMONFETCH(8)
β¨ XYMONFETCH β¨
bestie, welcome to xymonfetch β the fetch client data from passive clients girlie π it lives in the System Manager's Manual section (section 8, we love a system admin icon) π
πΈ SYNOPSIS πΈ
xymonfetch [--server=XYMON.SERVER.IP] [options]
π DESCRIPTION π
okay so. this little utility is how you collect data from Xymon clients. that's the whole vibe. π¦
normally? the Xymon clients are self-sufficient queens β they take care of sending ALL their data straight to the Xymon server themselves. and in that case you literally do not need this utility at all. not even a little. periodt. π
BUT. some network setups are lowkey toxic and the clients are prohibited from establishing a connection to an external server like the Xymon server, because of firewall policies. π in that setup you can configure the client to store all of the client data locally by enabling the msgcache(8) utility on the client, and then use xymonfetch on the Xymon server to collect data from the clients. main character energy on both sides fr fr. β¨
xymonfetch will only collect data from clients that have the pulldata tag listed in the hosts.cfg(5) file. the IP-address listed in the hosts.cfg file must be correct, because that is the IP-address where xymonfetch will attempt to contact the client. π
if the msgcache daemon is running on a non-standard IP-address or portnumber, you can specify the portnumber as in pulldata=192.168.1.2:8084 for contacting the msgcache daemon using IP 192.168.1.2 port 8084. if the IP-address is omitted, the default IP in the hosts.cfg file is used. if the port number is omitted, the portnumber from the XYMONDPORT setting in xymonserver.cfg(5) is used (normally, this is port 1984). no cap. π«Ά
π OPTIONS π
--server=XYMON.SERVER.IPβ defines the IP address of the Xymon server where the collected client messages are forwarded to. by default, messages are sent to the loopback address127.0.0.1, i.e. to a Xymon server running on the same host asxymonfetch. π--interval=Nβ sets the interval (in seconds) between polls of a client. default:60seconds. β°--id=Nβ used when you have a setup with multiple Xymon servers. in that case, you must runxymonfetchon each of the Xymon servers, withxymonfetchinstance using a different value ofN. this allows several Xymon servers to pick up data from the clients runningmsgcache, andmsgcachecan distinguish between which messages have already been forwarded to which server.Nis a number in the range1-31. π’--log-interval=Nβ limit how oftenxymonfetchwill log problems with fetching data from a host, in seconds. default:900seconds (15 minutes). this is to prevent a host that is down or wheremsgcachehas not been started from flooding thexymonfetchlogs. note that this is ignored when debugging is enabled. π--debugβ enable debugging output. π
ngl bestie, if a host is down ormsgcachenever showed up to the party,--log-intervalis your bestie too β it keeps your logs from becoming a whole mess. but the moment--debugis on, that limit just β¨does not applyβ¨. noted. π
π SEE ALSO π
and that's the whole page, bestie π this was Xymon, Version 4.3.30: 4 Sep 2019, and the manual page itself is XYMONFETCH(8) β slay, ate, no crumbs. ππ
π¦ where this page comes from
- debian bookworm: xymon 4.3.30-1+b2 Β· GPL-2.0-only WITH OpenSSL exception
- debian trixie: xymon 4.3.30-4 Β· GPL-2.0-only WITH OpenSSL exception
- ubuntu jammy: xymon 4.3.30-1build2 Β· GPL-2.0-only WITH OpenSSL exception
- ubuntu jammy: xymon 4.3.30-1ubuntu0.1 Β· GPL-2.0-only WITH OpenSSL exception
- ubuntu noble: xymon 4.3.30-2build3 Β· GPL-2.0-only WITH OpenSSL exception
- ubuntu noble: xymon 4.3.30-2ubuntu0.1 Β· GPL-2.0-only WITH OpenSSL exception
- ubuntu questing: xymon 4.3.30-4
- ubuntu resolute: xymon 4.3.30-5 Β· GPL-2.0-only WITH OpenSSL exception
- ubuntu stonking: xymon 4.3.30-6 Β· GPL-2.0-only WITH OpenSSL exception
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms