What you will learn in this TP
- Install Cribl Stream with Docker
- Create a syslog source
- Capture events
- Create a destination and a route
- Check in Monitoring
Introduction #
What you will learn in this section
- Install Cribl Stream with Docker
- Create a syslog source
- Capture events
- Create a destination and a route
- Check in Monitoring
Context. Your team wants to evaluate Cribl before trusting it with production logs. You need a test instance and a first end-to-end flow.
Prerequisites: a machine with Docker and Docker Compose (4 GB free memory), curl and jq · Estimated time: 40 min
A persistent Cribl instance receiving syslog and writing it to compressed JSON files.Setup #
Guided steps, with their solution.
1. Start Cribl Stream
Why? The volume keeps configuration if the container is recreated.
Start the container with a configuration volume and an output folder, then wait for the API to answer.2. Log in
Why? The default password must be changed immediately.
Openhttp://localhost:9000, log in asadmin/admin, change the password and accept the free licence.3. Create the syslog source
Why? A source defines the listening port and the fields added to each event.
In Data › Sources › Syslog, createin_syslogon TCP and UDP port 9514, with the fieldsourcetype='syslog'. Send a few messages.4. Watch live
Why? Always look at data before transforming it.
On the source, open Live Data, resend, then save the capture as the sample filesyslog_app.log. Find_raw,_time,host,appname.5. Destination and route
Why? The route decides which events go where, with which pipeline.
Create a Filesystem destinationout_files(folder/data/out, JSON, gzip, partitioned bysourcetype), then asyslog_to_filesroute at the top of the table: filter__inputId.startsWith('syslog:in_syslog'), pipelinepassthru, destinationout_files.6. Check in Monitoring
Why? Counters prove nothing is lost between input and output.
In Monitoring › Data, compare events received byin_syslogand sent byout_files. Then look at the created configuration file.
Difficulty level : ●●○○○ (2/5)
My progress
Sign in to track your progress and take notes. Sign in
💬 Questions about this lesson
No questions yet: be the first to ask for help or share your configuration.
Recommended Articles
Automating Cribl: REST API, Packs, Git and Terraform
Managing Cribl as code: REST API (authentication, group paths, commit and deploy), reusable Packs...
Installing and deploying ClickStack: all-in-one, Docker Compose, Helm and Managed ClickStack
Deploying ClickStack to fit the need: all-in-one container with persistence, Docker Compose and i...
Installing Grafana Tempo (Docker Compose, binary and Helm)
Install Grafana Tempo: the tempo.yaml configuration, Docker Compose with Grafana and Prometheus, ...
Installing Grafana Loki (Docker Compose, binary and Helm)
Install and validate Grafana Loki: minimal configuration, Docker Compose with Grafana and Alloy, ...
Installing Jaeger v2: all-in-one, configuration and storage
Run Jaeger v2 as all-in-one, understand its configuration file (jaeger_storage and jaeger_query e...
Installing the Datadog agent and configuring integrations
Install the Datadog agent on Linux, Docker and Kubernetes (Datadog Operator), understand datadog....
Installing Bindplane: server, BDOT Collector and OpAMP connection
Install the Bindplane server (Docker Compose, Linux, Kubernetes), connect BDOT collectors via OpA...
Installing OpenObserve and ingesting your first data
Install OpenObserve with Docker Compose or the binary, configure it with its ZO_* variables, send...
Installing Zabbix and monitoring your first host
Install Zabbix with Docker Compose (server, PostgreSQL, web interface), install agent 2 on a Linu...