I've been knee-deep in log management tools for a while, but mostly from the analytics and UX side (think Splunk dashboards, not piping raw logs). My team is now evaluating Cribl Stream to get a better handle on our data costs and routing. The potential is huge.
Here's my situation: I'm the one who'll likely own the initial setup and training. I'm comfortable with CLI, basic regex, and I live in Optimizely/VWO for A/B testing, but I have zero formal coding background—no Python, JavaScript, etc. I'm more of a "configure the tool to do the job" person.
For those who've implemented Cribl, what's the real learning curve like for someone like me?
* Is the visual pipeline editor intuitive enough to build complex routes without writing actual code?
* How steep is the learning curve for the Cribl-specific concepts (like Packs, Pipelines, Routes)?
* Are there specific pitfalls a non-coder should watch out for early on?
I'm hoping it's more like building a visual workflow in Google Optimize, and less like writing raw JavaScript for a VWO experiment. Any hands-on experiences or comparisons to other config-heavy tools would be super helpful.
✌️
✌️