Add notifications to Infrastructure Monitoring

[gorkem-bwl]

Just like uptime monitoring, Slack/Discord/Telegram/Webhook notifications should be a part of Infra monitoring.

[PaulyBearCoding]

I'd like to work on this issue as my first contribution. Please assign it to me if it's still available.

[gorkem-bwl]

I'd like to work on this issue as my first contribution. Please assign it to me if it's still available.

Hello. Sure. Since it's not a small feat, can you please let us know how you are going to implement it on a high level, pointing out to necessary blocks/codebases? Then we can move ahead.

[PaulyBearCoding]

Hey @gorkem-bwl — thanks for the ping! Here’s how I’d tackle adding notifications:

1. Notifier interface
   In pkg/notifications, define:

   type Notifier interface {
     Notify(event Event) error
   }

Event should include things like service name, status, timestamp, etc.

Provider adapters

Slack (pkg/notifications/slack)

Discord (pkg/notifications/discord)

Telegram (pkg/notifications/telegram)

Webhook (pkg/notifications/webhook)

Config changes
I'd add this to the config.yaml:

notifications:
slack:
enabled: true
webhook_url: https://hooks.slack.com/…
discord:
enabled: false
telegram:
enabled: true
bot_token: ABC123
chat_id: 98765
webhook:
enabled: true
url: https://example.com/webhook

CLI flags
In cmd/infra-monitor, add flags like:

bash
Copy
Edit
--config /path/to/config.yaml
--enable-notifications
Tests

Unit tests for each notifier (mock HTTP).

End-to-end test simulating a status change.

Docs
Update docs/infra-monitor.md with setup steps and example payloads.

Let me know if you'd like me to proceed.

[gorkem-bwl]

@PaulyBearCoding I think it may be better for you to check other Github projects. Checkmate is a complex project and needs an understanding/reading of underlying codebase before really starting with anything.

[PaulyBearCoding]

@PaulyBearCoding I think it may be better for you to check other Github projects. Checkmate is a complex project and needs an understanding/reading of underlying codebase before really starting with anything.

Thanks for the feedback, @gorkem-bwl! 🙏 I definitely want to get up to speed on the Checkmate codebase before jumping in.

Could you point me toward:

1. Any high-level architecture or design docs?
2. The key packages/modules I should start reading (e.g. the monitoring loop in pkg/monitor)?
3. Any suggested workflows (tests to run locally, useful hints in CONTRIBUTING.md, etc.)?

Once I’ve got a feel for those areas, I can open small PRs—whether it’s improving docs, adding tests, or scaffolding the notifications package—and build from there.

I just want to learn more and contribute.

[gorkem-bwl]

@PaulyBearCoding I think it may be better for you to check other Github projects. Checkmate is a complex project and needs an understanding/reading of underlying codebase before really starting with anything.

Thanks for the feedback, @gorkem-bwl! 🙏 I definitely want to get up to speed on the Checkmate codebase before jumping in.

Could you point me toward:

1. Any high-level architecture or design docs?
2. The key packages/modules I should start reading (e.g. the monitoring loop in pkg/monitor)?
3. Any suggested workflows (tests to run locally, useful hints in CONTRIBUTING.md, etc.)?

Once I’ve got a feel for those areas, I can open small PRs—whether it’s improving docs, adding tests, or scaffolding the notifications package—and build from there.

I just want to learn more and contribute.

Hello. I can confidently say that Checkmate is a large project, and is not for beginners, unfortunately.