Releases: log-forge/logforge
V2.0.1 Support for more architecture and a few new features
Fixes Implemented for the following:
Addressed Notifier: SMTP URL Normalization (issue #21)
Addressed missing libraries on certain architectures (issue#23 and discussions#22)
Additional features:
- filter by stack
- create groups via filters
- Batch monitoring on/off for groups
- See how many containers are being monitored in a group in the UI
Note: on machines with insufficient resources, monitoring a lot of containers can result in performance issues. This release does not have optimizations as part of it, but the next major release will. With that in mind, we caution users to the use of the new batch monitoring feature for now.
LogForge 2.0.0 - Alert Engine, UI-first rules, safe auto-remediation
Highlights
- Alert Engine: rules on logs, container events, and performance thresholds
- Safe auto-remediation: restart, stop, kill, start, or run script with guardrails
- UI-first setup: create and manage rules, actions, and notifications in the UI
- One-click templates: stability, performance, logs, and security scenarios
- Real-time experience: live alerts, container updates, and health snapshots
- Core is source-available: backend that talks to the Docker socket is fully inspectable
What's New
- Rules engine
- Triggers: keyword matches in logs, container lifecycle events; metric thresholds in Pro
- Timelines: N times in M minutes and sustained for X minutes
- Scoped rules: global, by container, or by group
- Multi-step actions: chain actions with optional delays
- Safe automation
- Guardrails: cooldowns, exponential backoff, rate limits, verification delays
- Temporary disable after repeated failures to prevent loops
- Templates and duplication checks
- Ready-made rule templates with simple customization
- Duplicate rule protection warns on overlapping rules
- Alert history and acknowledgements
- Clear history with pagination and quick totals
- Acknowledge alerts to hide until new activity
- Noise controls
- Case sensitivity, any or all keyword matching, and ignore lists
- Test and health
- Test notifications from the UI
- Health endpoints and live counts for rules, alerts, and containers
Images
- madanb13/logforge-backend:v2.0.0
- madanb13/logforge-frontend:v2.0.0
- madanb13/logforge-notifier:v2.0.0
- madanb13/logforge-alert-backend:v2.0.0
- madanb13/logforge-alert-frontend:v2.0.0
- madanb13/logforge-autoupdate:latest
Improvements
- implemented caching for log view
- improved alerts interface
- improved warning pill
Core Source-Available
-
The LogForge Core backend interfaces directly with the Docker socket. Core is source-available so you can review exactly what runs with that level of access.
-
Thanks to early users who tested builds, shared feedback, and suggested rule templates. Logforge is actively being developed, we expect things to come up and appreciate everyone who lets us know.
GROUPING, Toggle Container monitoring status and Alert interval control
🚀 LogForge v1.0.2
Release date: 2025-07-18
What’s New
🆕 Grouping Functionality
Easily organize and view containers by group for faster navigation and streamlined monitoring.
⏱️ Customizable Interval Checks
Control how often LogForge checks your containers. Now supports:
- 10 seconds
- 30 seconds
- 1 minute
- 5 minutes
- 10 minutes
- 30 minutes
Default is set to 30 secs.
🔀 Toggle Container Monitoring
You can now choose which containers are actively monitored directly from the dashboard. Disable monitoring for any container at any time.
Default is to not monitor a container on startup.
🟢 Seamless Data Migration
Moving to the latest version? All your existing data and settings will migrate automatically—no manual steps required.
💡 Upgrade Notes
- Existing LogForge users: Update your stack and all your settings and alert/logs will be preserved.
- As always, report any issues via GitHub Issues.
🛠️ Full Changelog
- Added container grouping for improved organization
- Added monitoring interval controls (10s, 30s, 1m, 5m, 10m, 30m)
- Added per-container monitoring toggle
- Implemented seamless, automatic data migration for all upgrades
Try it out now — feedback and PRs welcome!
Persistency + general improvements
Highlights
- terminal enhancements
- persistency for settings
- revamp of notifications UI (Quality/ease of life changes),
- added additional support for many popular notification channels
- significant reduction in overall size
- fixed parsing for ANSI code in logs
- implemented more robust parsing for datetime
- Calendar to query logs along timeline now works
Initial Stable Release - File Browser, Terminal, Notifications and Alerts
🚀 LogForge v1.0.0 — Initial Stable Release
We're proud to release LogForge v1.0.0, the first stable version of our self-hosted service monitoring dashboard built for developers. After weeks of iteration, LogForge is now ready for real-world usage with a focus on fast-moving teams and startups — stay confident in production-like dev environments, and iterate quickly.
Minimal overhead. Zero config. Get started in seconds, scale as needed — no learning curve.
✨ Highlights
-
Docker & System Monitoring
- Auto-detect Docker containers
- View health and metadata on UI
-
Real-time Log Viewer
- Live streaming logs via WebSocket
- Filter logs in UI
- Set (global) Alert keywords (Case-sensitive matching)
-
Alerts & Notifications
- Trigger alerts via keyword matches in logs
- Alert visibility in Web UI
- AI-Assisted Summaries alongside alert notifications (Toggle)
- Alert messages highlighted in red in log viewer
- Separate UI tab to view all caught alerts
- Send alerts to: Discord, Slack, Telegram, Gotify and Email
-
Modern UI
- Clean intuitive interface
- Dark/light mode support
-
Built-in Terminal
- Direct command-line access per container
-
File Browser
- Browse container file systems
LogForge for teams
We're working on LogForge Pro — an optional premium tier with advanced functionality for power users and teams:
-
RBAC (Role-Based Access Control)
Granular permission management for teams and organizations -
Per-Container Keyword Configuration & Notifications
Define custom alert keywords and notification rules for each container independently -
Extended Log Retention
Retain logs beyond 7+ days with historical access and search support -
Cloud Sync & Multi-Device Access
Secure cloud backup of your config and alert history — access LogForge across multiple machines -
Custom Notification Channels
Send alerts to your additional preferred platforms for any webhook — fully configurable per container -
🤖 AI for Your Containers (Private, Local) (experimental)
Imagine Cursor, but embedded directly into each Docker container.
-
Container-Specific AI Agent
Each container gets its own scoped AI agent — it only sees logs and metadata from that container -
Contextual Log Summaries
Quickly understand what went wrong — “This service crashed due to a DB timeout after 3 retries” -
Anomaly Detection
Spot unusual behavior in logs before it becomes a critical issue -
Fix Suggestions
AI-powered recommendations based on logs: “You may want to increase your timeout or check database connectivity” -
Private by Default
Runs locally. No data leaves your server unless you enable external sync
-
