Opbeat Blog

Great trick. Incredible that it's not on by default. if you've applied that trick and still find yourself wondering what's taking up time, we just released a performance monitoring tool. We're looking for feedback, so please let me know how you find it: https://opbeat.com/angularjs

I've used https://opbeat.com/ for a small side project and been fairly happy - they track exceptions, releases and performance.

Also, there is Opbeat (https://opbeat.com), which also does release/deploy tracking (you can see which errors come from/after which release).

I found these tools mentioned by the author really helpful, I compiled a list of them: http://jinja.pocoo.org/ https://www.getsentry.com/welcome/ http://graphite.wikidot.com/start https://opbeat.com/ is there a way though to use/test opbeat ?

I just founded my third startup Elastic Byte (https://elasticbyte.net), which is a DevOps and infrastructure consulting company operating as SaaS (public monthly pricing plans). Indeed culture is a big part of the DevOps puzzle besides software. This mentality shift is also a part of what we offer (training and advice). Individual ownership, moving fast, are all parts of the greater strategy. I've found the talk "You shipped it, you fix it" [1] by Ron Cohen (CTO of Opbeat) a great source of solid ideas. https://opbeat.com/community/posts/you-shipped-it-you-fix-it-by-ron-co… The old model where developers hand off their code to the ops department is fundamentally a bad strategy because it leads to: "It worked fine in test... Ops problem now!" There is no accountability. If your code causes problems when deployed to production, ops is the one getting a call/page in the middle of the night, and trying to fix the problem for which they have no domain experience or understanding. However, if you deploy your own code at your own pace, then there is accountability.

One of our users open sourced a PHP integration he made to our API. But it only supports error monitoring unfortunately. Not our performance monitoring: https://opbeat.com/docs/articles/error-logging-in-php/

Here are some SaaS choices: * Sentry: https://sentry.io/welcome/ * Logentries: https://logentries.com/ * Loggly: https://www.loggly.com/ * Opbeat: https://opbeat.com/ * Papertrail: https://papertrailapp.com/ Sentry is open source and there is even an official up-to-date docker image: https://hub.docker.com/_/sentry/ Loggly published an "Ultimate Guide to Logging": https://www.loggly.com/ultimate-guide/

The Django community knows full well that this is a missing feature in modern web development. There was a talk featuring this topic at DUTH this fall. https://opbeat.com/events/duth/#twisted-and-django

I can't say I've used twisted at all, but Amber had a fairly good talk at Django Under the Hood this year on this topic: https://opbeat.com/events/duth/#twisted-and-django