Logtide: 1 Year After the First Commit (The Real Numbers)

说明与用途

Logtide 从最初的原型发展为完整的多租户可观测性平台，使用 Docker Compose、SvelteKit、TimescaleDB、ClickHouse、MongoDB 和 OpenTelemetry，强调安全性和社区贡献。

问题

Self‑hosted observability stack users need a lightweight, multi‑tenant log, trace and metrics platform that can be deployed quickly and scaled without excessive resource consumption.

结果

Logtide grew from zero to a mature, multi‑tenant observability platform with a strong community of self‑hosters, achieving significant Docker pull growth and a robust feature set while maintaining a lightweight footprint.

工作流

• 1. Publish initial Docker Compose and SvelteKit frontend
• 2. Add TimescaleDB as default storage
• 3. Introduce Redis/BullMQ for job queue
• 4. Release incremental versions adding optional Redis, PII masking, ClickHouse, OTLP metrics, MongoDB, custom dashboards, uptime monitoring, webhook receivers, digest emails, error regression detection, geo map panels, rebuilt UI, unified query language, incident inbox, Slack/Teams/PagerDuty integrations, and an extension system
• 5. Conduct security audit before 1.0 release, fix cross‑tenant read and XSS vulnerabilities
• 6. Publish yearly metrics and lessons learned
• 7. Encourage community contributions via SDKs and extension system

证据

Docker pulls (backend image) 47,000+

来源

The stars curve flattened after the virtualizationhowto.com spike. The Docker pulls curve did not.

来源

The commit count is mostly me. 1,982 of the 2,020 commits have my name on them.

来源

0.5.0 made Redis optional. 0.6.0 added PII masking at ingestion, and ClickHouse as a second storage engine.

来源

All of it was fixed in 1.0, along with a dedicated isolation test suite and CI checks so the same pattern fails the build if it comes back.

来源

Docker Compose as the main install path.

来源