Skip to content

Feat: Create escalation protocol with timed alerts and email notifications#8

Merged
dach3n merged 1 commit intodevelopfrom
escalation-protocol
Apr 8, 2026
Merged

Feat: Create escalation protocol with timed alerts and email notifications#8
dach3n merged 1 commit intodevelopfrom
escalation-protocol

Conversation

@dach3n
Copy link
Copy Markdown
Owner

@dach3n dach3n commented Apr 8, 2026

Describe your changes

Created an escalation protocol for continuous alerts for persistently stopped monitors. Sends alerts as an incident lasts until user-defined intervals.

Write your issue number after "Fixes "

Fixes ramfam101#123

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.

  • (Do not skip this or your PR will be closed) I deployed the application locally.
  • (Do not skip this or your PR will be closed) I have performed a self-review and testing of my code.
  • 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>
  • 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
  • I didn't use any hardcoded values (otherwise it will not scale, and will make it difficult to maintain consistency across the application).
  • I made sure font sizes, color choices etc are all referenced from the theme. I don't have any hardcoded dimensions.
  • My PR is granular and targeted to one specific feature.
  • I ran npm run format in server and client directories, which automatically formats your code.
  • I took a screenshot or a video and attached to this PR if there is a UI change.

@dach3n dach3n merged commit 297bbb7 into develop Apr 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant