Cribl Stream^™ Use Case:
Route From Any Source to Any Destination

Stream acts as a universal receiver and collector of log and metrics data. With it, you can retrieve, transform, analyze, and correlate data from any source and send it to any destination, or even to multiple destinations, without adding any tooling.

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 optimal location to leverage it most effectively.

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 goes beyond just collecting data from any source and delivering it anywhere, it maximizes the value of observability data by transforming and adding context from other sources, in real-time, enhancing the value of all your analytics tools.