Advanced System Tools
System-wide utilities, scaling, and recovery
Smart Auto-Scaling Rules
Automated resource scaling based on real-time metrics
| Rule Name | Resource | Trigger Condition | Scale Action | Cooldown | Min / Max | Status | Actions |
|---|---|---|---|---|---|---|---|
| Loading... | |||||||
Total Backup Size
—
Across all locations
Last Full Backup
—
On schedule
Backup Success Rate
—
Last 30 days
Retention Period
—
Policy compliant
Recent Backups
Recent backup jobs and their execution status
| Target | Type | Schedule | Last Run | Size | Duration | Status | Actions |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
Backup Locations
Loading backup locations…
Recovery Point Objective (RPO)
0
Maximum data loss window
Recovery Time Objective (RTO)
0
Maximum downtime target
Last DR Test
0
Passed
DR Status
0
All systems standby
Recovery Procedures
Step-by-step disaster recovery runbooks
Procedure for complete platform restoration when all primary systems are unavailable. Estimated recovery time: 3-4 hours.
- Activate DR failover site and verify network connectivity
- Restore database cluster from latest S3 vault backup
- Deploy application containers from configuration backups
- Verify data integrity and run automated health checks
- Update DNS records and redirect traffic to DR site
Procedure for recovering a single failed compute node. Estimated recovery time: 30-60 minutes.
- Isolate the failed node from the load balancer pool
- Migrate active workloads to healthy nodes
- Perform hardware diagnostics and repair or replace
- Restore node configuration from backup
- Re-add node to cluster and verify health checks
Procedure for restoring database services from backup when primary database is corrupted or unavailable. Estimated recovery time: 1-2 hours.
- Stop all write operations and enable maintenance mode
- Identify the latest clean backup point from backup logs
- Restore full backup then apply incremental transactions
- Validate data integrity with checksums and spot checks
- Resume services and monitor for anomalies
Procedure for activating DNS failover when the primary datacenter becomes unreachable. Estimated propagation time: 5-30 minutes.
- Confirm primary site is unreachable via multiple checks
- Activate secondary DNS records with pre-configured low TTL
- Verify secondary site services are healthy and accepting traffic
- Monitor DNS propagation and client connectivity
Procedure for recovering from a network partition or complete network failure. Estimated recovery time: 15-45 minutes.
- Identify the scope and cause of the network partition
- Activate backup network paths and BGP failover routes
- Reconfigure affected firewalls and load balancers
- Verify inter-node communication and service mesh health
- Run full connectivity test suite across all regions
Failover Groups
Active failover groups and DR drill controls
| Name | Primary | Secondary | Status | Actions |
|---|---|---|---|---|
| Loading... | ||||
Service Linking
Service dependencies and health monitoring
See Service Linking tab → for the full dependency view.
Service Link Groups
| Link Group | Primary Service | Linked Services | Link Type | Auto-Action on Failure | Status | Actions |
|---|---|---|---|---|---|---|
| Loading... | ||||||
Impact Analysis
Shows cascading effects when a primary service is affected
(Domain)
— would be suspended
SSL Certificate
— would be revoked
DNS Zone
— would be disabled
Daily Backup
— would be paused
Active Anomalies
0
▼ -3 vs yesterday
False Positive Rate
0
▼ -1.4% improvement
Prediction Accuracy
0
Based on confirmed anomalies
Healthy Nodes
—
Automatic resolution rate
Active Anomalies
| Detected At | Node / Service | Anomaly Type | Confidence % | Auto-Action Taken | Status |
|---|---|---|---|---|---|
| Loading... | |||||
AI Model Settings
Detection Sensitivity
Normal / High / Maximum
High
Training Data Window
30 days
Auto-Remediation
Only for confidence > 90%
Enabled
Alert Threshold
70% confidence
Anomaly Retention
90 days
Model Version
Last trained: Mar 25, 2026
v2.4.1-prod
Excluded Services
Development environments
3