Noah Labhart

This episode is sponsored by Mesmo.

If you're responsible for reliability, performance, or platform architecture, you already know the problem.

Telemetry volume is growing faster than teams can manage it.

Mesmo addresses this by moving observability upstream.

Instead of storing everything and asking questions later, Mesmo processes telemetry in motion, filtering, transforming, and enriching logs, metrics, and traces before they reach your observability backend.

The result is cleaner data, reduced ingestion costs, and faster root cause analysis using the tools you already rely on.

Mesmo integrates with platforms like Datadog, Dynatrace, and Open Source Stacks, giving teams more control without adding operational overhead.

This is especially useful for platform engineers and SREs supporting complex, distributed systems where context and speed matter.

To see how active telemetry works in practice, get a demo at mezmo.com slash codestory.

That's M-E-Z-M-O dot com slash codestory.

I'm curious about scalability.

This will be interesting, right?

Where scale was considered in the beginning.

Obviously, there's going to be some elements that are part of your bread and butter, but I'm also curious about where you've had to fight scale as you've grown.

And that could be people, could be technology.

I'm primarily interested in the technology aspect.

I'm curious, Toby, as you step out on the balcony, look across all that you've built thus far at growth, what are you most proud of?

Let's flip the script a little bit.

Tell me about a mistake you made and how you and your team responded to it.

Toby, you've touched on this a bit, but I kind of want to give space for a full answer and some things that you see in where you're going as GrowthLoop, but also where the industry is going and all the things.