Escalated Notifications Update

[Felix772]

Describe your changes

Briefly describe the changes you made and their purpose.

I updated the monitor creation UI and validation to let users set up escalation rules — basically things like “after X minutes, notify this channel.” That’s now wired all the way through the system, including the frontend, backend types, and the Mongoose schema.
I also hooked escalation logic into the job engine. Now when an incident happens, it tracks how long the downtime has been, avoids sending duplicate alerts, and triggers escalation notifications at the right time. I added tracking for that too, so we store which escalations have already been sent.
On the backend side, I made a few reliability improvements — better MongoDB connection handling, a reusable SMTP setup for emails, added health checks, and support for persistent queue storage if needed.

Write your issue number after "Fixes "

Fixes #1

Please ensure all items are checked off before requesting a review. "Checked off" means you need to add an "x" character between brackets so they turn into checkmarks.

• [ x] (Do not skip this or your PR will be closed) I deployed the application locally.
• [ x] (Do not skip this or your PR will be closed) I have performed a self-review and testing of my code.
• [x ] I have included the issue # in the PR.
• I have added i18n support to visible strings (instead of <div>Add</div>, use):

const { t } = useTranslation();
<div>{t('add')}</div>

• [x ] I have not included any files that are not related to my pull request, including package-lock and package-json if dependencies have not changed
• [ x] I didn't use any hardcoded values (otherwise it will not scale, and will make it difficult to maintain consistency across the application).
• [x ] I made sure font sizes, color choices etc are all referenced from the theme. I don't have any hardcoded dimensions.
• [x ] My PR is granular and targeted to one specific feature.
• [ x] I ran npm run format in server and client directories, which automatically formats your code.
• [ x] I took a screenshot or a video and attached to this PR if there is a UI change.

[ajhollid]

Hi @Felix772 ,

Thanks for taking the time to work on the project.

Can you please resubmit this PR as two separate PRs, one for the backend implementation and one for the frontend implemetnation?

We'll review the backend implementation first and make sure it behaves as expected, then we'll review the frontend implementation after that.

This helps us keep PR sizes down and makes PRs much easier to review for us.

It also appears you may have started from an older branch and their have been changes since, so we have some merge conflicts here. Please rebase your changes as well before reopening.

Thank you!

[Felix772]

Hi Alexander, Here are the links to my new PRs. #3475 #3474 Best, Zaichen Hao

…

On Tue, Apr 7, 2026 at 1:02 PM Alexander Holliday ***@***.***> wrote: *ajhollid* left a comment (bluewave-labs/Checkmate#3468) <#3468 (comment)> Hi @Felix772 <https://github.com/Felix772> , Thanks for taking the time to work on the project. Can you please resubmit this PR as two separate PRs, one for the backend implementation and one for the frontend implemetnation? We'll review the backend implementation first and make sure it behaves as expected, then we'll review the frontend implementation after that. This helps us keep PR sizes down and makes PRs much easier to review for us. It also appears you may have started from an older branch and their have been changes since, so we have some merge conflicts here. Please rebase your changes as well before reopening. Thank you! — Reply to this email directly, view it on GitHub <#3468 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWCWO4FKD6CLSSAGX4BYHY34UUYBTAVCNFSM6AAAAACXOSTMYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMBQHAZDQNBWHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>