Problem / Motivation
Users often discover issues only after manually checking logs. There is currently no proactive way to detect critical situations such as sudden spikes in errors or the appearance of new error patterns. This limits Logport’s usefulness during incidents and reduces its value as an operational tool.
Proposed Solution
Introduce a basic alerting system focused on the most common and actionable scenarios:
- Alert when error count exceeds a defined threshold within a time window
- Alert when specific log patterns appear
Alerts should be evaluated periodically (pull-based) and scoped per service. Configuration should be simple, with minimal tuning required, and alerts should trigger notifications via configured notification providers.
Alternatives Considered
No response
Additional Context
Problem / Motivation
Users often discover issues only after manually checking logs. There is currently no proactive way to detect critical situations such as sudden spikes in errors or the appearance of new error patterns. This limits Logport’s usefulness during incidents and reduces its value as an operational tool.
Proposed Solution
Introduce a basic alerting system focused on the most common and actionable scenarios:
Alerts should be evaluated periodically (pull-based) and scoped per service. Configuration should be simple, with minimal tuning required, and alerts should trigger notifications via configured notification providers.
Alternatives Considered
No response
Additional Context