Health Checker that notify every VATZ is up and running properly.

[xellos00]

Checklist

• New Feature for the Service/Plugin (Vatz)
• Enhancement (Vatz)
• others(etc. e.g, documentation, project policy management)

---

Is your feature request related to a problem? Please describe.

A clear and concise description of what the problem is. such as Ex. I'm always frustrated

I'm always frustrated with currently there's no checker or notification VATZ is running to discord.

Describe the solution you'd like| Ex

A clear and concise description of what you want to happen

Send a notification to protocol channel to notify to Validator team

• whether it is up and running

Describe alternatives you've considered

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

Additional context or comment

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

the health check was similar to the alert reminder. Because Health check means vatz can send the INFO alert again. So we tried to develop the health check when the alert reminder developed.

[xellos00]

기존의 Node-manager 한국시간 10:03 reminder가 옵니다.
Requirements

1. crontab 과 같은 schedule이 가능하게 해주세요.
2. 예를 들어 go-cron과 같은 package가 있습니다. 참고해 주세요.

---

@heejin-github, @kim201212

There's no function in VATZ as same as above.

1. Update label to create alive
2. development

[kim201212]

@heejin-github and I decided to develop a function to send metric information using promethus first and make a health checker.

Prometheus issue : #169

[xellos00]

@heejin-github and I decided to develop a function to send metric information using promethus first and make a health checker.

Prometheus issue : #169

@heejin-github
@kim201212

Let's separate issue two things, I do not want to dup issue.
As I mentioned in #169 (comment)

[heejin-github]

@heejin-github and I decided to develop a function to send metric information using promethus first and make a health checker.
Prometheus issue : #169

@heejin-github @kim201212

Let's separate issue two things, I do not want to dup issue. As I mentioned in #169 (comment)

@xellos00
As I mentioned in #169 (comment), it's already separated.
We'll NOT handle any prometheus related issues or discussion in this issue.