Auto-instrumentation sounds like a free lunch - press buttons, get signals - but nothing is truly free. Auto-instrumentation requires resources just like any other process, and this requirement scales with the application it's automatically instrumenting.

So what's the cost? Well, I can't tell you what it will be in your application, but over the last year or so we’ve been auto-instrumenting quite a lot of code. Along with those findings, let's explore some performance testing experiments, and comparisons with other “free signals” tools, to learn more about how much you're paying for that free lunch.

Oh, and what are the benefits? Let me show you that too :)