observability

Observability Overview

Monitor CPU, memory, network, and health for every service you deploy on Runix.

Runix automatically collects metrics from every running service. You can view real-time CPU, memory, and network usage right in the dashboard — no extra setup required.

What You Can Monitor#

CPU usage — percentage of your instance's CPU allocation being used
Memory usage — how much RAM your service is consuming
Network I/O — bytes sent and received over time
Container health — whether your service is running and responding to health checks

Viewing Metrics#

Open the Observability page

Go to your dashboard and click Observability in the sidebar.

Select a service

Pick the deployment you want to monitor from the dropdown. You'll see live charts for CPU, memory, and network.

Choose a time range

Metrics are sampled every 30 seconds. You can view the last hour, last 24 hours, or last 7 days.

If your service is using more than 80% of its memory consistently, consider upgrading to a larger instance type.

For web services, Runix sends an HTTP GET request to your health check path (default: /) every 30 seconds. If the service fails to respond 3 times in a row, it is marked as unhealthy and Runix will attempt to restart it.

You can set a custom health check path in your runix.yaml:

runix.yaml

yaml

services:
  - name: my-api
    type: web-service
    health_check_path: /health

Resource Limits by Instance Type#

Instance	CPU	Memory	Max PIDs
Starter	0.5 vCPU	512 MB	128
Standard	1 vCPU	2 GB	256
Pro	2 vCPU	4 GB	512

If your app exceeds its memory limit, the container is killed and restarted automatically. Check your dashboard for OOM (out of memory) events.

Metrics via CLI#

Check the status of your deployments from the terminal:

bash

runix status my-api

Example output