Crib LogStream - Docs

Getting started with Cribl LogStream

Questions? We'd love to help you! Meet us in #cribl (sign up)
Download manual as PDF - v2.1

    Docs Home

Deployment Types

Deployment guide to get you started with Cribl

There are at least two key factors that will determine the type of Cribl LogStream deployment in your environment:

  • Amount of Incoming Data: This is defined as the amount of data planned to be ingested per unit of time. E.g. How many MB/s or GB/day?

  • Amount of Data Processing: This is defined as the amount of processing that will happen on incoming data. E.g. Is most data passing through and just being routed? Or are there a lot of transformations, regex extractions, field encryptions? Is there a need for heavy re-serialization?


Single Instance Deployment


When volume is low and/or amount of processing is light, you can get started with a single instance deployment.

Distributed Deployment


To accommodate increased load, we recommend scaling up and perhaps out with multiple instances.

Splunk App Deployment


If you have an existing Splunk Heavy Forwarder infrastructure that you want to utilize you can deploy Cribl App for Splunk. See the note below before you plan.

Cribl App for Splunk Deprecation Notice!

Click here.

Updated about a month ago

Deployment Types


Deployment guide to get you started with Cribl

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.