We're thrilled to announce Cribl Collectors and Collector-based Sources are now supported inside Cribl Packs!
What’s the Big Deal?
Previously, while you could use Packs to share and manage a majority of push and pull based Sources, you had to manage your Collector Sources separately. This often led to a disjointed workflow, making it difficult to maintain and share a complete solution. With the latest release of Cribl Stream 4.14, that all changes. Now, you can create a Pack that will let you add any Collector into the mix and help you manage Cribl configurations with ease.
What Can I Actually Collect?
All of the powerful Cribl Collectors and Collector-based Sources are now fully supported in Packs, enabling you to bundle the entire telemetry stream from a vast array of data sources. This includes Collectors for popular cloud services like Amazon S3, Azure Blob Storage, and Google Cloud Storage, as well as relational databases with our Database Collector. You can also now include data collection into Cribl from internal, external, and vendor based APIs and web services using the versatile REST Collector. This comprehensive support ensures that whether you're collecting from a cloud data lake, a structured database, or a custom API, your entire end-to-end solution can be contained, shipped, and deployed seamlessly as a single, portable Cribl Pack.
What Else Do I Get With Collectors?
For several Cribl Collectors, it's important to include other knowledge objects when configuring things like Rest Collectors, which is why it was imperative to include support for HMAC functions and Database connections. The inclusion of HMAC functions and Database connection knowledge objects in Cribl Packs is a game-changer for delivering complete, portable, and robust data solutions. These specialized objects, which handle everything from generating secure API authentication signatures to managing credentials for database access, can be bundled directly with your Collector configurations inside Packs. By including this critical authentication and access logic within a Pack, you can eliminate manual setup steps, prevent misconfigurations, and ensure your entire telemetry pipeline is fully self-contained.
How It Works
Getting started is simple. When you create or edit a Pack, you can now add Collectors into packs by creating or entering a Cribl Stream Pack, navigating to Sources tab and clicking Collectors.
Once added, these Collector sources are part of the Pack’s configuration. When you export the Pack, all of the Collector, Source, and supporting Knowledge objects (like HMAC functions and database connections) are included but sensitive credential information like encrypted strings or secrets will be removed upon export. When you import the Pack, the Sources are automatically created on the target system, ready for you to deploy the Collector and start shipping data.
The Power of Packs, Expanded
This release is a huge leap forward in our mission to make data ingestion and processing as simple, efficient, and governable as possible. It empowers you to build, share, and deploy portable telemetry streams like never before.
Ready to start building and sharing your complete telemetry streams in Packs? Update your Cribl Stream instance to v4.14 today, and add a Collector to a Pack!
And as always, if you have a great Pack you'd like to share, contribute it to the Cribl Community on packs.cribl.io!
