About Thumpr.org:

Hi, my name is Christopher Sebastian, and I created thumpr.org. I created it because I needed a simple, reliable, free way to monitor a bunch of different kinds of things:

  • I wanted to monitor the uptime of a bunch of computers... some of them behind NAT and firewall.
  • I needed to make sure my Cron jobs were running successfully (for backups, automatic report generation, etc).
  • Even more importantly, I wanted to know when my Cron jobs were NOT running, due to unexpected problems.
  • I also wanted to be able to keep track of items that I had to do periodically, like change my password at work.

I also had some restrictions, requirements, and obstacles to overcome:

  • I did not want to install ANY software on the client computers.
  • I had to run on a variety of operating systems and environments.
  • I needed something that could be used from the command line, but also something that could be used from C and Python code (without adding dependencies).
  • I wanted a centralized solution (so i didn't have to maintain and keep track of multiple).
  • Because many of my computers were behind NATs and firewalls, standard monitoring software (which usually connects to the target computer periodically to gather statistics) would not work. Instead, connections had to be initiated by the computers who were behind the firewalls.

Thumpr.org was developed as a single, simple solution for all of the above goals and requirments. All logging events are just HTTP requests initiated by the computers that need to be monitored. This approach is simple to do from any environment, whether it's Linux, Mac, iPhone, Windows, DOS, bash, C, Python, or NodeJS.

Another benefit to this approach is the fact that no system-specific information needs ever be exchanged. Instead, thumpr.org just uses some randomly-generated IDs to identify log events. Thus, there are no security issues created by this approach.