This release adds 6 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
+9 more
Summary
AI summaryFive new source adapters (Docker, systemd journal, SSH, Loki, Graylog) and OpenSearch tail support enable direct log ingestion.
Full changelog
Logatory 0.3.0
This release is all about getting logs in. Since 0.2.0, Logatory gained
five new source adapters — point it at wherever your logs already live
instead of exporting a file first. Every new source supports both a one-shot
scan and a realtime tail, and runs the full pipeline: PII
redaction, the detection rule engine, error tracking, and webhook alerts.
New source adapters
- Docker — read container logs straight from the Docker daemon, no log
stack required.logatory docker scan·logatory docker tail
(needspip install 'logatory[docker]') - systemd journal — read journald via
journalctl.
logatory journald scan·logatory journald tail - Remote hosts over SSH — pull logs from any SSH-reachable server with no
agent, no open port, no daemon — with automatic reconnect.
logatory ssh scan·logatory ssh tail - Grafana Loki — query a Loki instance with a LogQL selector.
logatory loki scan·logatory loki tail - Graylog — query a Graylog server via its search API.
logatory graylog scan·logatory graylog tail
The journald, SSH, Loki and Graylog adapters need no extra dependency.
Also new
opensearch tail— realtime polling of an OpenSearch / Elasticsearch
index for newly-arrived events.
Install / upgrade
pip install --upgrade logatory
Full changelog: https://github.com/T0nd3/logatory/compare/v0.2.0...v0.3.0
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About Logatory
All releases →Related context
Related tools
Beta — feedback welcome: [email protected]