Monitoring
TurboStack monitors your infrastructure and applications so problems are caught early. This page explains the monitoring and observability you get and how to use it well.
Note
The in-app Monitoring screen is documented at Monitoring, and each host has a Health tab documented at Health.
Tip
Each host's Health tab gives you a live overview of top issues, CPU/memory/disk usage and service checks. The Monitoring section in the main navigation collects monitoring across your hosts.
Infrastructure and service monitoring
TurboStack's monitoring provides uptime and health checks for your hosts and services. It watches system-level metrics such as disk, memory, load and open ports, and runs dedicated checks for the services you run, including:
You receive email alerts whenever a status changes, and you can review current state on a read-only monitoring dashboard.
Per-application health checks
You can set a monitoring_url for each application so that every production site is actively monitored. See Applications for where to configure this.
Tip
Set a monitoring_url on every production application so each site is checked continuously and you are alerted the moment it goes down.
Application Performance Monitoring (APM)
For deeper insight into how your applications behave, optional APM integrations are available:
These are configured with per-application API keys. See Advanced settings.
Tip
With Blackfire you can profile a page directly from the browser: install the Blackfire browser
extension (Chrome or Firefox), sign in with your blackfire.io account, open the page and click
Profile to see the call graph and timeline. The Profile all requests mode (for POST and
Ajax calls) currently works in Firefox, not Chrome. You can also start a profile over SSH with
tscli blackfire enable.
Database monitoring
Advanced Database Monitoring provides query-performance insight and metrics dashboards for your databases. It uses a central monitoring master server that collects metrics from your TurboStack servers.
To send a server's database metrics to a monitoring master, enable it on the host's Advanced > Advanced Database Monitoring. Fill in the master server's hostname and, optionally, the sampling rate. You can also configure it in YAML:
pmm_master:
server_hostname: pmm.example.com
Tip
Keep the default sampling rate of 50 unless you have a reason to change it. It collects metrics from every Nth query; a lower value gives more detail but adds load to both the monitored server and the master.
Once a monitoring master is running, open its dashboard at https://pmm.<yourdomain>. Log in with the pmmagent user; its credentials are available from the Credentials button in the TurboStack interface.
If you do not have a monitoring master yet, you can run one on TurboStack - see Self-hosted platforms. For where database services are configured, see Services.
Standards-based metrics
An optional OpenTelemetry collector is available for standards-based metrics export, so you can feed monitoring data into your own observability tooling.