Scout is going to AWS re:Invent!

By Mark Bullet_white Comments Comments


Find us in Booth #1130 at AWS re:Invent. Be sure to stop in - meet the team, and rub Dave’s head for good luck!


Schedule a Meeting with a Scout Founder

Derek (CEO) and Andre (CTO) would love to meet with you in Vegas. Contact me and I'll schedule a time.

See our new product: app monitoring

We're launching our second product, a perfect complement to server monitoring: application monitoring.

Yes - we're taking on New Relic. We're going to be your fastest path from performance nightmare to a line-of-code: we'll be the first git-integrated app monitoring out there.

Sign up for early access!

Win an Oculus Rift when you deploy Scout APM during aws:reInvent!


StackProf: The Holy Grail of Rails Profiling

By Mark Bullet_white Posted in App Monitoring Bullet_white Comments Comments


The holy grail of performance profiling is finding a tool that's safe to run in production. A tool that identifies slow code as it works "in the wild".

Profiling code locally is never as good as production profiling: the load is small, hardware specs are different, and I'd need to pull down a huge chunk of data to simulate things.

Enter StackProf, the production safe*, holy grail of Ruby profiling tools.

Read More →


Heading to the mountains

By Derek Bullet_white Comments Comments

grand lake

There's no better place for big thinking than the mountains.

Just a short time ago, Scout was myself and Andre. Today, we're a fun, smart team of seven (and growing).

We've got grand plans for the future of Scout (we'll be debuting those @ aws:reinvent) and we're hunkering down in Grand Lake, Colorado working on the next exciting phase of Scout.

Expect a full report later on what we're working on...


StatsD. Build vs. Buy?

By Mark Bullet_white Posted in Business Bullet_white Comments Comments


"Remember that time is money."

A phrase used by Benjamin Franklin in Advice to a young Tradesman, written by an old One. Sage advice - and even after all these years, still relevant!

It's no surprise that we all look for tools that make our jobs easier, deliver value for our customers -- and ultimately save us time.

StatsD is one of those tools.

In a recent conversation with Martin Kelly, we talked about StatsD and how it saved him time.

Here's what he had to say:

"We don’t use StatsD for in-app instrumentation, but for user experience tracking. The client will ask us to measure a discrete element of the user experience, and with a couple lines of Python we can put together a test and start tracking it and graphing it within minutes."

Furthermore, he talked about the importance of dashboards and how visualizing the data helped him:

"In combination with the really quick-to-assemble dashboards in Scout, it allows us to see what system components are potentially affecting user experience, which does two things: lets us narrow down our diagnostic root through trivially easy correlation really quickly, and gives us much more user centered data for our capacity planning."

I asked him about the tools he was using before StatsD:

"We had a lot of Python tools already doing that job, but reworking the entire suite to work with StatsD was trivial. An hour from start to finish."

Summing up:

"Yes, I could probably cook something up similarly with Graphite, Fluentd, Sensu, Statsd and other parts, but the value for us is all that work is done. The cost for the offering over the whole estate is less than the engineering cost to maintain a pieced together solution."

A big THANKS to Martin for sharing his feedback. Internally, we've had the same experience with StatsD: Minimal setup and quick payback.

If you haven't tried StatsD yet, here's a few resources to get you started:

StatsD Intro Video

Docker Event Monitoring from scratch with StatsD

Scout StatsD Rack Gem

Give StatsD a try today! If you have any questions, contact us here, or follow us on Twitter for more StatsD news.


Monitoring InfluxDB with Scout

By Derek Bullet_white Posted in App Monitoring Bullet_white Comments Comments

We're using InfluxDB in our new app monitoring service.

While InfluxDB hasn't reached 1.0 yet, it has loads of potential and has been holding up well during our BETA period. Don't worry, we'll talk more about InfluxDB in coming posts.

So, how are monitoring InfluxDB performance? Here's how we get an overview of our app performance. InfluxDB is one of the categories we track:


When there's a slow request, we can dig into details, including viewing the actual InfluxDB query:


Need some InfluxDB monitoring action?

Sign up for early access and ping us at to let us know you are using InfluxDB.


Introducing easy StatsD with Scout

By Mark Bullet_white Comments Comments

The easiest way to unleash StatsD.

One agent. Minimal overhead. Robust language support. A unified monitoring solution for your servers and metrics.

We've added StatsD support to our monitoring agent. With Scout, you are just minutes away from StatsD-backed charts and alerts. Use StatsD to report code execution times, user signup rates, and more.

StatsD generated metrics are first class citizens in Scout - coexisting with every metric available via Scout.

Don't just take our word for it, Scout customer Martin Kelly had this to say:

It took about an hour to get all of our prod and preprod custom metrics into Scout and displayed on our dashboard. Both the client and project manager were very happy!"

Why StatsD + Scout?

Prior to today, all metrics in Scout were generated by our agent (monitoring system resource usage) or plugins (monitoring services). This works great for sampling metrics, but it's not a great fit for event-based metrics (ex: tracking user signups, response times, etc).

StatsD is a great fit for event-based metrics, but rolling your production-grade setup for StatsD is involved. We also want to see all of our metrics (and configure alerting) from a single app.

We tested StatsD+Scout internally first, loved it, and rolled out to customers during a preview stage. Today, StatsD is battle-tested and ready for your metrics.

Quick tip: replacing metric logging with StatsD

First time with StatsD? Here's a tip: if you are logging a metric, it probably makes more sense to send it StatsD.


logger.warn "Error Occurred!"



...which gives you ready-to-go charts and alerting (ex: alert when the error rate exceeds 50 errors/min).

Get started with StatsD today!

Additional resources to get you started:

Questions? Comments? Contact us at

More updates on StatsD? Follow us on Twitter.


Older posts: 1 ... 3 4 5 6 7 ... 57