XYNAGIOS(1)

πŸ“¦
version 20230301build1 Β· 3 versions
, in ubuntu resolute, ubuntu stonking

πŸ’– XYNAGIOS πŸ’–

okay bestie, gather round, because we're talking about xynagios β€” that's the little Perl bestie from the User Contributed Perl Documentation section of your manual, and she is literally the glue holding your Nagios checks and your Xymon dashboard together. no cap. 🫢


✨ NAME ✨

xynagios β€” an adaptor for using Nagios checks with Xymon. it's giving "translator bestie" and honestly? iconic. πŸ‘‘


🌸 SYNOPSIS 🌸

xynagios [options --] plugin [options ...]

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the vibe: xynagios runs a Nagios check, and then reports its output in a way that's compatible with the Xymon (Hobbit, BB) monitoring system. yes, all three names, because this ecosystem has history, and we respect it. πŸ’…

Now, the test name β€” this is the part everyone asks about. The Xymon test name is taken from the plugin output if it starts with test_name OK|WARNING|CRITICAL|ERROR|UNKNOWN:. Otherwise, the basename of the plugin filename is used. And a check_ prefix gets removed for brevity, because we're not about that verbose life. ✨


πŸ’… OPTIONS πŸ’…

  • --hostname=host β€” report tests as this host. like, "whose vibes are these? this host's vibes." 🏠
  • --strip=prefix β€” remove prefix (a regexp) from test names. heads up: the prefix check_ is always removed before stripping other prefixes. super useful for trimming down overly verbose Nagios test names, e.g. check_postgres_database_size becomes database_size. glow-up fr fr. βœ‚οΈ
  • --test=name β€” the test name to submit. per default, the test name is derived from the plugin output, or from the plugin name if the output doesn't indicate the name. main character naming rights, basically. πŸŽ€
  • --help, --version β€” print help text and version, and exit. the classic "hi and bye." πŸ‘‹

bestie, listen: if any of these is set, a data host.trends message is sent. any. one. of. them. πŸ’€

  • --trends β€” in addition to printing performance data in the status report (suitable for the NCV/SPLITNCV xymond_rrd modules), send in a data report for hostname.trends. this rrd module is more robust. it's the upgraded version, no notes. πŸ’ͺ
  • --ds=name β€” the data source (DS) name used in the RRD files. defaults to lambda. πŸ“
  • --dst=type β€” the data source type used in the RRD files. useful values are GAUGE (the default), COUNTER, DCOUNTER, DERIVE, DDERIVE, and ABSOLUTE. see rrdcreate(1) for details, iykyk. πŸ“Š
  • --heartbeat=secs β€” RRD heartbeat in seconds, default is 600. that's ten whole minutes of heartbeat, we love a steady pulse. πŸ’“
  • --min=N β€” data source minimum value, default is U for unknown. we simply do not know. πŸ™ˆ
  • --max=N β€” data source maximum value, default is U for unknown. same energy, other end of the scale. πŸ™ˆ

🌈 SEE ALSO 🌈

xymon(7), xymon(1), xymoncmd(1), nagios3(8). go read the whole friend group. πŸ“š


πŸ‘‘ AUTHOR πŸ‘‘

Christoph Berg <myon@debian.org> β€” the legend who wrote this. respect. 🫑


Copyright (c) Christoph Berg <myon@debian.org>

okay so legal bestie says: redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

and that's the whole page, babe. this one came to you courtesy of perl v5.40.1, dated 2025-12-11, and it's filed under XYNAGIOS(1) in your friendly neighborhood manual pages. stay monitored, stay slay. πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from