The way I monitor the server now is a mess. Recently the processor broke because a file was missing from githubarchive.org. Normally the server emails me every hour telling me the results of the archive-processor run, and separately it emails me if it realizes that the latest event is more than a couple hours old, but at some point it stopped doing that because I chmod'd the ssmtp.conf wrong, and the logs on the disk aren't something I look at regularly until I realize something's wrong.
So I need to look into alternatives and implement one of them. Requirements:
Free (at least for this usage)
Easy to post arbitrary events through an API
Python and Go libraries (preferably drop-in replacements for the standard logger)
Must have a command line utility to post these events, preferably one with no dependencies
hut8
commented
8 years ago
The way I monitor the server now is a mess. Recently the processor broke because a file was missing from githubarchive.org. Normally the server emails me every hour telling me the results of the
archive-processorrun, and separately it emails me if it realizes that the latest event is more than a couple hours old, but at some point it stopped doing that because I chmod'd the ssmtp.conf wrong, and the logs on the disk aren't something I look at regularly until I realize something's wrong.So I need to look into alternatives and implement one of them. Requirements: