These docs are for Cribl Stream 4.8 and are no longer actively maintained.
See the latest version (4.20).
OS and System Requirements
For a successful Cribl Stream deployment, verify that your system meets the minimum hardware and software specifications outlined below.
Leader Node Requirements
Given the Leader’s critical role in coordinating Worker instances, we recommend deploying it on a stable and highly available infrastructure.
All the quantities listed below are minimum requirements.
| Specification | Requirements |
|---|---|
| OS |
|
| System |
|
| Git | git must be available on the Leader Node (details below) |
| Browser Support | The five most-recent versions of Chrome, Firefox, Safari, and Microsoft Edge |
Worker Node and Single-Instance Requirements
This section outlines the requirements for deploying Worker Nodes and Single-instance deployments. For a deeper understanding of these concepts, see Worker Nodes and Single-instance deployments.
Requirements
The Worker Node requirements are identical to Single-instance deployments. All quantities listed below are minimum requirements.
| Specification | Requirements |
|---|---|
| OS |
|
| System |
|
| Git | git must be available on the Leader Node. See details below |
| Browser Support | The five most-recent versions of Chrome, Firefox, Safari, and Microsoft Edge |
| SELinux Support | enforcing mode is supported, but not required. |
Requirements Considerations
Keep the following considerations in mind:
Cloud VM Recommendations
To fulfill the requirements using cloud-based virtual machines, see Recommended AWS, Azure, and GCP Instance Types.
Core Equivalency
We consider 1 physical core to be equivalent to:
- 2 virtual/hyperthreaded CPUs (vCPUs) on Intel/Xeon or AMD processors
- 1 (higher-throughput) vCPU on Graviton2/ARM64 processors
Memory Requirements
- Each Worker Process can consume memory up to its maximum heap size, plus Node.js overhead, and additional memory that scales with configuration (e.g., Destination type and number).
- Ensure your total host memory allocation covers the memory usage of all Worker Processes and OS requirements.
- Continuously monitor Node memory usage, especially after configuration changes.
- For additional details, see