Skip to main content
You’ll enable health checks on your apps to detect downtime, track availability history, and get alerted when something breaks.

​
Enable health checks

Open your app from the Apps list and go to the Monitoring tab. You’ll see the Health Check card in the monitoring grid. Click on it to configure:
SettingDescription
EndpointThe path Nixopus hits to check health (e.g., /health)
MethodHTTP method — GET, POST, or HEAD
IntervalHow often the check runs (in seconds)
TimeoutMax wait time before marking as failed
EnabledToggle the health check on or off
Create a dedicated /health or /healthz endpoint in your app that checks database connectivity and critical dependencies — not just returns 200.

​
Viewing results

The Monitoring tab shows a health check chart with response times and status over time:
  • Green — App responded with a 2xx status within the timeout.
  • Red — App failed to respond or returned a non-2xx status.
The monitoring grid also shows a Deployment Health Chart and Deployment Overview for a full picture of your app’s status.

​
Automatic alerts

When a health check fails, Nixopus triggers notifications through your configured channels (email, Slack, Discord). See notifications to set up alerting.
Health checks run from the Nixopus control plane, not from within your container. This means they verify external accessibility, not just process liveness.