[M6.3] Alerts and notifications

Open
  • Is something wrong?
#234 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
angular, typescript
Domain
backend, devops, frontend

Research direction

Start by reading SPEC 12 for the alert rule types and the implementations or tests for dependencies M6.1 and M6.2. Identify the alert paths and integration test entry points for the control plane and web UI, then check how test channels are configured. Done means every rule type fires in an integration test and delivers to a test channel across the listed email, Slack, Discord, Telegram, and webhook channels.

Written by the indexing model from the issue text.

Description

priority:P2 task track:control-plane track:web
Task id

M6.3

Track

C: control plane, W: web UI

Scope
  • Rule types from SPEC 12; channels email, Slack, Discord, Telegram, webhook.
Acceptance criteria

Each rule type fires in an integration test and delivers to a test channel.

Depends on

M6.1, M6.2

Dominant language
TypeScript
Stars
2
Forks
1
Avg merge
7h 17m
Merged PRs (30d)
197

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from shipkeepdev/shipkeep

All issues in shipkeepdev/shipkeep

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.