CRITICALVIEW.CGI(1)

πŸ’– CRITICALVIEW.CGI πŸ’–

okay bestie, so this is the manual page for criticalview.cgi β€” it lives in section 1 of the General Commands Manual and honestly? she's a little legend. sit down, grab a strawberry, let's get into it πŸ“βœ¨


✨ NAME ✨

criticalview.cgi β€” the Xymon Critical Systems view CGI. that's her. that's the whole vibe. πŸ‘‘


🌸 SYNOPSIS 🌸

criticalview.cgi

no args, no drama, she just is. periodt.


πŸ¦‹ DESCRIPTION πŸ¦‹

so criticalview.cgi gets invoked as a CGI script β€” and like, through the criticalview.sh CGI wrapper, okay? that's the whole entrance, the red carpet moment. πŸ’…

what she does: she takes all the current critical statuses and matches them up against the critical.cfg(5) file. then she generates the "Critical Systems" view. that's it. that's the job. no cap.


🌈 RELATION TO OLD CRITICAL PAGE 🌈

okay this is the glow-up section. this view is a replacement for the statically generated "critical" page that shipped in versions of Xymon prior to version 4.2. so old money, basically.

and yeah, the "critical" pages are still supported all the way through Xymon 4.x β€” no one's coming for them β€” but the recommendation is that You (capital-Y You, bestie) switch over to the newer Critical Systems view that this CGI gives you. it's giving upgrade era. 🫢


πŸ’… OPTIONS πŸ’…

  • --acklevel=NUMBER β€” sets the acknowledgment level for acknowledgments that get sent through the ackinfo.cgi(1) page. heads up tho: this can be overridden by the configuration of the ackinfo.cgi utility. so she says one thing, the config might say another. 😭
  • --tooltips β€” hides the host description inside a "tooltip", which means it only pops up when your mouse hovers over the hostname on the webpage. super lowkey. and the reason it slaps? it saves space on the display so there's way more room for the status columns. main character energy, minimal footprint. ✨
  • --hffile=PREFIX β€” defines the header/footer files used when building the webpage. the actual files it uses will be PREFIX_header and PREFIX_footer, and they live in the ~xymon/server/web/ directory. Default: critical.
  • --env=FILENAME β€” loads the environment defined in FILENAME before executing the CGI script. pre-game ritual, basically. 🌸
  • --area=NAME β€” loads environment variables for a specific area. NB: if you use this one, it must appear before any --env=FILENAME option. order matters, bestie, don't play yourself. πŸ™ˆ
  • --debug β€” enables debugging output. she starts telling you everything. πŸ›
  • --config=FILENAME β€” use FILENAME as the configuration file for the Critical Systems information. the default is to load this from $XYMONHOME/etc/critical.cfg.
  • --config=ID:FILENAME β€” allows the use of multiple Critical Systems configuration files on a single webpage. "ID" is a text that will be shown on the web page prior to the critical systems from FILENAME. and the fun part: this option can be repeated to include critical systems from multiple configurations. stacking them like bracelets. πŸŽ€

🧚 ENVIRONMENT VARIABLES 🧚

  • XYMONHOME β€” used to locate the template files for the generated web pages. she needs to know where home is. relatable.
  • QUERY_STRING β€” contains the parameters for the CGI script. the receipts, basically. πŸ’œ

πŸ‘‘ SEE ALSO πŸ‘‘

ackinfo.cgi(1), xymon(7)


okay that's the whole page, go forth and be critical (systems view). πŸ”₯

signed, sealed, delivered: this page is brought to you by Xymon, Version 4.3.30, dated 4 Sep 2019 β€” mwah, love that for us πŸ’–πŸ’«

πŸ“¦ where this page comes from