EVENTLOG.CGI(1)

💖 eventlog.cgi(1) 💖

okay bestie, gather round, because we're talking about eventlog.cgi — the CGI program that reports the Xymon eventlog, and honestly? it's giving receipts. it's giving "who touched what and when". periodt.

✨ NAME ✨

eventlog.cgi — a CGI program that reports the Xymon eventlog. that's it, that's the whole job, and it does it flawlessly 💅

🌸 SYNOPSIS 🌸

eventlog.cgi

no flags, no drama, no arguments. it just arrives. main character energy fr fr.

🦋 DESCRIPTION 🦋

so here's the tea, bestie: eventlog.cgi gets invoked as a CGI script through the eventlog.sh CGI wrapper. (yes, there's a wrapper. it's the little fairy godmother 🧚 that makes the magic happen.)

based on the parameters it receives, it generates the Xymon event log for a period. and what does that log show? all status changes that have occurred for all hosts and services. every single one. no skipping. no cap. it's the group chat scrollback of your infrastructure 😭

now — the important part. eventlog.cgi is passed a QUERY_STRING environment variable, and that string carries these parameters:

• MAXTIME — maximum minutes to go back in the log ⏪ (how far back in time we're scrolling, bestie)
• MAXCOUNT — maximum number of events to report 🔢 (because sometimes you need to cap the yapping)

that's the whole menu. two params, infinite peace of mind 🫶

💅 OPTIONS 💅

• --env=FILENAME — loads the environment defined in FILENAME before executing the CGI script. basically it's like, "hey, read this file first so we're all on the same vibe" ✨

👑 SEE ALSO 👑

• hosts.cfg(5)
• xymonserver.cfg(5)

go read those too, they're iconic in their own right 🌈

ok real talk for one sec: everything above is exactly what the page says — same parameters, same option, same files. I'm just delivering it with ✨flair✨. don't come for me, come for the docs 💖

and that's the whole page, bestie!! Xymon, Version 4.3.30, dated 4 Sep 2019 — shoutout to the Xymon girlies for keeping the eventlog lore alive. slay, bye 💜🎀🦋