This is the second or third time I've seen a service like this created (getexceptional.com and airbrake.io are two that come to mind quickly).<p>I can only hope this trend continues and in an open-architecture style. The ability to basically develop a skeleton monitoring UI that I can plug my own software into is fantastic.<p>My only thought is: why is this local to the machine I put it on? I'd rather have a central repository that I send me data to, like getexceptional. I don't mind having to set-up the process for each server I spin up, but I would prefer it if the information all aggregated to one source that I could browse through.<p>What I sort of imagine is registering for an Amon account and getting a unique key and identifier. Whenever I install Amon on a machine or want to call it from my code, I use that unique key and give the hardware a unique name and register my software service (pulling the hardware name from some config file automatically). Then, when I log into my central Amon account, I can browse through my exceptions and hardware details by machine name or software service.<p>Give me the ability to have multiple logging levels and I am in heaven.<p>Take it one step further: let fall-back be to either a local db or file-system and have a cron-job go through to try to fulfill the upload tasks.<p>That is definitely something I would pay $25-$50 a month for.
Looks awesome.<p>I will try to deploy this on Heroku and see how it compares to my django-sentry [<a href="https://github.com/dcramer/django-sentry" rel="nofollow">https://github.com/dcramer/django-sentry</a>] installation.
Looks very promising - I can't help wonder how you can spend time building a quality product like this, then release it for free : is there a monetization strategy at some point (i.e : pro support) ?
I especially like the logging feature. Haven't had the chance to look at the code yet but how tightly coupled to mongodb is this? Would it be relatively easy to replace the store with redis?