ctrlb-decompose
Collapse millions of log lines into typed patterns before an LLM reads them
Emerged finds new products worth a look, daily — what’s new today
When a service falls over at 3am, logcrux reads the journal or container logs on the box itself and names the burst or failure that matters, without shipping data anywhere.
logcrux reads a log file or a piped stream from journalctl, docker or kubectl and reports what went wrong: error bursts, rate spikes and one-off failures, each tied to the entities involved and the lines that show it. A statistical engine does the detection; small local classifiers group events and label the likely incident. It recognises more than 200 log formats, needs no account or network, and installs with uv. Apache-2.0, v0.10.0, from a maker known only as Ravipati.
More like this
Kibana-agent
Let a coding agent search, count and tail your logs through Kibana, read-only
Fanout
Self-hosted traces, logs and metrics that you and your agents can query
HomeButler
Tells you what changed on your server, not what is running
TrackLLM
A public record of when hosted language models quietly change behaviour
Geiger
Inventory every AI agent on your machine and what it can reach