This section breaks down the key terms and concepts you need to know to talk about and build Cribl setups.
Deployment Model | What It Is | How It Works (The Technical Stuff) |
|---|
| Cribl.Cloud Hosted | A deployment model where Cribl components are provisioned and managed within a public cloud infrastructure (AWS/Azure) using the Cribl.Cloud (SaaS) service. | - Cribl provisions infrastructure using Cloud APIs.
- Networking and security are handled through cloud-native tools (VPCs, firewalls, and others).
- Identity is tied to cloud services like AWS IAM.
- Data is stored in cloud object storage (S3, Azure Blob, and others).
- Access to Cribl Search and Cribl Lake.
|
| On-prem or Customer-managed | A deployment model where all Cribl components are hosted within customer-controlled infrastructure, including physical data centers, private clouds, or customer-managed virtualization platforms. | - Download and run Cribl software on your own infrastructure.
- You manage the hardware and virtual machines directly.
- You’re in charge of all networking and security.
- You use your own local storage systems.
- It integrates with your existing company identity systems.
- You control the placement and sizing of all components.
- Cribl Search and Cribl Lake are not available.
|
| Hybrid | A flexible deployment that combines cloud-hosted and on-prem components, all managed from a single, centralized control plane in Cribl.Cloud. | - The Cribl.Cloud Leader serves as your centralized control plane.
- Worker Nodes that process your data can be anywhere: in Cribl.Cloud, on public/private cloud instances you manage, or in your own data centers.
- This setup makes it easy to expand your observability into new cloud regions or replace physical data centers without losing centralized control.
- You can add or reassign Worker Nodes and Edge Nodes using simple, auto-generated command-line scripts from the UI. Access to Cribl Search and Cribl Lake.
|
