Skip to content

v1.3.1

Choose a tag to compare

View all tags
@Polliog Polliog released this 17 Aug 12:08
· 11 commits to main since this release
v1.3.1
50cac85
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

LogTide 1.3.1 ships the five community-requested dashboard panel features (#296-#300, all by @SemoTech), expands email digests to fifteen toggleable sections, and fixes MongoDB span sorting.

Highlights

Custom dashboards (#296-#300)

  • Per-panel pause (#296): every panel gains a Pause/Resume toggle; paused panels are skipped by auto-refresh and batch fetches (with everything paused no network call is made), manual refresh still works, and a paused live Log Table freezes its rows while keeping the socket alive
  • Display preferences (#297): new Settings > Display card with 12h/24h clock and explicit IANA timezone, honored by all custom-dashboard panel timestamps; browser timezone and 24h remain the defaults
  • Live Log Stream rows (#298): maxRows cap raised from 50 to 100, matching the Log Table panel
  • Top-N metadata dimension (#299): top_n_table panels can rank any flat metadata key (e.g. GeoIP geo_place) with limit up to 50, optional level/service filters and a Last seen column; reservoir topValues learned includeLastSeen on TimescaleDB, ClickHouse and MongoDB
  • Time series labels (#300): time_series panels accept optional per-level seriesLabels (e.g. info -> "Heartbeat"); legend and tooltip use them, falling back to Debug/Info/Warn/Error/Critical

Email digests

  • Fifteen toggleable sections: daily/weekly digests can now report on every vertical, with ten new sections (log level breakdown, top error messages, traces, metrics, alerts, security activity, monitor performance, usage and quota warnings, webhook deliveries, team activity). New sections are off by default and configurable per organization in Settings > Email Digests; the original five keep their content and stay on by default. Disabled sections cost zero queries
  • Generation performance: reservoir window pairs and per-project span health lookups run in parallel, the usage section dropped discarded per-project scans, and MongoDB gained a (project_id, duration_ms) span index for the slowest-spans read

Fixed

  • MongoDB span sorting: span queries now accept the same sort fields as TimescaleDB and ClickHouse (duration_ms, end_time, service_name, operation_name); previously any sort other than start_time/time was silently ignored, which would have rendered "slowest spans" as most-recent on Mongo

Full detail in CHANGELOG.md.

Contributors

SemoTech
Assets 2
Loading