Notification Enhancements include reminder

[xellos00]

1. Type of change

Please delete options that are not relevant.

• New feature
• Enhancement
• Bug/fix (non-breaking change which fixes an issue)
• others (anything other than above)

---

2. Summary

Please include a summary of the changes and which issue is fixed or solved.

Related: # (issue)
close #174
close #246

Summary

1. Send Notification when flags(State + Severity) have changed from previous results.
2. Reminder to recover is stop when state: SUCCESS, Severity: INFO
3. When Plugin is Down filter from health check
   Health Check only Sent Single Message that Plugin is Down.
   Will be covered on other issue for health Check Reminder.

State	Severity	Send Notification (Y/N)	Reminder (Y/N)
SUCCESS	WARNING	Y	Y
SUCCESS	CRITICAL	Y	Y
SUCCESS	INFO	Y	N
FAILURE	*	Y	Y
ANY OTHER	*	N

---

---

3. Comments

Please, leave a comments if there's further action that requires.

[rootwarp]

LGTM

rootwarp@Mindhack2021 ~/g/d/vatz ISSUE-174-revised > make coverage
echo "Test Coverage script will be here"
Test Coverage script will be here
ok      github.com/dsrvlabs/vatz        3.425s  coverage: 11.0% of statements
ok      github.com/dsrvlabs/vatz/manager/api    1.667s  coverage: 0.0% of statements [no tests to run]
ok      github.com/dsrvlabs/vatz/manager/config 1.603s  coverage: 95.0% of statements
ok      github.com/dsrvlabs/vatz/manager/dispatcher     2.007s  coverage: 8.9% of statements
ok      github.com/dsrvlabs/vatz/manager/executor       2.427s  coverage: 68.2% of statements
ok      github.com/dsrvlabs/vatz/manager/healthcheck    2.676s  coverage: 45.0% of statements
?       github.com/dsrvlabs/vatz/manager/types  [no test files]
?       github.com/dsrvlabs/vatz/mocks  [no test files]
ok      github.com/dsrvlabs/vatz/rpc    4.016s  coverage: 65.5% of statements

[gnongs]

@xellos00
I think parse_made is not work.

2022-10-07T18:00:23+09:00 ERR dispatcher CH: Telegram-Invalid telegram token. module=dispatcher

When I remove this valuable, It is work.

below log is return body.

{"ok":false,"error_code":400,"description":"Bad Request: can't parse entities: Can't find end of the entity starting at byte offset 96"}

[xellos00]

@gnongs
I cloned again with main branch after merge and I confirmed it works preperly.
Can you compare your telegram message to below, your message is not in formatted as markdown.

Can you raise another issue with your case above if you still have same trouble with new cloning or after pull latest commits
just Keep in mind that when you share your configs on issue, you need to blur all your secret to prevent other trouble.

[gnongs]

@xellos00 I have noted the issue below.

• dispatcher CH: Telegram-Invalid telegram token. #262

[heejin-github]

Send Discord alert as we expected. 👍

1. plugin down

• send CRITICAL when it down
• send only once not repeated.
• send INFO when it recover

2. Send Notification from plugin

• send alert as determined severity by plugin
• send alert repeated by reminder schedule
• send INFO when it recovered
• reminder is stop when its state : SUCCESS, severity : INFO

repeated by reminder schedule (every minute in this case)

send alert WARNING -> CRITICAL -> WARNING well.
send INFO when it recovered, and it didn't repeated to send INFO level notification.