🔄 Auto-refresh: 5s

MongoDB Production Dashboard

Enterprise Monitoring • Project: bab-rizk-415120 • Last Updated: 2026-10-18 12:15:28
Total Connections
484
Databases
1
RAM Usage (Avg)
35.1%
CPU Usage (Avg)
4.4%
Server System Metrics
Server Status CPU Usage RAM Usage Disk Usage Load Average MongoDB Processes
Server 1 - Primary (Nuremberg, DE)
91.98.162.254
ONLINE 4.5% 27.3% 14.2% 0.96 1
Server 2 - Hot Secondary (Falkenstein, DE)
91.99.189.202
ONLINE 11.8% 42.7% 16.2% 0.51 1
Server 3 - Warm Secondary (Helsinki, FI)
135.181.203.67
ONLINE 1.0% 45.7% 17.0% 0.08 1
Server 4 - Archive (Helsinki, FI)
46.62.223.214
ONLINE 2.5% 42.5% 20.7% 0.12 1
Server 5 - Arbiter (Ashburn, US)
178.156.199.143
ONLINE 2.0% 17.3% 19.3% 0.04 1
Replica Set Instances
Instance Server Status State Repl Lag Connections Uptime (hours) Memory (MB)
Primary (Nuremberg) Server 1 - Primary (Nuremberg, DE) Online PRIMARY - 160 0.7h 15644 MB
Hot Secondary (Falkenstein) Server 2 - Hot Secondary (Falkenstein, DE) Online SECONDARY 0s 127 0.7h 12714 MB
Warm Secondary (Helsinki) Server 3 - Warm Secondary (Helsinki, FI) Online SECONDARY 2.0s 99 0.7h 13395 MB
Archive (Helsinki) Server 4 - Archive (Helsinki, FI) Online SECONDARY 2.0s 98 0.7h 6247 MB
Arbiter (US) Server 5 - Arbiter (Ashburn, US) Online ARBITER N/A 0 0.7h 0 MB
Storage & Performance Metrics

💾 Storage

Data Size 41.73 GB
Index Size 9225 MB
Compression Snappy

🔄 WiredTiger Cache

Used / Total 15.1 / 30.2 GB
Utilization 50.0%

⚙️ System

Disk Usage 14.2%
Load Average 0.96
Processes 1
Security & Backup Status

🔒 Security

TLS Encryption ✅ Enabled
CN=*.database.babrizq.co
Authentication ✅ SCRAM-SHA-256

💾 Backup Status

Last Backup N/A
No backups found
Location
/tmp/mongodb-backups (empty)
🎯 Missing Indexes - Recommendations (Last 7 Days)
Collection Fields to Index Hit Count Avg Time Max Time COLLSCAN Impact Score Recommendation
Orders systemID, createdAt 19x 129.1 ms 188 ms - 46588
⚠ No index proposed — The index for this filter already exists (systemID, createdAt). The remaining cost is "reason" is not a field of Orders — $addFields computes it from "reasonDocs.reasons". Needs manual inspection: index the filter that runs BEFORE the first $project/$addFields/$lookup, or move the filter earlier so it can be indexed.
Orders systemID, inventoryStatus.warehouse, createdAt 7x 167.0 ms 249 ms - 8183
db["Orders"].createIndex({"systemID": 1, "inventoryStatus.warehouse": 1, "createdAt": -1});
Orders systemID, type, inventoryStatus.sales, counter.no_answer, salesDetails.assignee 8x 111.4 ms 119 ms - 7128
db["Orders"].createIndex({"systemID": 1, "type": 1, "inventoryStatus.sales": 1, "counter.no_answer": 1, "salesDetails.assignee": 1});
⚠ One value dominates "type", "inventoryStatus.sales", "salesDetails.assignee" in the sample (>60% of documents), so this index is weakly selective there — append a sort key such as createdAt:-1 so the worst case can still stop at the limit.
Orders systemID, type, inventoryStatus.sales, counter.no_answer, salesDetails.assignee, createdAt 4x 111.8 ms 118 ms - 1788
db["Orders"].createIndex({"systemID": 1, "type": 1, "inventoryStatus.sales": 1, "counter.no_answer": 1, "salesDetails.assignee": 1, "createdAt": -1});
⚠ One value dominates "type", "inventoryStatus.sales", "salesDetails.assignee" in the sample (>60% of documents), so this index is weakly selective there — append a sort key such as createdAt:-1 so the worst case can still stop at the limit.