Skip to main content

This is what Streams are made of

Next stop, Stream! Err, rather, we're already here, why don't we look at another new feature in Stream?

End-to-End Packs​

Has this ever happened to you? You've built out a beautiful pipeline in Stream. Everyone is proud of you (even your parents). You want to share your masterpiece with the world, or at least your team. But dammit, they don't have the same Sources as you! They don't have the same Destinations as you! Not yet, anyway. Hello Source and Destination Packs! Now when you create a Pack, you can include all the Sources and Destinations you need to make your pipeline work. And when you share it with your team, they can install the Pack and have everything they need to run your pipeline. No more "I don't have that source" or "I don't have that destination" excuses!

See For Yourself
  1. If you're not in Stream, at the top left of the Cribl.Cloud interface, click Products > Worker Groups > default
  2. In the default Worker Group, click Processing > Packs in the top submenu
  3. Click into Hello Packs
  4. Click into either Sources or Destinations in the Packs submenu
  5. Rejoice!

Normally we'd dive deeper into specifics, but this is just creating Sources and Destinations, which I assume you've done before. If not, we have yet another sandbox (YAS👏) for that: Cribl Stream Overview.

What happens in packs stays in packs

When configuring Sources or Destinations in a Pack, they will only be available in the Pack. They will not be available in the Worker Group or any other Pack. This is to ensure that the Pack is self-contained and can be shared without worrying about conflicts with other Sources or Destinations.

I won't cheapen the experience by trying to add any other minor feature walkthroughs here. Let's wrap up.