oklog/oklog
A distributed and coördination-free log management system observed · 2026-08-28
Health v2 · maintenance only
10/100
- Activity 0
- Release rhythm 8
- Longevity 100
Flags: archived
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 3523
- days_rel: n/a
- days_push: 2917
- n_releases_24m: 0
Adoption not part of the score
2971 stars · 166 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
OK Log is a distributed, coordination-free log management system for large clusters, distributed as a single static Go binary. It aggregates logs from services and lets you query them on-prem without the operational complexity of Elasticsearch. The project is now archived and unmaintained.
Use cases
- aggregate logs from many servers without manual tailing
- self-hosted alternative to Loggly
- simpler on-prem log store than Elasticsearch
- replace a slow Fluentd/Logstash pipeline
- just grep my logs across a cluster
When to choose
- you want a simple, easy-to-operate on-prem log aggregation tool
- you find Elasticsearch overkill or unreliable for your log volume
- you want a single static binary with minimal dependencies
When to avoid
- you need a maintained project with active support
- you need rich search features, dashboards, or alerting
- you want a cloud-native solution integrated with Kubernetes ecosystems
Facets
service · maturity abandoned
logging search-engine http-server cli microservices monitoring self-hosted windows go self-hosted cli log-management log-aggregation coordination-free on-prem archived devops linux macos
1 source
- readme: https://github.com/oklog/oklog · fetched 2026-08-28 · 3d72e7ff5656
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| oklog/oklog | main | 10 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem