Walkthrough
Install
Edgepacer — one Rust binary that finds your sources.
Collection runs on Edgepacer, a single static binary written in Rust. Install it on a host or drop it into a cluster as a DaemonSet or sidecar — there's one agent to deploy, not a collector stack to assemble and maintain.
It finds your sources
Edgepacer discovers what's running on its own: containers, journald and systemd units, and log files under /var/log. You don't hand-write a source list per host or keep manifests in sync as services come and go — discovery is continuous. Kernel-level discovery via eBPF is being built out to widen what the agent can see without configuration.
It speaks your telemetry
Edgepacer is OTLP-compatible, so existing instrumentation works without a rip-and-replace or a new SDK. It collects application and system logs, host metrics out of the box, and traces shipped off-host. Parsing, structuring and storage all live downstream — the agent's job at the edge is to see everything and ship it reliably.
It stays out of the way
In our own running fleet the agent sits at under 0.1% CPU and roughly 10 MB of memory, and it buffers to local disk with delivery guarantees — a network blip or a backend hiccup replays from disk instead of dropping a line. (More on that in The Edgepacer agent.)
$ curl -fsSL logpacer.sh/install | sh
discovering sources…
✓ 12 containers
✓ 9 journald units
✓ 4 log files
✓ on host metrics
25 sources · metrics on · 0 config files