Skip to content

v1.1.1 — journal example; timestamp columns skipped

Choose a tag to compare

View all tags
@copyleftdev copyleftdev released this 02 Jun 01:18
· 4 commits to main since this release
v1.1.1
ff93a4f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Fixed

  • Timestamp columns are recognized as sequences and skipped by the value detectors. Role::Sequence required strict monotonicity, but real clock columns (journald __REALTIME_TIMESTAMP/__MONOTONIC_TIMESTAMP, a pcap timestamp) tie/regress, so they were treated as measurements — coll.cusum flagged their "level shift" (time advancing) and point their jumps. A timestamp/ts name token now classifies a column as sequence, kept narrow so response_time-style measurements are unaffected. cad.regularity stays role-agnostic, so --cadence timestamp still works. No config_version change.

Examples

  • examples/journal_anomalies.py — find anomalies in the systemd journal (point/structural/collective within a window, e.g. per-unit CPU-usage spikes; or _SYSTEMD_UNIT/PRIORITY distributional drift between windows via --baseline-since). Pipes journald JSON on stdin and maps findings back to timestamp/unit/message.
  • examples/stock_anomalies.py — (from the previous drop) Yahoo-Finance stock anomalies / drift.

Gate

cargo-mutants 0 missed on roles.rs; CI green.

Install: cargo install anomalyx

Full changelog: v1.1.0...v1.1.1

Assets 2
Loading