Cribl Stream^™ Use Case:
Avoid Vendor Lock-In

Stream is built around protocols first, and then around specific vendors as needed. Since we focus on standards, you can bring any source into the equation, and send that data to any system of analysis – or to multiple destinations at a time.

Stream can receive push data from sources such as Splunk, HTTP, Elastic Beats, Kinesis, Kafka, TCP JSON, and pull data from Kafka, Kinesis Streams, Azure Event Hubs, SQS, S3, Microsoft Office 365, or even external inputs such as weather data, air quality, and anything else your business wants or needs to drive better decisions.

With Stream it’s finally possible to send the exact data your organization needs, in the precise format required, to the best location. At the end of the day, your analytics tools are only as good as the data they receive.

Stream data through Stream to Splunk, AWS Kinesis Streams, SQS, and CloudWatch Logs, Elasticsearch, Honeycomb, TCP JSON, Syslog, Kafka Azure Event Hubs and Monitor Logs, StatsD and StatsD Extended, Graphite, InfluxDB, Wavefront, SignalFx, and more, as well as destinations that support batch or non-streaming output such as S3 compatible stores, filesystem/NFS, MinIO, Google Cloud Storage, and Azure Blob Storage.

Stream unlocks more options for your observability data – and your organization. It goes beyond collecting data from any source and delivering it anywhere; Stream optimizes your observability pipeline, giving you the flexibility to choose the best tools for your use case – regardless of your current vendor.