[Feature]: Uptime Kuma Metrics for Landing page

---

Note

You can now preview the latest updates and improvements every 2–3 days at the following link: 👉 Helixque-Changes

Describe the feature you'd like
Add a self-hosted uptime and incident monitoring stack using Uptime Kuma to track the availability and latency of Helixque’s core services, publish a public status page, and send real-time alerts to the team’s Discord.​ Monitors should cover the web app, API, signaling service, realtime gateways, DNS, certificates, and network reachability using supported HTTP(S), TCP, Ping, DNS, keyword, and JSON-query checks at short intervals.​

Describe alternatives you've considered

• Upptime (GitHub Actions based): free, Git-only status site and incident automation with 5-minute checks and GitHub Pages status page.​
• Grafana + Prometheus Blackbox Exporter: flexible blackbox probing and dashboards, but requires Prometheus and Grafana management.​
• Better Stack (Better Uptime): hosted monitoring and status pages with incident workflows and rapid setup.​

Additional context
Uptime Kuma supports multiple monitor types, notification channels including Discord, and multiple status pages, making it well-suited for a self-hosted SRE-first setup.​ A Docker-based deployment exposes a web console for configuring checks, notifications, SSL monitoring, and public status pages with minimal operational overhead.

---

Prerequisite Checklist

• ⭐ Starred Helixque Repo
• ⭐ Starred Helixque Landing Repo
• 📘 Read and understood Contributing Guidelines
• 💬 Joined Discord Channel
• 🌐 Explored and signed up on helixque.netlify.app

---

✅ Issues will be assigned once all checklist prerequisites are verified.

[!IMPORTANT]

🛑 Contribution Guidelines — Please Read Before Proceeding

• Any PR raised for an unassigned issue (even if the issue number is mentioned in the PR) will not be merged and will be closed automatically.
• If your issue is valid but not yet assigned, please ping the Project Maintainers in the Discord Channel to get it assigned before starting work or submitting a PR.
• Only Code Owners or Project Maintainers have the authority to verify, approve, and assign issues.
• Do not self-assign issues — any self-assigned issue will be reviewed, and the final decision will rest with the Code Owners.

Thank you for helping shape HelixQue’s future this Hacktoberfest 🙌

Note

You can now preview the latest updates and improvements every 2–3 days at the following link: 👉 Helixque-Changes