Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Critical or Warning Notification behaviors include reminders. #163

Closed
1 of 4 tasks
xellos00 opened this issue Jul 5, 2022 · 6 comments
Closed
1 of 4 tasks

Critical or Warning Notification behaviors include reminders. #163

xellos00 opened this issue Jul 5, 2022 · 6 comments
Assignees
Labels
type:discussion Issue that has to go over discussion. type:feature-request If there anyone has to raise a hand to request new feature. Vatz Project Name

Comments

@xellos00
Copy link
Member

xellos00 commented Jul 5, 2022

Checklist

  • New Feature for the SVC/Plugin
  • New Feature for CI/CD
  • Enhancement on Vatz
  • Others(etc. e.g, documentation,...)

Please describe, what it's about or related Problem with

A clear description of what feature need to be developed or enhanced in Vatz

Currently, VATZ is repeatedly sending alerts to the discord when a critical situation occurs.

  • This same alert can also cause you to miss the alerts you really need. So, in one problem situation, it would be better to change to one alert.
  • How does it has to send notification behave when there's no error on plugins and then
    • state is SUCCESS
    • severity is CRITICAL or WARNING

Describe the output that you are expecting for above

A clear and concise description of what you expect to happen.

Generate only one alert in one problem situation.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Because the database does not exist, the problem is solved by checking its contents with one variable.

Additional context

Add any other context or screenshots about the feature request here.

@xellos00 xellos00 added Vatz Project Name type:feature-request If there anyone has to raise a hand to request new feature. labels Jul 5, 2022
@xellos00 xellos00 added this to the Sprint 12 ( ~ 2022-07-06) milestone Jul 5, 2022
@xellos00 xellos00 added the type:discussion Issue that has to go over discussion. label Jul 5, 2022
@xellos00 xellos00 self-assigned this Jul 6, 2022
@xellos00
Copy link
Member Author

xellos00 commented Jul 6, 2022

  • AS-IS (문제 상황이면 메세지를 보낸다.)

    • CRITICAL -> every 6 seconds(CRITICAL 있을 때 계속 메세지를 보낸다.)
    • WARNING -> every 6 seconds
  • TO-BE (상태가 변화가 있으면 메세지를 보낸다.)

    • CRITICAL -> 문제가 발생했을 때만 Send alert! (Single time alert)
    • WARNING -> 문제가 발생했을 때만 Send alert! (Single time alert)
  • Final (상태의 변화가 있으면 메세지를 보낸다. 지난 번 Alert을 보낸 후, 일정 시간 이후 상태가 지속되면 Reminder� 보낸다.)

    • CRITICAL -> 문제가 발생했을 때만 Send alert ! (담당자가 시간을 설정 reminder)
    • WARNING -> 문제가 발생했을 때만 Send alert ! (담당자가 시간을 설정 reminder)

@xellos00
Register issue for TO-BE

@xellos00
Copy link
Member Author

xellos00 commented Jul 6, 2022

  • state == SUCCESS
  • severity == CRITICAL, WARNING

image


@xellos00
Register issue for CRITICAL, WANING
Refer to #174

@xellos00
Copy link
Member Author

xellos00 commented Jul 9, 2022

  • AS-IS (문제 상황이면 메세지를 보낸다.)

    • CRITICAL -> every 6 seconds(CRITICAL 있을 때 계속 메세지를 보낸다.)
    • WARNING -> every 6 seconds
  • TO-BE (상태가 변화가 있으면 메세지를 보낸다.)

    • CRITICAL -> 문제가 발생했을 때만 Send alert! (Single time alert)
    • WARNING -> 문제가 발생했을 때만 Send alert! (Single time alert)
  • Final (상태의 변화가 있으면 메세지를 보낸다. 지난 번 Alert을 보낸 후, 일정 시간 이후 상태가 지속되면 Reminder� 보낸다.)

    • CRITICAL -> 문제가 발생했을 때만 Send alert ! (담당자가 시간을 설정 reminder)
    • WARNING -> 문제가 발생했을 때만 Send alert ! (담당자가 시간을 설정 reminder)

@xellos00 Register issue for TO-BE

@Choi-Jinhong
Can you Create a issue regarding above?

@gnongs
Copy link
Member

gnongs commented Jul 11, 2022

  • AS-IS (문제 상황이면 메세지를 보낸다.)

    • CRITICAL -> every 6 seconds(CRITICAL 있을 때 계속 메세지를 보낸다.)
    • WARNING -> every 6 seconds
  • TO-BE (상태가 변화가 있으면 메세지를 보낸다.)

    • CRITICAL -> 문제가 발생했을 때만 Send alert! (Single time alert)
    • WARNING -> 문제가 발생했을 때만 Send alert! (Single time alert)
  • Final (상태의 변화가 있으면 메세지를 보낸다. 지난 번 Alert을 보낸 후, 일정 시간 이후 상태가 지속되면 Reminder� 보낸다.)

    • CRITICAL -> 문제가 발생했을 때만 Send alert ! (담당자가 시간을 설정 reminder)
    • WARNING -> 문제가 발생했을 때만 Send alert ! (담당자가 시간을 설정 reminder)

@xellos00 Register issue for TO-BE

@Choi-Jinhong Can you Create a issue regarding above?

Okay, I will create it.

@xellos00
Copy link
Member Author

  • AS-IS (문제 상황이면 메세지를 보낸다.)

    • CRITICAL -> every 6 seconds(CRITICAL 있을 때 계속 메세지를 보낸다.)
    • WARNING -> every 6 seconds
  • TO-BE (상태가 변화가 있으면 메세지를 보낸다.)

    • CRITICAL -> 문제가 발생했을 때만 Send alert! (Single time alert)
    • WARNING -> 문제가 발생했을 때만 Send alert! (Single time alert)
  • Final (상태의 변화가 있으면 메세지를 보낸다. 지난 번 Alert을 보낸 후, 일정 시간 이후 상태가 지속되면 Reminder� 보낸다.)

    • CRITICAL -> 문제가 발생했을 때만 Send alert ! (담당자가 시간을 설정 reminder)
    • WARNING -> 문제가 발생했을 때만 Send alert ! (담당자가 시간을 설정 reminder)

@xellos00 Register issue for TO-BE

@Choi-Jinhong Can you Create a issue regarding above?

Okay, I will create it.

@Choi-Jinhong
is this issue - #177?

@gnongs
Copy link
Member

gnongs commented Jul 20, 2022

  • AS-IS (문제 상황이면 메세지를 보낸다.)

    • CRITICAL -> every 6 seconds(CRITICAL 있을 때 계속 메세지를 보낸다.)
    • WARNING -> every 6 seconds
  • TO-BE (상태가 변화가 있으면 메세지를 보낸다.)

    • CRITICAL -> 문제가 발생했을 때만 Send alert! (Single time alert)
    • WARNING -> 문제가 발생했을 때만 Send alert! (Single time alert)
  • Final (상태의 변화가 있으면 메세지를 보낸다. 지난 번 Alert을 보낸 후, 일정 시간 이후 상태가 지속되면 Reminder� 보낸다.)

    • CRITICAL -> 문제가 발생했을 때만 Send alert ! (담당자가 시간을 설정 reminder)
    • WARNING -> 문제가 발생했을 때만 Send alert ! (담당자가 시간을 설정 reminder)

@xellos00 Register issue for TO-BE

@Choi-Jinhong Can you Create a issue regarding above?

Okay, I will create it.

@Choi-Jinhong is this issue - #177?

@xellos00 Yes, that's right

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:discussion Issue that has to go over discussion. type:feature-request If there anyone has to raise a hand to request new feature. Vatz Project Name
Projects
None yet
Development

No branches or pull requests

2 participants