On a dreary afternoon in New York City, a 25-year veteran IT director from a Fortune 50 professional services company attended a Splunk User Group meeting, hoping to learn something new to help salve his organization’s license-cost pains. He happened to catch a talk given by Dritan Bitincka, Cribl’s Head of Product— and what he heard intrigued him so much that he vowed to bring his entire team to the next meeting so they could meet Dritan as well.

This IT director is responsible for the care and feeding of the usual mountain of data associated with a modern-era large enterprise. His team’s clients within the company include the app owners, who work with performance, user journey flow, and related analytics data; the operations group, up to their eyebrows in every kind of infrastructure log and config change; and the security practice, who need their threat data feeds coming in and the ability to correlate their contents across – well – pretty much all of the data the other two groups are working with; a great deal of that data
was flowing into Splunk.

The biggest project on the IT director’s plate at the time was a classic one: a whole-enterprise migration to the cloud. And like most things worth doing at this scale, it was going to be the biggest of headaches— costly, time-consuming, and a lot of extra work for him and his team. But what he heard from Dritan made him think it just might all be ok after all. As Dritan described it, Cribl LogStream offered them the opportunity to not only simplify the company’s cloud migration, but also cut back on the data they needed to send to achieve the same business results. The first time the IT veteran heard this, he wasn’t sure he completely understood what was possible, or how long it might take— but once his team grokked the good news, they were off to the races.