RousselTMLEARNING

Observability

Cribl Edge: collecting close to the sources

Deploying Cribl Edge on Linux, Windows and Kubernetes: the agent's role, Fleets and Subfleets, collecting files, journald, Windows events, system and Kubernetes metrics, sending to Stream via Cribl HTTP, and best practices.

1. The role of Cribl Edge #

The same engine, as an agent.

Principle #

Edge and Stream

Cribl Edge is an agent installed on hosts or as a Kubernetes DaemonSet. It embeds the same engine as Stream (sources, routes, pipelines, destinations) and can therefore filter, mask and reduce at the source, saving bandwidth. Edge Nodes are driven by the Leader, grouped in Fleets (and Subfleets) sharing a configuration.

2. What Edge collects #

Local sources.

Sources #

SourceCollects
File Monitorlog files, with automatic discovery and rotation tracking
Journal Filesjournald (systemd)
Windows Event LogsApplication, System, Security, Sysmon logs…
System Metrics / Windows MetricsCPU, memory, disks, network, processes
Kubernetes Logs / Metrics / Eventscontainer logs, node and pod metrics, cluster events
Execoutput of a scheduled command (inventory, check)

Edge also offers local exploration: from the Leader, you browse a host's files and processes to choose what to collect.

3. Deploying #

Linux, Windows, Kubernetes.

Methods #

  • Linux: in the Leader, Add/Update Edge Node generates a command (install script with token and Fleet) to run on the host.
  • Windows: MSI installer, with the same parameters (Leader, token, Fleet), deployable by GPO or endpoint management tool.
  • Kubernetes: Edge Helm chart, deployed as a DaemonSet (one agent per node); the Leader UI provides the Helm command with the right parameters.
Watch out : Use the commands generated by your Leader: they contain the token, address and Fleet. Do not copy a command found online with a sample token.

Sending to Stream #

The Cribl HTTP destination (on Edge) and Cribl HTTP source (on Stream) pair is the recommended link: compressed, authenticated, and designed so data is not counted twice in the licence between Edge and Stream. Cribl TCP is the TCP equivalent.

4. Best practices #

A discreet agent.

Rules #

  • One Fleet per host type (web servers, databases, Windows endpoints) and Subfleets per environment.
  • Filter and mask on Edge; keep multi-tool routing and heavy enrichment on Stream.
  • Limit the agent's resources (CPU, memory) and monitor its own metrics from the Leader.
  • Test any new configuration on a small Subfleet before rolling it out.

Commands to know #

Commands to know
  • systemctl status cribl-edge : agent status on Linux
  • kubectl -n cribl get pods -o wide : cluster Edge agents
  • Manage › Edge › Add/Update Edge Node : generate the install command
  • Cribl HTTP (destination → source) : Edge to Stream link

Sources #

Checked in November 2026 (Cribl 4.20): Cribl ships a minor release about every two months, check the release notes before relying on a detail.

Related articles

Cribl: the data pipeline for observability and security

Discover Cribl: why a telemetry data pipeline, the Cribl suite (Stream, Edge, Lake, Search, Cribl.Cloud), the…

Installing and administering Cribl Stream

Installing Cribl Stream with Docker or on Linux, running it as a service, understanding $CRIBL_HOME, default …

Sources, destinations and routes in Cribl Stream

Receiving and sending data with Cribl Stream: push, pull, collector and internal sources, event breaking, des…

Keep learning

Support us

♥ SUPPORT US

Support RousselTM Learning

Courses, articles, labs and certificates stay free with no intrusive ads. A voluntary contribution, of any amount you choose, pays for hosting, lab environments and new content.

Contribute with PayPal Any amount · card or PayPal accountLearn more
QR code PayPal
Or scan this QR code with your phone

Thank you, every contribution counts!