We’ve been busy building more features for Cribl Stream, and are excited to share the new value we offer our users. Cribl Stream 3.5 is now available! This release brings some much-requested features that will help users build more robust observability pipelines, with new sources and destinations. Let’s dive into what’s new!
Cribl.Cloud’s Summer 2022 release is now available in an AWS cloud near you! As part of this release, we are excited to share the features we have been building, including the latest Cribl product releases (Stream 3.5 and Edge 3.5). This release brings some much-requested features that will help customers increase their compliance, reduce overall costs, and deploy a more resilient observability data pipeline.
What is an observability engineer? They build monitoring tools, right? Develop data pipelines? For time series data? Maybe distributed tracing? Ah, got it…an observability engineer is just an extension of an SRE with a wider ‘end-user’s’ perspective? But don’t they also build solutions that move telemetry for security tools? Maybe monitor and review an organization’s overall security posture?
What a kickoff to the summer! That’s right, in the past two weeks, we got to welcome a lot of our ecosystem back with hugs, high fives, fist bumps, and air fives! It has been a great way to get welcomed into my new work family.
It’s common for most CISOs to lead off a security conversation by comparing what other companies in the industry are spending on cybersecurity and simply matching that. After all, regardless of the results, the CISO can always tell the board of directors they’re following industry guidelines around security budgets. The problem is security outcomes are bad regardless of budgets. It’s not what you spend. It’s the results you get that matter.
Many years ago, I attained my private pilot’s license. This entailed completing a very structured program, similar to how most companies introduce a product to a new user. Let’s be honest, there is a really good reason for this – to avoid the crash and burn. With flight training, it’s literal, while with products it’s a bit more figurative (except when you YOLO something into production–that can cause a crash and burn–and leave for a bad first impression).
Cribl Packs are, in my opinion, our most exciting feature. Packs encapsulate the deep log processing capabilities and enable sharing of the best practices with customers, Worker Groups/Fleets, and the Community. Ease of sharing enables consistent configurations across distributed deployments of Cribl Stream or Cribl Edge. All users can leverage Packs–and should! If you collect Microsoft Windows Logs, use Palo Alto Networks or share logs via Syslog, Packs are for you.
Every enterprise collects and stores massive amounts of security and observability data but struggles to get value outside of operations and security teams. These datasets can offer enormous value to business operations and enterprise reporting teams if they have access to the data in their toolsets. BizOps needs to optimize batch planning and the enterprise reporting teams need to reconcile how many assets the enterprise owns versus the number it has under support contracts.
Back in late May, we hosted a webinar on the heels of our Series D funding announcement where we also took the wraps off our big product announcement: Cribl Search.
Software exists to make your job easier, not to suck the joy out of your work. It should be there when and if you need it, but be completely out of the way when you don’t — you’re at work to get a job done, not to use any particular product. If you’re forced into using the same underperforming, over-customized, difficult to implement, or just generally terrible software each and every day, it can really put a damper on the quality of your work and quality of life.
