Database Alarm

the database alarm subsystem furnishes real time security alerts whenever kron dam detects a database event that breaches an active alarm policy all evaluations are handled by the dam engine; production traffic is not interrupted, and all decision logic occurs within the proxy or local agent layer screen layout three coordinated tabs surface the entire workflow tab purpose typical actions history displays every alarm instance with full context review alarm details, acknowledge, or delete records policy hosts reusable alarm policies and rule sets enable/disable policies, edit rules, and assign notification targets notification targets stores' e mail / sms destinations add, edit, or retire targets alarms that reach the delivery threshold are saved in the history tab and dispatched to the linked targets through the internal noreply mail service each message reproduces the fields shown in the detail pane—id, level, repeat count, cause, and full trigger metric—thereby preserving forensic integrity