This release adds 3 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
+9 more
Summary
AI summaryUpdates The fleet, Also, and Dashboard across a mixed release.
Full changelog
Logatory 0.4.0
Fleet — monitor a whole set of log sources at once.
Until now each command read a single source. 0.4.0 adds Fleet: declare all
your log sources in one targets.yaml — each can be a file, journald, Docker,
an SSH host, OpenSearch, Loki or Graylog — and work them together.
The fleet
logatory fleet init— an interactive wizard that buildstargets.yaml
for you; credentials are stored as${ENV_VAR}references, never in plain
text.logatory fleet scan— scan every target once, concurrently. A target
that fails is reported without aborting the run.logatory fleet tail— follow the whole fleet in real time: each target
is polled in its own thread and merged into one stream, with a findings-only
default and a periodic heartbeat. One host dropping out doesn't stop the rest.logatory fleet list— list the configured targets;--checkprobes
each one for reachability.- Select subsets of the fleet with
--target/--group.
Dashboard
- A new Fleet page lists the targets and offers an add-target form with
per-type fields — a browser-based editor fortargets.yaml. - The Findings and Errors pages gain a target/group filter, populated from
yourtargets.yaml.
Also
- Findings and errors now carry the originating fleet target, persisted to
SQLite — existing databases migrate automatically. /api/docsnow documents only the public REST API, not dashboard internals.
Install / upgrade
pip install --upgrade logatory
Full changelog: https://github.com/T0nd3/logatory/compare/v0.3.0...v0.4.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]