This message originated from Cribl Community Slack.
Click here to view the original link.
Hi all,
I'm looking to add multiple teams to the cribl console that I manage.
I won't be needing multiple workspace, so I consider using Projects in Stream .
The setup is pretty simple, every team can read every projets but editor only of their own.
My question is, is there any recommendations or tips to switch from using routes to subscriptions?
Should I put all my routes to one sub, then let the teams filter with pipelines? Or make 1 sub per route already there?
The goal is to make them autonomous without admin access
Solved
Cribl Console Team Management: Recommendations For Switching From Routes To Subscriptions
Best answer by Jon Rust
I think either workspaces, or Packs, would be a better path forward for you. Packs now include sources and destinations, so you can bundle in the entire event lifecycle. The engineers developing it can do so on their own instance, then push (git, or just files) to the cribl admin.
I think either workspaces, or Packs, would be a better path forward for you. Packs now include sources and destinations, so you can bundle in the entire event lifecycle. The engineers developing it can do so on their own instance, then push (git, or just files) to the cribl admin.
Sign up
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.