Curious + Community

Get data and data pipelines flowing – from any source to any destination. We’ll show you how, your peers will tell you how, and together we’ll build a better data experience for you and your organization.

Cribl Blog Articles

The Cribl blog covers Observability Pipelines, Big Data Analytics, Data Streams Processing, News about Cribl's Products, and Much More!

Mastering Tail Sampling for OpenTelemetry: Cost-Effective Strategies with Cribl
Recently, I have seen a trend of enterprises moving toward OpenTelemetry (OTel) for application tracing. Tail sampling, in particular, has emerged as a preferred approach to gain actionable insights while balancing data volume and cost. OpenTelemetry offers developers and practitioners the ability to instrument their code with open-source tools, moving away from vendor-provided tools for […]
The Stream Life Podcast 110: Microsoft Azure + Cribl – Better together
In this episode of The Stream Life Podcast, Kam Amir and Aldo Dossola join the show to discuss Microsoft Ignite, Cribl’s solutions for Microsoft Azure customers, and much more. Resources Microsoft Azure + Cribl: Better together If you want to automatically get every episode of the Stream Life podcast, you can subscribe on your favorite […]
Rethinking Security: Why Organizations are Flocking to Microsoft Sentinel
We’ve been steadily building strong momentum with Microsoft over the past year, and the latest step forward is a significant one: Cribl solutions are now available on the Microsoft Azure Marketplace. But why this focus on Microsoft Azure? The answer lies in what customers are prioritizing and discussing with us. Azure’s popularity has surged in […]
Maximizing Financial Efficiency for MSSPs with Cribl: Reducing Egress Costs
In previous discussions about Managed Security Service Providers (MSSPs), I’ve looked into the architectural benefits and product-level advantages of integrating Cribl. Today, let’s explore why Cribl isn’t just technically sound—it’s also a smart business decision that can help MSSPs like you manage and lower egress costs, creating a significant impact on the financial efficiency of […]
Drain the Data Swamp! Tagging your Data in a Data Lake to help Organize and Optimize Search
Sending events into a data lake can make it challenging to find and organize them. Using tagging with Cribl Lake in conjunction with Cribl Search across a primary data source will increase speed of analysis and reduce costs, as well as help keep your data organized. This scenario involves us performing an investigation for an […]

Announcements

Cribl Release 4.9 is Here!
This update brings exciting new features and usability improvements across the Cribl suite and Cribl.Cloud! Here are some hi-lights: Cribl Stream • Persistent Queue: New options—Always On and Backpressure—for reliable data flow. REST Collector: Now supports paginated results in Discover. • Global Navigation: Experience an…

Curious Discussions

How does "teleporting" work in Cribl Stream and Edge?
How does the 'teleporting' function work on a technical level? Based on the documentation on ports (https://docs.cribl.io/stream/ports/), it seems no inbound ports need to be opened on worker or edge nodes for the feature to work. The leader node handles teleport functionality via port 4200. When teleporting to a node,…
How to Protect Syslog data !!!!
Hi I'm in the process of setting up Cribl to send data from a syslog source ( AWS hosted Cisco FTDs) to Amazon S3 . Although the firewall rules are locked down to source and destination , I'm concerned about transmitting unprotected data over the Internet . Can you please advise on the best way to protect the traffic ?…
Data to TCP JSON source it not captured
I am trying to send data to Cribl stream→ TCP Json source using curl command, and i can see the data is coming to Cribl worker node on the given port ( verified with tcpdump) but the same data is not being captured in the TCP JSON source. Any settings i am missing here?
we are removing some fields using Eval function but the bytes_in and bytes_out are still the same.
we are removing some fields using Eval function but the bytes_in and bytes_out are still the same. But, in the pipeline statistics we can see the bytes_out is reduced but it is not reflecting in the Monitoring → Flows.
log and sourcetype reporting in splunk
I want to report on logs ingested with Cribl in the Splunk environment. The logs will remain stored on the Cribl side, but the reporting will be done in Splunk. How can I achieve this? The logs are NOT forwarded to Splunk. thank you in advance for your answers

Get Notified

Feeling you are missing out on the latest news and events? Sign up to be notified with the latest from Cribl.

Join Us on Slack

Join our Slack to ask questions, learn from other users, and share your own experiences as your expertise develops.

Join Slack

Featured Goat

The Cribl Community is incredibly responsive and helpful!

Govardhanen Gopal