APPFEED.CGI(1)
π appfeed.cgi(1) from the General Commands Manual π
okay bestie, this is the manual page for appfeed.cgi(1) and it has MAIN CHARACTER energy π
let's get into it β¨
β¨ NAME β¨
appfeed.cgi - Xymon CGI feeder for Smartphone apps π± it's the thing that hands Xymon status data over to phone apps π¦
β¨ SYNOPSIS β¨
appfeed.cgi [options]
that's the whole synopsis, just the one line, no cap π
β¨ DESCRIPTION β¨
okay so appfeed.cgi gets invoked as a CGI script through the appfeed.sh CGI wrapper π§
it can optionally take a QUERY_STRING environment variable with the filter=FILTER parameter in it. FILTER is a filter for the xymondboard command that gets sent to the xymond(8) daemon π these filters are explained in full detail in the xymon(1) manual, so go check that if you want the deep dive π€ usually the filter picks out hosts on one specific (sub)page. for example, filter=page=webservers makes appfeed.cgi only return the hosts that show up on the "webservers" page in Xymon πΈ
if you don't give it a filter, appfeed.cgi returns data for all the red, yellow or purple statuses. that's the same stuff you'd see on the "All non-green" page π₯ but if you run it with the --critical option, it gives you data from the "Critical systems" page instead β
the output is an XML document with the current status of whichever hosts and services got selected π«Ά
β¨ OPTIONS β¨
--env=FILENAMEβ loads the environment fromFILENAMEbefore the CGI runs π--critical[=FILENAME]βFILENAMEis the "Critical Systems" configuration file, and if you don't pick one it defaults tocritical.cfgπappfeed.cgiwill only return the statuses that are currently on the "Critical Systems" view π--access=FILENAMEβ on top of whatever filtering thefilterparameter or the--criticaloption is doing, this one limits the output to only the hosts the user has access to. that access comes from the Apache-compatible group-definitions inFILENAME. seexymon-webaccess(5)for more on that π¦
β οΈ bestie, read this part! using--accessmeans access to theappfeed.cgitool has to be password-protected by whatever your webserver software offers. the login userid also has to be available through theREMOTE_USERenvironment variable. the good news is this is standard CGI behaviour, so every webserver should provide it if you're using its built-in authentication π
β¨ SEE ALSO β¨
xymon(1), critical.cfg(5), xymon-webaccess(5) π
and that's a wrap, bestie π«Ά this page is from Xymon version 4.3.30, dated 4 Sep 2019, so it's giving vintage charm π periodt β¨π
π¦ 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 claude-haiku-5-5 on : a language model's rewrite of the original, under its terms