You’re seeing a mobile optimized view. To explore a walkthrough demo, please return on a desktop device.

Cribl.Cloud 2.0

Explore how Cribl transforms data management through the use of our Cribl.Cloud platform.

Welcome!

We're so glad you’re here! No seriously, it makes our marketing team look good. Why are you here? Big questions... Well, let's just stick to what is covered in this click-through demo.

In this demo, we'll follow telemetry from ingest to insight at Cribl Coffee Co., and see how the Cribl platform gets data ready for the people, and the AI and agents, who rely on it. Three goals:

  • Build AI-ready telemetry: Collect from everywhere, shape it, and route the right data to the right place.

  • Investigate faster without moving all your data: Retain data in open storage and search it in place.

  • Give every team self-service, with central control: Workspaces and Projects that turn the data team into a team of yes.

We'll use Cribl Stream, Edge, Lake, and Search to do it.  Click "Next" if you're ready to rumble!

Setting the Stage: What is Cribl Coffee Co.?

What started as a small coffee shop in the Albanian foothills has grown into a global coffee brand, with over 100 stores and distribution in 140+ countries. After expanding to New York and scaling rapidly, the company faced a major challenge: managing massive volumes of data from POS systems, online orders, invoices, and logistics partners.

Cribl gives Cribl Coffee Co. one platform to collect, shape, route, store, and search telemetry across every source. That turns raw, noisy data into trusted, structured data that IT and security teams can act on, and that is ready for the analytics and AI the business wants to build.

Today, Cribl remains at the core of the Cribl Coffee Co. tech stack, supporting innovation across logistics, manufacturing, and retail analytics. Their story is a testament to how embracing modern data infrastructure, like an AI Platform for Telemetry, can power smarter decisions and global scale.

(Cribl Coffee Co. is, unfortunately, not a real company... yet).

Ready to Explore?

New to Cribl? Click the "Tell Me More" button below to learn more about the Cribl suite of products and how they work together to form a powerful AI Platform for Telemetry

Not so new? Or just impatient? Click "Start Demo"!

Take it to the Edge

Telemetry starts at the source. Cribl Edge enables us to collect it efficiently. With global servers, we need a simplified, centralized management approach across our server fleet.

Edge agents collect and process observability data in real-time – logs, metrics, and traces – from endpoints like Linux, Windows, MacOS, and Kubernetes, forwarding it to Cribl Stream or other destinations.

What's on the Box?

Cribl Edge's centralized management lets you explore logs collected within any Edge node. For example, we can explore the /var/log directory, ensure it contains needed data, and start monitoring it in a few clicks.

Kubernetes? I 'ardly knew 'er!

Our Kubernetes admins, managing thousands of pods, use Edge to filter out unwanted metadata, like ignoring pods in the kube-system namespace. This source filtering reduces the volume of data sent to centralized systems. That’s data we never have to pay to move or store.

Get Those Logs Flowing!

Let's focus on Stream, our first step in building intelligent telemetry pipelines. Stream is where raw telemetry becomes usable data: parsed, enriched, and routed to the right place. Looking at our routing table, you can see how we've organized our application data flow. Data tiering is a core strategy here:

  • First, we send a full-fidelity copy to low-cost object storage for long-term, cost-effective archiving. This is crucial for compliance and potential future analysis.

  • We route a copy to our Lakehouse in Cribl Lake for faster access to recent data (30 days), enabling quick insights.

With our global Kubernetes infrastructure and point-of-sale systems, we use Cribl Edge to collect logs at the source via the 'Cribl HTTP' input. These Edge-collected logs are optimized by Stream pipelines and efficiently distributed to multiple destinations.

Lay Some Pipelines

In this pipeline view, with the functions on the left and a log sample on the right, admins who struggled managing complex configuration files from other solutions will enjoy using the powerful user interface.

We're parsing top-level fields and creating meta fields like __type to drive our data tiering strategy. Every event is parsed, labeled, and structured before it reaches a destination. That's what makes the data trustworthy for people, and for the AI and agents that increasingly consume it. This differentiates data value – critical server errors are more important than informational logs.

This raises important questions about fit-for-purpose data:

  • Should informational logs burden our SIEM?

  • Would our DevOps team find them valuable?

  • Can we route them to Lake, freeing downstream resources?

The OUT tab (on the right) shows the results of our data manipulation. Here, we're sampling health endpoint data, keeping only 1 in 10 status 200 checks, with the dropped events visible in real-time.

This approach ensures we're only sending relevant data to each system, optimizing both performance and cost. Next, let’s see where the full-fidelity copy lands.

Hot Data Summer! At the Lake

Stream shaped our data. Now it needs somewhere to live. Cribl Lake lets us keep everything without sending everything to the SIEM, by decoupling log collection from SIEM and observability platforms.

Building a data lake for long-term retention traditionally means S3 buckets, IAM roles, and approvals across multiple teams. At Cribl Coffee Co., another team owns AWS resources, so every request meant waiting on provisioning. We also had to work out partitioning schemes, retention periods, and permissions for rehydration.

It's as Easy as 1, 2, 3

Cribl Lake is our easy button. We can quickly provision a dataset, set sliding-scale retention periods, and immediately have it available as a destination in Stream and searchable in place with Cribl Search.

Unlike manual S3 management, we've set up Cribl Lake to archive data with per-dataset retention policies in just a few clicks. The data is stored in open formats like JSON and Parquet, avoiding vendor lock-in and providing flexibility in analysis tools. That full-fidelity copy is what we’ll search next.

Where's Wal-Data?

Having stored our data efficiently, we need quick access to insights. That's where Cribl Search comes in, letting us search data in place – in data lakes, APIs, even at the Edge.

From Symptom to Answer

Our subscription service's checkout latency alert fires. Instead of moving data into yet another tool, we search it in place, filter on the parsed fields, and narrow the problem to one region in minutes. The fields are parsed and ready for easy interrogation, so security and operations teams get fast answers during incidents.

That's ingest to insight. Next, let's see how every team gets to do this, with central control.

Say Less. Say "Yes"!

Everything so far works for one team. Cribl.Cloud lets every team do it, with central control.

As Cribl Coffee Co. scaled globally, our centralized IT team was overwhelmed with requests from marketing, DevOps, security, and others. We became known as the "team of no" because we couldn't keep up. Provisioning, permissions, and data requests created bottlenecks that slowed the business.

Now, with Cribl.Cloud Workspaces, we're the "team of yes." Each team has its own isolated workspace:

  • Our main workspace for centralized management, which shares data with the others under controlled sharing and isolation

  • A Marketing Ops workspace focused on customer data analytics

  • A DevOps workspace for application monitoring

  • A SecOps workspace for security monitoring

Each workspace has separate product configurations, independent data flows, and dedicated resources, so teams can't interfere with each other. Access controls, API credentials, licenses, and billing stay centrally managed under a unified control plane. Teams move independently, and governance stays intact.

Subscribe to What Matters

As our coffee business expanded to 100 stores globally and our bean distribution reached 140 countries, the volume of data exploded. Projects and Subscriptions provide the fine-grained control we need to manage this data efficiently.

For example, our DevOps team subscribes to data from our web application and database logs without being overwhelmed by point-of-sale system data from our retail locations when it's not relevant to their work.

Welcome to the Projects

Stream Projects let our DevOps team move fast. When we launched our specialty coffee subscription service last year, the team needed visibility into the entire customer journey from checkout to delivery.

Rather than submitting tickets to IT and waiting days for access, they could immediately build the pipelines they needed within their project boundaries. While they optimize data for their specific monitoring needs, we still maintain a full-fidelity copy in Cribl Lake for compliance and potential future needs.

Wrap Up

Today we followed telemetry from ingest to insight at Cribl Coffee Co.:

  • AI-ready telemetry: Edge and Stream collected, shaped, and routed the right data to the right place, keeping a full-fidelity copy in Lake.

  • Faster investigations: Lake and Search let us find answers without moving all our data.

  • Self-service with control: workspaces and projects turned the data team into a team of yes, with access, licensing, and billing still centrally managed.

The result is trusted, usable telemetry that IT and security teams, and the agents working alongside them, can act on at scale.

Ready to try it? Start a guided sandbox, start a Cloud trial with your own data, or download Cribl Stream and Edge to run it yourself.

Schedule a demoTry Cribl

See

Cribl

See a custom demo tailored to your tools and data challenges, with one of our team.

Try

Cribl

Get hands-on with a Sandbox or guided Cloud Trial.

Free

Cribl

Process up to 1TB/day, no license required.