Data is the lifeblood of every business, but most of it is underutilized, buried under high costs and complex schema management. Simply funneling data into an analysis platform or cheap storage isn’t enough. Data deserves better.

In today's digital landscape, security and observability teams face an unprecedented challenge: managing massive volumes of data while maintaining both performance and cost-effectiveness. As organizations generate more data than ever before, the traditional approach of storing everything in high-performance, expensive systems is becoming unsustainable. How will your team evolve how it manages and uses telemetry data across the enterprise?

I’m so excited to share that Cribl recently surpassed $200 million in annual recurring revenue! This milestone and our rapid growth comes down to one thing: Solving real problems for our customers. The more our customers partner with us and use Cribl products to simplify their telemetry data management, the more our business grows and the more milestones we’ll hit together. Thank you to our fantastic customers and partners who have helped us reach this point in our journey!

What do you do when an incident occurs, and you need to investigate and troubleshoot? Replay data. What about performing audit trails for compliance and reporting? Replay data. Need to do system testing and validation? Replay data. There are countless reasons to replay telemetry, but the ease of doing so largely depends on the tools and infrastructure you have in place. Manual replay is often cumbersome and time-consuming, requiring access to stored raw data in logs or files.

Let’s face it—the term "software supply chain" can feel like navigating a maze of tech jargon. Commit signing, Software Composition Analysis (SCA), eBPF monitoring, SBOM generation, provenance attestations… the list goes on. But at its core, the software supply chain is the backbone of modern development, and its security is non-negotiable. A single vulnerability in this chain can ripple through entire systems, leading to breaches, downtime, and reputational damage.

The end of the year for technology companies always brings with it a raft of new predictions for the coming twelve months. Many predictions, breathlessly delivered, suggest a tenuous future can be conveniently avoided with the appropriate application of vendors’ products. Using predictions as a way to shill products is boring, and it misses an opportunity to help enterprises plan for the coming year. After all, predictions don’t have to be correct to be useful.

Let me set the record straight before anyone accuses me of bias or not being an OpenTelemetry supporter. Cribl loves OpenTelemetry! We’ve written lots of blogs about It; we have vendor-specific OpenTelemetry Destinations (with more to come!), and we support automatic batch parsing for easier data manipulation and re-batching for network transport efficiency of logs, metrics, and traces.

As we wrap up an incredible year, it’s the perfect time to celebrate Cribl’s progress and innovation in 2024! This year brought many exciting features designed to solve real-world problems and make life easier for our customers. In the spirit of reflection and festivity, I’ll highlight twelve game-changing product features, releases, and enhancements— each a testament to listening, learning, and delivering value to you, our users.

Ever wondered how many NetFlow exporters or edge routers you have configured on your core switches? What if I told you that every exporter uses ~0.2% bandwidth in overhead? While that may not seem like much (and it has been a few years since most network engineers were worried about CPU overhead for NetFlow exports), older hardware and network OS versions may be more sensitive to having multiple flow exporters configured.

Over the past year, I’ve noticed some interesting trends in my work with state and local governments. Across my conversations with organizations in this space, there’s a common thread: teams are getting creative about maximizing their limited resources. With budgets either flat or shrinking and operational demands increasing, these teams face tough choices. They’re being asked to maintain or improve services while working with the same, or in some cases, fewer resources than before.