Navigate monitoring
The workspace Monitor section contains Incidents and Vulnerabilities. On Incidents, choose Active or Resolved, then optionally filter by severity. On mobile, open Page menu for these controls.Performance history
Open a server, app, or resource and select Monitor → Performance. Use the time range and chart controls to inspect CPU, memory, disk, and network measurements. Workload views also offer environment and container selection. The URL retains the chart filters, so a shared link opens the same view. Deployment and restart markers connect changes in usage to operational events. Drag across a chart to zoom, or choose a custom time range. Missing measurements appear as gaps. See Scout Agent for collection and retention, and Deployment comparisons for comparing releases over equal windows.Alerts, incidents, and vulnerabilities
Use workspace Incidents to review active or resolved conditions across every server, app, and resource. Filter the list by severity. Configure and inspect alert rules from the relevant entity page; Scout Alerts covers rules and notification destinations. Vulnerabilities provides a separate view of known package findings from app image scans; see Vulnerability scanning.System health
Open Manage → System health and choose Run checks.
System health focuses on Towbar’s control plane; provider availability lives under Integrations.
Server and workload health
The server’s Checks view records connectivity and runtime observations. Its Apps and Resources sidebar items separate the workloads assigned to the host. Health indicators and tooltips identify healthy, unhealthy, starting, and unavailable observations. A deployment can succeed and later become unhealthy. Check the latest runtime state and logs instead of relying only on deployment history.Allocated CPU and memory
Allocation is the limit declared for a workload. Usage is the latest observed consumption relative to that allocation. CPU percentages account for the number of allocated CPUs; memory percentages use the configured memory limit. Server capacity columns describe the host’s maximum capacity. They do not represent an app’s allocation. Missing measurements display as unavailable rather than zero. Review the observation timestamp if the server cannot be reached.
A server’s Apps page compares observed usage with allocated CPU and memory.