apache / apache/hertzbeat

[Task] <Suggestions for improving the alarm notification policy>

Open
#1,169 0 comments 2 reactions 0 assignees View on GitHub
status: volunteer wanted
Dominant language
Java
Stars
7.4k
Forks
1.3k
Avg merge
1d 20h
Merged PRs (30d)
32

Description

### Description

Alarm notification policy for this scenario: Alarms affecting database operation shall be sent to Party A, row lock and deadlock of database shall be sent to development and rectification, unavailable monitoring shall be sent to DBA for troubleshooting, or problems involving different businesses in the same set of database shall be sent to contact persons of different departments for handling. It is recommended that you add an alarm with a corresponding ID when adding an alarm to the threshold alarm. Then you can select a specific alarm ID when configuring the notification policy and send it to the corresponding personnel for processing

### Task List

_No response_

Contributor guide

Open the contributing guide

Research direction

No file, test, or entry point is named in the issue. First map the existing threshold-alarm and notification-policy flows, then define how alarm IDs are assigned and selected for routing to the specified personnel; done means each described alarm category can target its corresponding recipients.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.