Notification of Important Status Changes in Monitored Services

[minhhoangvn]

Title: Notification of Important Status Changes in Monitored Services

Story:
As a non-technical user who values the reliability of our monitoring system, I want to receive notifications when important status changes occur in our monitored services. These notifications will help me stay informed about the health of our services without delving into technical details.

Acceptance Criteria:

1. I expect to receive notifications when there is a significant change in the status of our monitored services.

2. The system will use an "isImportantBeat" function to evaluate the status changes during monitoring.

3. An "important beat" is determined by specific conditions:

   • If it's the first beat of monitoring for a service, it's considered important.
   • If a service goes from an "UP" to "DOWN" status, this change is considered important.
   • If a service goes from "DOWN" to "UP," this change is considered important.
   • If a service goes into or comes out of "MAINTENANCE" mode, these changes are considered important.
   • Other status changes, such as "UP" to "PENDING" or "PENDING" to "DOWN," are not considered important for notifications.

4. When an important status change occurs based on the defined criteria, the system will send me a notification to keep me informed.

Definition of Done:

• I receive notifications when there are significant status changes in our monitored services.
• Notifications are sent based on the criteria defined in the "isImportantBeat" function.
• I am only notified of status changes that are considered important, as described in the acceptance criteria.

This user story aims to provide non-technical users with a clear and user-friendly way to receive important notifications about the status changes of monitored services, allowing them to stay informed about the health of the services without needing to understand the technical details of the system.