Monitoring overview

Coolify tracks the state of connected servers and the workloads running on them. The dashboard shows current status, while notification channels can report selected failures and operational events to your team.

The short version

Sentinel provides the preferred server-to-Coolify status path on supported servers. Metrics adds historical CPU and memory charts. Metrics can be disabled while Sentinel continues to report server and container health.


What Coolify monitors

Monitoring in Coolify covers server state, workload state, resource usage, operational events, and logs.

Server availabilityShows whether a connected server is reachable, validated, and usable.
Workload stateReports container state and Docker health status for applications, databases, and services.
Disk checks and metricsChecks disk usage and records CPU and memory metrics.
Events and logsSends operational notifications and forwards workload logs.

Monitoring boundaries

Built-in monitoring provides platform and container visibility, but it is not a complete external observability system.

What Coolify covers

Use external tools when you need endpoint checks, threshold alerting, long-term analysis, or provider-managed retention.

Built into Coolify

  • Server reachability, validation state, and disk usage checks
  • Container state and Docker health information
  • Historical CPU and memory charts when Sentinel metrics are enabled
  • Selected operational notifications and workload log forwarding

Requires an external system

  • CPU or memory threshold alerts from the built-in charts
  • Public endpoint checks from outside your infrastructure
  • Application workflow checks beyond the health endpoint you configure
  • Log retention, queries, dashboards, and log-based alerts

Log drains forward workload container output. They do not forward Coolify deployment logs or replace the retention and alerting controls in your log provider.


Continue with observability

On this page