16 posts with tag #logging
Elasticsearch vs. OpenSearch vs. Loki vs. Quickwit vs. ClickHouse: Kubernetes Operations, Backup & DR
Setup, ingest, backup & DR, observability, and alerting for Elasticsearch, OpenSearch, Loki, Quickwit, ClickHouse 7-year log archives. Part 2 of 5.
Elasticsearch vs. OpenSearch vs. Loki vs. Quickwit vs. ClickHouse: Security & Compliance
Encryption, RBAC, and WORM compliance for log archives: Elasticsearch, OpenSearch, Loki, Quickwit, ClickHouse. S3 Object Lock, audit logging. Part 3 of 5.
ClickHouse Use Case: Vector, Istio, nginx, Java on OVH MKS
Vector → ClickHouse on OVH MKS: Envoy/Istio, nginx, Java, Go and Kubernetes logs with hot-to-cold S3 tiering. Monthly awffull reports via SQL export. Part 5 of 5.
Elasticsearch vs. OpenSearch vs. Loki vs. Quickwit vs. ClickHouse: UX, Dashboards & Alerts
UI layers, log search UX, cold-tier query behaviour, dashboard building, sharing, multi-team isolation, and alert management. Part 4 of 5.
Elasticsearch vs. OpenSearch vs. Loki vs. Quickwit vs. ClickHouse: Long-Term Log Archiving for 7+ Years
Five-way log archiving comparison: Elasticsearch, OpenSearch, Loki, Quickwit, ClickHouse — tiering, compression, query languages, SaaS options. Part 1 of 5.
vigil-log-relay: Kubernetes Log Collection Without a DaemonSet
vigil-log-relay streams logs from Kubernetes pods, HTTP endpoints, or Unix sockets and forwards them as ndjson to any TCP-capable log collector. No DaemonSet, no node-level access, no filesystem mounts — just a single binary with a namespace-scoped ServiceAccount.