Workfreeli Server Status

Loading…
Healthy

Server

Environment—
Port—
Runtime—
Uptime—
Version—
PID—

MongoDB

Status—
Host—
Database—

XMPP / ejabberd

Status—
Domain—
API Client—

Memory

RSS?Memory Usage (RSS)Physical RAM being used by your server process.✅ Good: Stable under 1 GB⚠️ Warning: Growing steadily over time🔴 Critical: Near system limit, or constant growth🔧 Do: Check for memory leaks in long-running resolvers❌ Don’t: Don't restart without investigating — the leak will return—
Heap Used?Heap UsedMemory used by your Bun/Node.js JS objects.✅ Good: Stable pattern (saw-tooth from GC)⚠️ Warning: Constantly increasing🔴 Critical: Hitting heap limit (crashes)🔧 Do: Profile heap snapshots; look for unbounded caches❌ Don’t: Don't just raise --max-old-space-size — find the leak—
Heap Total—

In-Memory Cache

Companies—
Teams—
Devices—
Cron Jobs—

Endpoints

Status JSON/status
Performance/api/performance
Slow Queries/api/slow-queries
Security Scan/api/security-scan
Prometheus/metrics
REST v1/v1
Stripe Webhook/webhook
Jitsi Events/jitsi-events

CPU Usage (60s) —

Memory RSS (60s) —

Requests / sec (60s) —

Response Time —

Security Scan —

Slow GraphQL Queries (>500ms) —

Understanding Your Metrics

🟢 Good — no action needed
🟡 Warning — monitor closely
🔴 Critical — take action now
Hover over ? for detail
Metric Good Warning Critical Action
P50< 100ms100-300ms> 300msAdd indexes
P95< 300ms300-800ms> 800msAdd pagination
P99< 500ms500-1000ms> 1000msFix N+1 queries
CPU< 70%70-85%> 85%Scale up / profile hot paths
Slow Rate< 5%5-15%> 15%Optimize queries, use DataLoader
Memory RSS< 1 GBGrowingNear limitFind the memory leak
Error Rate< 1%1-5%> 5%Check logs, fix failing endpoints