How trungtq-ai-transform/checkcle works
CheckCle is a full-stack monitoring platform. Users manage monitored services and infrastructure in the web console; the platform collects monitoring results, presents health and history, and supports incident response and public status reporting. The frontend also exposes SSL, regional monitoring, maintenance, and administrative settings. The README documents notification channels and analytics as capabilities, but the sampled files do not establish their full runtime wiring. Backend worker detail is likewise limited to startup orchestration and selected services.
Main entry points: App.tsx Web app routes · app.go PocketBase · main.go Monitoring workers · services Service views
Components 23
Web console
- Web app routes
application/src/App.tsx - Authentication
application/src/services/authService.ts - Dashboard
application/src/components/dashboard - Service views
application/src/components/services - Service actions
application/src/components/services/hooks/useServiceActions.ts - Service detail data
application/src/components/services/ServiceDetailContainer/hooks/useServiceData.tsx - Administration
application/src/components/settings
Monitoring domains
- Uptime history
application/src/services - Regional monitoring
application/src/components/regional-monitoring - Server monitoring
application/src/components/servers - Container monitoring
application/src/components/docker - SSL monitoring
application/src/components/ssl-domain
Status and response
- Incident management
application/src/components/schedule-incident - Operational pages
application/src/components/operational-page - Public status
application/src/components/public
Backend operations
- Monitoring workers
server/service-operation/main.go - Data retention
server/service-operation/data-retention/service.go - Alert delivery
server/service-operation/notification
Persistence
- PocketBase client
application/src/lib/pocketbase.ts - PocketBase
server/core_backend-server/core/app.go
Other components
- Operator
- Monitored systems
- Notification channels
Connections 24
- Operator → Web app routes: uses
- Web app routes → Authentication: routes login
- Web app routes → Dashboard: routes dashboard
- Web app routes → Service views: routes services
- Web app routes → Regional monitoring: routes regional
- Web app routes → Server monitoring: routes servers
- Web app routes → Container monitoring: routes containers
- Web app routes → SSL monitoring: routes SSL
- Web app routes → Incident management: routes incidents
- Web app routes → Operational pages: routes pages
- Web app routes → Public status: routes public
- Web app routes → Administration: routes settings
- Authentication → PocketBase client: authenticates via
- Service views → Service actions: uses actions
- Service views → Service detail data: loads detail
- Service detail data → Uptime history: fetches history
- Service actions → PocketBase client: deletes records
- Monitoring workers → Monitored systems: checks systems
- Monitoring workers → Data retention: starts scheduler
- Monitoring workers → PocketBase: initializes client
- Data retention → PocketBase: reads and deletes
- Alert delivery → Notification channels: sends alerts
- Alert delivery → PocketBase: loads configuration
- PocketBase client → PocketBase: accesses backend