Scout Blog

Stuff we think matters

February Newsletter

A quick look at what we've been up to for the past few months, including support for Ruby 4, improved Python support for errors, and strengthened reliability enhancements product-wide.

Already Love Scout APM? We Have Integrated Error Monitoring!

Error monitoring is now fully integrated with APM, with errors, traces, and logs in one interface. When an error spikes, you can immediately see if it correlates with a performance regression, drill into the trace, and find the problematic code without switching tools or piecing together data from multiple sources. Scout treats errors like first-class citizens, not an afterthought. This means that the integration depth and actionability is different than other tools: in Scout, errors and traces live in the same view by design, not as bolt-on features.

How a Singleton Pattern Broke Our Django Logging

When wrapping resources in Singleton objects, understanding the lifecycle behavior of both the underlying resource and the calling code is key. Django loves to close logging handlers frequently during its boot cycle. Debugging log handlers is its own special kind of fun; read on for the schadenfreude.

Application Monitoring 101: Queue Time Can Alert Before a Breakdown

Regular monitoring practices can emphasize application response time, but queue time is also often an early and important warning sign. If it rises, you’ll quickly see downstream effects: tail latency, timeouts, and error spikes. This means that this metric can give you a head start tackling app issues before they become user problems. In this post, we’ll discuss queue time, how things can go off track, and practical steps to turn it around.