CF-MONITORD(8)

πŸ“¦
version 3.24.1 Β· 2 versions
, in debian trixie

πŸ’– CF-MONITORD(8) πŸ’–

okay bestie, so this is cf-monitord, and it lives in section 8 of the System Manager's Manual β€” that's the club for daemons and system admin stuff, iykyk. She's the monitoring daemon for CFEngine and honestly? she's the quiet main character keeping watch while everyone else does their thing. πŸ¦‹


✨ NAME ✨

cf-monitord β€” the monitoring daemon for CFEngine πŸ‘‘


✨ SYNOPSIS ✨

cf-monitord [OPTION]...  [FILE]

✨ DESCRIPTION ✨

so like, cf-monitord is the monitoring daemon for CFEngine. she samples the probes that are defined in policy code, and she also tries to learn what "normal" looks like for your system based on what she's seeing right now plus everything she's seen before. lowkey a genius. 🧠✨

her current estimates get made available as special variables β€” for example $(mon.av_cpu) β€” and then cf-agent can read those and use them to inform policy decisions. it's giving teamwork, it's giving besties supporting besties. 🫢


✨ OPTIONS ✨

  • --help, -h β€” prints the help message. classic. when in doubt, ask for help, no shame in it πŸ’…
  • --debug, -d β€” turns on debugging output, so you can see all the messy behind-the-scenes lore πŸ”
  • --verbose, -v β€” outputs verbose information about how cf-monitord is behaving. she will tell you everything. she's an oversharer and we love that πŸ—£οΈ
  • --dry-run, -n β€” all talk and no action mode: makes no changes at all, and only tells you about promises that weren't kept. zero commitment, all vibes πŸ™ˆ
  • --version, -V β€” outputs the version of the software. know your era ✨
  • --no-lock, -K β€” ignore the system lock. (yes bestie, she's gonna just walk right past the lock like it's not even there πŸ’€)
  • --file, -f _value_ β€” specify an alternative input file instead of the default one. but heads up: this option gets overridden by FILE if FILE is supplied as an argument. so the argument wins, periodt.
  • --log-level, -g _value_ β€” specify how detailed the logs should be. possible values: 'error', 'warning', 'notice', 'info', 'verbose', 'debug' β€” pick your level of detail, like choosing how much of the story you wanna hear πŸ“œ
  • --inform, -I β€” prints basic info about changes made to the system, i.e. promises that got repaired πŸ› οΈ
  • --diagnostic, -x β€” activates internal diagnostics. developers only, so if that's not you, respectfully step back 🚧
  • --no-fork, -F β€” runs the process in the foreground instead of as a daemon. no hiding in the background, she's right there in front of you πŸ‘€
  • --histograms, -H β€” ignored, kept around for backward compatibility. she's just there for the nostalgia πŸ•°οΈ
  • --tcpdump, -T β€” interfaces with tcpdump if it's available, to collect data about the network πŸ“‘
  • --color, -C _value_ β€” enables colorized output. possible values: 'always', 'auto', 'never'. and if you use the option, the default value is 'auto' 🎨🌈
  • --timestamp, -l β€” logs timestamps on each line of log output. receipts, with times ⏰
  • --ignore-preferred-augments, - β€” ignores the def_preferred.json file in favor of def.json. choosing the main character file, iconic behavior πŸ‘‘

✨ CFENGINE ✨

CFEngine provides automated configuration management of large-scale computer systems. a system administrator describes the desired state of a system using CFEngine policy code. the program cf-agent reads that policy code and attempts to bring the current system state to the desired state described. πŸ“

policy code is downloaded by cf-agent from a cf-serverd daemon. and the daemon cf-execd is the one responsible for running cf-agent periodically. whole little ecosystem, everyone has a job πŸ’–

documentation for CFEngine is available at https://docs.cfengine.com/.


✨ PROMISE THEORY ✨

CFEngine is built on principles from promise theory, proposed by Mark Burgess in 2004. promise theory is a model of voluntary cooperation between individual, autonomous actors or agents who publish their intentions to one another in the form of promises. 🫱🫲

a promise is a declaration of intent whose purpose is to increase the recipient's certainty about a claim of past, present or future behaviour. for a promise to increase certainty, the recipient needs to trust the promiser β€” but trust can also be built on the verification that previous promises have been kept, so trust plays a symbiotic relationship with promises. it's literally a situationship built on reliability, fr fr πŸ’ž

for an introduction to promise theory, please see http://arxiv.org/abs/0810.3294/


✨ AVAILABILITY ✨

cf-monitord is part of CFEngine. πŸŽ€

binary packages may be downloaded from https://cfengine.com/download/.

the source code is available at https://github.com/cfengine/ ⭐


✨ BUGS ✨

please see the public bug-tracker at https://northerntech.atlassian.net/projects/CFE/.

GitHub pull-requests may be submitted to https://github.com/cfengine/core/. πŸ›πŸ’…


✨ SEE ALSO ✨

cf-promises(8), cf-agent(8), cf-serverd(8), cf-execd(8), cf-monitord(8), cf-runagent(8), cf-key(8)

(yes she's in her own SEE ALSO list. self-love, we stan πŸ‘‘)


✨ AUTHOR ✨

Mark Burgess and Northern.tech AS 🫢


ok that's the whole page bestie, no cap, nothing skipped πŸ’–

and for the cute sign-off: this lil page comes to you from the System Administration corner of the CFEngine manual, filed under CF-MONITORD(8) β€” go be a monitoring main character πŸ¦‹βœ¨πŸŽ€

πŸ“¦ where this page comes from