Amon - web application debugging and monitoring toolkit
21–30 of 31 posts
Re: Amon - web application debugging and monitoring toolkit
#22Re: Amon - web application debugging and monitoring toolkit
#23The installation and uninstallation scripts are idiotic, dangerous and clearly untested.
Re: Amon - web application debugging and monitoring toolkit
#24The installation and uninstallation scripts are idiotic, dangerous and clearly untested.
Re: Amon - web application debugging and monitoring toolkit
#25This 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). 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. My only thought is: why is this local to the machine I put it on? I'd rather have a central repo…
So, as you may see, there's a point for this.
Also, don't forget that all you want for the replication already exists. You can easily replicate the mongodb data to another machine or back it up and save it somewhere else periodically.
As for giving each machine a unique id, this is a cool idea, but this implies that you have enough resources to set up your own monitoring system to monitor multiple hosts. That implies that you can implement something redundant.
Re: Amon - web application debugging and monitoring toolkit
#26The installation and uninstallation scripts are idiotic, dangerous and clearly untested.
Would you care to elaborate?
First, it downloads and installs a non-checksummed i686 binary version of mongodb. This is outrageously anti-social and one should be embarrassed for releasing that. Ditto ez_setup and all that crap. This is 2011.
I'm only looking at the Debian script now, but it's littered with other bugs such as not calling update-rc.d for amon (it is called for amond). The suggestion to run "curl uninstall.amon.cx | sh" is particularly unsafe as the script has a Bash shebang and /bin/sh could be anything.
A glance at the rpm script suggests bugs fixed in one have not been copied over - for example, you use pgrep correctly in the debian script but in the rpm script you essentially do [ "$(ps aux | grep -c mongo)" = 1 ] which gives you completely the opposite result to what you want.
The uninstallation scripts are perhaps worse, riddled with typos ("/etc.init.d/amond", "torando", etc.) which demonstrate the code has never once been tested, deleting /usr/bin/mongo* even though you install it to /usr/local/ (and screw anyone who had their own version running), deleting any systemwide versions of jinja, and. It won't even uninstall on Darwin due to "[ "$(uname -s)" != "Darwin" ];". And you call "set +e" (a no-op as it's the default) so that if the site_packages shell expansion fails you try and delete "/jinja2", etc.
I'm going home now. This is just what I see on my first glance but I think I've seen enough, frankly.
Re: Amon - web application debugging and monitoring toolkit
#27Earlier quoted context omitted.
Would you care to elaborate?
Oh christ, where to even start.. First, it downloads and installs a non-checksummed i686 binary version of mongodb. This is outrageously anti-social and one should be embarrassed for releasing that. Ditto ez_setup and all that crap. This is 2011. I'm only looking at the Debian script now, but it's littered with other bugs such as not calling update-rc.d for amon (it is called for amond). The suggestion to run "curl u…
First, it downloads and installs a non-checksummed i686 binary version of mongodb. This is outrageously anti-social and one should be embarrassed for releasing that. Ditto ez_setup and all that crap. This is 2011.
Amon is language agnostic, so there is enourmous chance, that a person who has 0 python knowledge could use it. By default none of the Linux distributions out there have pip or easy_install, so I thats why I have to install it.
I'm only looking at the Debian script now, but it's littered with other bugs such as not calling update-rc.d for amon (it is called for amond)
That is for reason. Some people, especially on small VPS's prefer to keep their memory usage low, so that's why the web part is running on demand only.
It won't even uninstall on Darwin due to "[ "$(uname -s)" != "Darwin" ];"
It's not running on MacOS at all at the moment, that's still work in progress.
Re: Amon - web application debugging and monitoring toolkit
#28The installation and uninstallation scripts are idiotic, dangerous and clearly untested.
If you can help with advice, I will be more than happy to listen :)
I cannot judge the safety in general, but can you list a single reason for using the -f argument here? I'd bet that this is 'just in case' combined with muscle memory gone bad.
Re: Amon - web application debugging and monitoring toolkit
#29Earlier quoted context omitted.
If you can help with advice, I will be more than happy to listen :)
Just skimmed the scripts on my mobile and obviously I cannot claim to know the GP's thoughts, but one thing that stood out was a habit of using rm -rf a lot, sometimes with wildcard arguments or environment variables passed on. I cannot judge the safety in general, but can you list a single reason for using the -f argument here? I'd bet that this is 'just in case' combined with muscle memory gone bad.
Re: Amon - web application debugging and monitoring toolkit
#30Earlier quoted context omitted.
Would you care to elaborate?
Oh christ, where to even start.. First, it downloads and installs a non-checksummed i686 binary version of mongodb. This is outrageously anti-social and one should be embarrassed for releasing that. Ditto ez_setup and all that crap. This is 2011. I'm only looking at the Debian script now, but it's littered with other bugs such as not calling update-rc.d for amon (it is called for amond). The suggestion to run "curl u…