Skip to content

The CollectionInstrument No. 03

lantern

Jaeger shows traces. Loki shows logs. Grafana expects a stack. Lantern expects a port.

The Problem

You’re debugging locally and want to see what your service emits. The standard answer is an observability stack — collectors, indexes, dashboards — infrastructure that dwarfs the app you were trying to inspect.

The signal was never the problem. OpenTelemetry already carries traces, logs, and errors out of your process. There was just nowhere small for it to land.

The Insight

For local debugging you don’t need a platform. You need a binary and a browser tab.

The Instrument

lantern is a single Go binary that speaks OTLP — gRPC on :4317, HTTP on :4318 — stores everything in SQLite, and opens a UI on :4000. Point your existing OTel exporter at localhost and you have a trace waterfall, logs, and error fingerprint grouping.

A Bubble Tea TUI covers the terminal-bound, and snapshot/replay bundles let you hand a failing trace to a teammate like a save file.

One binary, both ends of the wire

  • your app, OTel exporter; connects to lantern (OTLP :4317 / :4318)
  • lantern, single binary; connects to SQLite, browser UI, TUI
  • SQLite, embedded store
  • browser UI, localhost:4000
  • TUI, Bubble Tea

Your app keeps its exporter. Lantern becomes the backend, the store, and the UI.

Spec

Ingest
OTLP gRPC :4317 · HTTP :4318
Storage
SQLite — no services, no volumes
Surfaces
Browser UI :4000 · terminal TUI
Debugging
Trace waterfall · logs · error fingerprints · snapshot/replay
Install
go install · release binaries · ghcr.io/meru143/lantern (v0.1.0)
Quick start
go install github.com/Meru143/lantern/cmd/lantern@latest

The Outcome

v0.1.0 shipped on 22 October 2026: binaries for Linux, macOS and Windows, and a public image at ghcr.io/meru143/lantern; Homebrew is still to come. Built so one binary replaces the stack you used to run just to answer “what did my app just do?”