DMON - Distributed MONitoring

dmon - what it is

• dmon monitors the state of a collection of hosts.
• Each host runs a dmon daemon
  • the daemon collects local data,
  • the data is stored in a local (sqlite) database,
  • the daemon answers database queries.
• On one host, the daemon also acts as a server.
  • The server collects (only) the current data of the clients.
• One host has a cgi script that generates the web pages
  • The cgi script gets the current data from the server
  • The cgi script queries the clients for historic data

dmon - what it does

• For a summary, see the dmon manual page ; section description.
• Dmon is managed with a single work-config file.
• Each client is managed by a work-file, generated by mk-dmon-work from the work-config file.
• Dmon is distributed in the sense that :
  • each client runs on its own checks ; there is no central (work)flow-control
  • each client keeps its own history in a local (sqlite) database
  • each client can talk to the server ; the server can talk to each client ; all connections are short-lived.

dmon - example

• See our dmon pages [access is restricted]
• See our work-config, and the generated work-files → server, clients [access is restricted]

dmon - documentation, source

• man pages : dmon - mk-dmon-work - gen-dmon-page - plotter.php - users-dmon
• source : archive.cs.uu.nl/PERL/dmon-dev/
• download : rsync rsync.science.uu.nl::dmon-dev/ your/path/

dmon - misc

• the wiki page{access is retricted}
• the dist directory
• the upgrade directory