Operations | Monitoring | ITSM | DevOps | Cloud

As someone who admittedly gets bored easily, one of my favorite things about working for a company like Cribl is the huge amount of technologies in our ecosystem I get exposure to. Over time, I also get to observe trends in the market – it’s always so cool to see big upswings in adoption for various platforms and tech. One such trend I’ve observed over the last year is a noticeable uptake and presence in the market of Google Chronicle.

Consistent performance and continuous improvement: these are the fundamentals we should aspire to in the world of cloud software delivery. We focus on ensuring our systems become more consumable, enjoyable and innovative. We seek to make customers’ lives easier and more productive through incremental achievements, and doing a better job, every day.

Event Hubs is Microsoft’s cloud-native real-time event streaming service. For Event Hubs to work, data must be pushed to or pulled from it. That is where Cribl Stream comes in. Event Hubs is a source and destination inside Cribl Stream and the control for how you route, shape, and transform your data from Event Hubs. But, one does not simply Stream into (or from) Event Hubs. There is a lot that goes into architecting an Event Hubs Source.