Fix notification system with proper rate limiting and aggregation
All checks were successful
Build and Release / build-and-release (push) Successful in 1m51s
All checks were successful
Build and Release / build-and-release (push) Successful in 1m51s
- Add rate limiting using rate_limit_minutes config (was ignored) - Add aggregation using aggregation_interval_seconds config (was ignored) - Use smtp_host and smtp_port from config (was hardcoded localhost:25) - Add trigger_on_warnings and trigger_on_failures config options - Add recovery_requires_all_ok and suppress_individual_recoveries - Use check_interval_seconds from config (was hardcoded 30s) - Expand status tracking to all components (drives, pools, services, backup) - Move notification checks from every collection to dedicated interval - Separate alert and recovery notifications with proper email formatting - Only notify on failed services (Critical), not inactive
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
[package]
|
||||
name = "cm-dashboard-agent"
|
||||
version = "0.1.275"
|
||||
version = "0.1.277"
|
||||
edition = "2021"
|
||||
|
||||
[dependencies]
|
||||
|
||||
Reference in New Issue
Block a user