If there was a question on if an enterprise needed an observability pipeline in 2019 or 2020, we now know the answer is: yes. The observability data management methods of the 2010s aren’t going to work in the 2020s. Data is growing too fast for us to ignore, and the need to gain intelligence from said data continues to grow in importance. Data (and access to it) is becoming a competitive edge for many enterprises today.
An old colleague of mine once said to me, “It doesn’t matter how inefficiently something DOESN’T work.” This was a joke used to make a point, so it stuck with me. It also made me consider that it does matter how efficiently something DOES work. Sometimes, when we have tools like Cribl Stream making things like routing, reducing, and transforming data so easy, we can forget that there might be a more efficient way to do it.
Git integration has always been at the foundation of Stream. In the fall 2021 release of Cribl Stream (both on-prem software and Cloud), our Enterprise users have a received set of APIs to separate the development and deployment of Stream. Stream GitOps connects with your favorite git based versioning platforms and leverages their PR, approve/reject, and CI/CD workflows to push production-ready changes from a development branch into a main branch or release.
It’s been an exciting few days at Cribl. A week ago, we announced our $150 Million Series D funding round led by Tiger Global, with participation from existing investors IVP, CRV, Redpoint Ventures, Sequoia Capital, and Greylock! We also announced an exciting new product: Cribl Search! We’ve been blown away by the excitement from our customers thus far.
Many cybersecurity teams are drinking from multiple firehoses without solutions in place to deal with the onslaught of data. And with 70 percent of companies experiencing over one hundred attacks each day, it’s not slowing down. Teams are overwhelmed with data from multiple sources and formats with continuous requests to pull in more and more.
As CEO of Cribl, one of my greatest privileges is to spend time on the road and on calls with our customers hearing about their needs and challenges. Cribl is a focused company. We build software for observability and security. With this lens, it becomes clear the industry is neglecting to address the unique needs of our users. There are many reasons, most of which are simply that vendors tend to come at a user’s problem through the lens of their existing technology.
We are pleased to announce we have closed our Series D round of funding, led by Tiger Global with participation from existing investors IVP, CRV, Redpoint Ventures, Sequoia, and Greylock Partners. In this round, we raised $150M, bringing our total raised to over $400M. This new fundraising round further validates the value we provide to customers.
“We lost choice and control when we migrated to Splunk Cloud, but got it back when we adopted Cribl Stream.” The above quote is from a new Cribl customer talking about why they adopted Cribl Stream to manage observability and security data.
Everybody is used to dealing with the bugs on their smartphone and other technology devices In their homes that have been an issue for years. The fact that they may never be resolved is just one of those things that we’ve decided to accept. At Cribl, we approach this situation differently — we’re not okay with bugs of any size.
One of Cribl Stream’s selling points is the reduction of ingested log volume, which helps our customers control costs and improve system performance. This can be accomplished in two ways – either by eliminating duplicate or unnecessary fields and null values within the events, or controlling the number of specific events that actually get sent to the destinations through strategic filtering.
