Configuration
Control Tower can be configured via the Control Panel under Settings → Control Tower, or by creating a config/control-tower.php file.
Config File
Create config/control-tower.php to override settings per environment:
<?php
return [
'trackVisitors' => true,
'trackEditors' => true,
'trackServerMetrics' => true,
'refreshInterval' => 30,
'visitorTimeout' => 120,
'editorTimeout' => 300,
'visitorRetentionDays' => 30,
'editorRetentionDays' => 90,
'contentEventRetentionDays' => 90,
'metricRetentionDays' => 30,
'alertRetentionDays' => 90,
'staleContentDays' => 90,
'metricsPollingInterval' => 60,
];
5.1.0 note:
Alert thresholds are no longer configured here. Define them as alert rules in the control panel instead. The legacy queueFailureAlertThreshold and enableCollisionDetection settings are still accepted by the model for backwards compatibility but are ignored at runtime — their behavior is now expressed as seeded default rules.
Tracking Controls
| Setting | Default | Description |
|---|---|---|
trackVisitors | true | Enable front-end visitor tracking |
trackEditors | true | Track CP user activity and element editing |
trackServerMetrics | true | Periodically sample CPU, memory, disk, and DB metrics |
Refresh & Timeouts
| Setting | Default | Description |
|---|---|---|
refreshInterval | 30 | Dashboard auto-refresh interval in seconds |
visitorTimeout | 120 | Seconds before a visitor is considered inactive |
editorTimeout | 300 | Seconds before an editor session is considered inactive |
metricsPollingInterval | 60 | Seconds between server metric snapshots |
Data Retention
| Setting | Default | Description |
|---|---|---|
visitorRetentionDays | 30 | Days to keep visitor data |
editorRetentionDays | 90 | Days to keep editor activity data |
contentEventRetentionDays | 90 | Days to keep content event data |
metricRetentionDays | 30 | Days to keep metric samples |
alertRetentionDays | 90 | Days to keep alert history |
Content Health
| Setting | Default | Description |
|---|---|---|
staleContentDays | 90 | Days without update before an entry is flagged as stale (also drives the stale_content_count metric for alert rules) |
Alert Thresholds
Alert thresholds are no longer configured in config/control-tower.php. Use the Alert Rules section in the control panel to define when alerts fire, what severity they have, and where they’re sent. See Alerts & Webhooks for full details and the list of available metrics.