📣 Updated Status of CheckCle Implementation

[tolaleng]

Hi everyone

I'd like to share the current progress on the implementation of CheckCle. Our backend currently runs on Go (powered by PocketBase), and I am extending the architecture with an additional Go-based service to enhance functionality (Separately from Pocketbase).

1. Server-Side Check Logic
   Moving the existing check logic from the client side to the server side. This includes expanding support for various check types:
   • HTTP
   • TCP
   • Ping
   • DNS

2. Distributed Regional Checks
   I’ve decided to implement support for distributed regional checks.
   In this architecture:
   • The CheckCle server acts as the Central Control Plane.
   • Regional Check Agents (Probes) are deployed on servers across different regions to perform checks from diverse locations.
   This will improve reliability and help detect region-specific outages or latency issues. Thanks @michaelortnerit @apologist for the ideas and suggestion.

3. Server Instance Monitoring
   We're also implementing agent-based server instance monitoring.
   In the first phase, this will support a single agent (no regional checks), focusing on collecting metrics like CPU, memory, disk, and network.

I'm open to any further suggestions or ideas you may have, feel free to share!

[michaelortnerit]

Very nice to hear, that you working on Distributed Regional Checks. This would be the first project i know which implements it! Thank you for your hard work.

[tolaleng]

I'm excited to announce that the Distributed Monitoring Agent has been fully implemented and is now ready for deployment across all regional servers.

Deploying the Regional Monitoring Agent
The Current Distributed Regional Monitoring system is designed to be easily deployed to any regional server. The Regional Monitoring Agent supports operational checks such as HTTP, PING, TCP, and DNS.

Steps to Set Up and Use the Regional Monitoring Agent
1. Install the Regional Monitoring Agent

• Use our one-click install command.
• Copy and paste the command into your target regional server and execute it.

2. Verify Agent Status

• Once the installation command has been successfully executed, the Regional Monitoring Agent will appear online.
• By default, you will see an agent listed as Default Agent (ID: 1), which serves as the default monitoring service.

3. Assign the Agent to a Service

• Navigate to the Uptime Monitoring Service section.
• Assign the Regional Monitoring Agent to a service (e.g., HTTP, TCP, PING, or DNS).

4. View Monitoring Data

• Go to the Service Detail Dashboard.
• You will see two agents listed: the Default Agent and the Regional Agent.
• In the Response Time History section, data from both agents will be displayed for comparison.

5. Switch Between Monitoring Sources

• In the Service Detail Dashboard, locate the Source Monitoring dropdown.
• Use this dropdown to filter and view data from either the Default or Regional monitoring source.

Note:

• The Default Agent is automatically assigned to all services. You do not need to manually assign it (The Default Agent is always active and automatically assigned to all services.)
• To avoid confusion, the Default Agent will no longer be shown in the assignment list (I will remove it)
• The Regional Agent will only begin checking a service after it is explicitly assigned.

[tolaleng]

Hello everyone

I’ve just released the core features in v1.4.0, including Uptime Monitoring, Server Monitoring, Distributed Monitoring, and Agent support. 🎉

However, the notification system isn’t fully complete yet. I’m actively working to make notifications fully functional and feature-rich.
Please stay tuned, the notification feature is planned for release by the end of this month!

Thank you all for your contributions and support!