log-forge/logforge v2.0.0 on GitHub

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

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

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.