LogTide v0.4.0 Released

[Polliog]

🌊 Welcome to LogTide (formerly LogWard)

This release marks our rebrand from LogWard to LogTide due to a trademark conflict. The new name reflects our mission: "Log" for what we
manage, "Tide" for the continuous flow of observability data.

📢 Read the full story behind the rebrand

✨ What's New

🔍 Substring Search Mode (#68)

• Find text anywhere: Search for partial matches in log messages (e.g., find "bluez" in "spa.bluez5.native")
• Two search modes: Full-text (word-based with stemming) and Substring (anywhere in message)
• Fast performance: Powered by PostgreSQL pg_trgm extension with GIN trigram index
• Admin configurable: Set default search mode system-wide

🖱️ Clickable Dashboard Elements (#67)

• Dashboard items are now interactive
• Click on recent errors, top services, etc. to navigate directly to filtered search results
• Improved workflow efficiency and discoverability

🐛 Enhanced Exception & Stack Trace Visualization (#23)

• Multi-language support: Auto-detect stack traces from Node.js, Python, Java, Go, PHP
• Structured parsing: File, line, function, and column information extracted
• Better UX: Syntax highlighting, exception type badges, collapsible frames
• Error grouping: Group similar exceptions by stack trace fingerprint with frequency tracking
• Copy support: Copy entire traces or individual frames

🗑️ Customizable Log Retention Policy

• Configure retention period per organization
• Admin UI for managing retention policies
• Background worker for automatic log cleanup

🔧 Improvements

⏰ Improved Custom Time Range Picker (#72)

• Time range fields pre-populated from recently used presets
• Values preserved when switching between preset and custom modes
• Quick adjustments without re-entering entire time range

🐛 Bug Fixes

📤 Export All Pages (#71)

• CSV/JSON export now includes all logs matching your filters
• Previously only exported the current visible page (~25 entries)
• No more manual merging of multiple exports

⚠️ Breaking Changes

Due to the rebrand, some configuration changes are required:

Environment Variables

Old	New
LOGWARD_PORT	LOGTIDE_PORT
LOGWARD_BACKEND_IMAGE	LOGTIDE_BACKEND_IMAGE
LOGWARD_FRONTEND_IMAGE	LOGTIDE_FRONTEND_IMAGE

Docker

• Container names: logward-* → logtide-*
• Network: logward-network → logtide-network
• Images: logward/backend → logtide/backend

Migration Guide

docker compose down                                                                                                                              
# Update .env with renamed variables                                                                                                             
docker compose pull                                                                                                                              
docker compose up -d  

✅ Data is preserved - no database migration needed

Full Changelog: https://github.com/logtide-dev/logtide/blob/main/CHANGELOG.md

Full Changelog: v0.3.3...v0.4.0

---

This discussion was created from the release v0.4.0.