# loggie-io/loggie

A lightweight, cloud-native data transfer agent and aggregator

Repository: https://github.com/loggie-io/loggie
Canonical: https://ross.abutalabs.com/products/loggie
Homepage: https://loggie-io.github.io/docs-en/
Language: Go
License: Apache-2.0
License Family: permissive
Topics: log, agent, kubernetes, cloudnative, opentelemetry
Last push: 2024-07-25T03:17:22+00:00

## Health v2 (maintenance only)
Score: 23/100 (v2, computed 2026-09-03T02:39:23.370411+00:00)
- activity 0, release rhythm 8, longevity 100
- inputs: {"age_days": 1746, "days_push": 769, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1333, forks 184 (observed 2026-08-28T04:04:24.564445+00:00)

## What it is
Loggie is a lightweight, high-performance, cloud-native log collection agent and aggregator written in Go. It uses Kubernetes CRDs to configure data pipelines with pluggable source, interceptor, and sink components, and can be deployed as a DaemonSet agent, sidecar, or standalone aggregator.

## Use cases
- collect container logs from kubernetes pods without mounting volumes
- ship log files to kafka or elasticsearch
- aggregate logs from multiple agents into a central pipeline
- parse and filter log events before sending to a sink
- set up log-based alerting with prometheus metrics
- auto-inject log collection sidecars into deployments
- build a cloud-native log data platform

## When to choose
- you run workloads on kubernetes and want CRD-driven log collection
- you need high-throughput log shipping with low resource usage
- you want pluggable pipelines for collecting, transforming, and routing log data
- you need agent, sidecar, and aggregator deployment modes in one tool

## When to avoid
- you need a general-purpose metrics or tracing collector rather than log/event data
- you want a fully managed SaaS logging solution
- your environment is not kubernetes-centric and you prefer simpler agents like fluent-bit
- you need long-term log storage and search built in

## Facets
- artifact type: service
- maturity: active
- function: logging, monitoring, streaming, etl, alerting
- domain: monitoring, cloud-computing
- platform: go, self-hosted
- tags: log-collection, log-agent, daemonset, sidecar, aggregator, crd, opentelemetry, kubernetes-operator, devops, containers, kubernetes, docker, linux

## Member repositories
- loggie-io/loggie (main) score 23

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:24.564445+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T04:44:47.636030+00:00, confidence not recorded.
  - readme: https://github.com/loggie-io/loggie (fetched 2026-08-28T04:04:24.564445+00:00, sha 9a96fde7e1a2)
  - homepage: https://loggie-io.github.io/docs-en/ (fetched 2026-08-29T12:03:57.723024+00:00, sha 720b9f26134f)
- Data as of 2026-08-30T08:39:29.467469+00:00.
