On Mon, Oct 21, 2013 at 8:58 PM, Lars Yencken <[email protected]> wrote: > I can second NewRelic. We've used it for some time at work, and it's > definitely the strongest performance monitoring tool that I've used. > Recently I used their free tier for my language game in Flask, and it's > again been useful. The 24h limit to history does prevent you from > investigating performance over time though -- for that you have to pay.
I've also been looking at open source solutions in this space, like collectd, ganglia, nagios, cacti, but it seems they overlap a bit, and at the same time they leave out a lot of the error monitoring that the likes of New Relic give you. I'll report back when I get a better idea. > We use Github, but Bitbucket's more reasonably priced. It's what I use for > my personal projects. The workflow around pull requests is probably not as > strong for teams though. Can you give an example? Besides the fact that pull requests don't create an issue (which may even be better for some people, I'm agnostic on the point), I can't see much difference. J _______________________________________________ melbourne-pug mailing list [email protected] https://mail.python.org/mailman/listinfo/melbourne-pug
