Apps

Monitoring

View real-time and historical container metrics for a Skytells app — CPU usage, memory consumption, and container health over time.

The Monitoring page shows resource consumption metrics for the running container. Use it to understand how your app behaves under load, identify resource bottlenecks, and decide when to scale.

Available metrics

MetricDescription
CPU usagePercentage of allocated CPU used by the container over time. Spikes correlate to high-traffic periods or expensive computations.
Memory usageRAM consumed by the container process. Steady growth over time may indicate a memory leak.
Container healthCurrent container state — whether the process is Running, Restarting, or Error.

Metrics are plotted as time-series charts with selectable time windows (last 1 hour, 6 hours, 24 hours, 7 days).

Reading CPU charts

  • Sustained high CPU (above ~80%) indicates the app is compute-bound. Consider optimizing the workload or upgrading the resource plan for this app.
  • CPU spikes that correlate with deployments are normal — the build process runs on a separate build worker and does not affect the running container's CPU.
  • CPU near zero on a running app may indicate the container crashed and is not receiving traffic.

Reading memory charts

  • Steady memory — healthy. The app allocates what it needs and holds it.
  • Growing memory — investigate for memory leaks. Common in Node.js apps that accumulate event listeners, cached objects, or buffered responses.
  • Memory near the plan limit — the container may be OOM-killed by the OS. Check Logs for Killed or exit code 137 messages.

Container health widget

The health widget shows the current container state:

StateMeaning
RunningContainer is live and accepting traffic.
RestartingContainer crashed and is being restarted. Check Logs for the crash reason.
StoppedContainer was stopped manually via the App Overview.
ErrorContainer failed to start. Check Logs and Environment for missing variables.

Relationship to project monitoring

This page shows metrics for this single app only. To see aggregated metrics across all apps and databases in the project, use Project Monitoring.

  • Logs — pair metrics with log output to correlate events.
  • Traffic — see request volume alongside resource usage.
  • Project Monitoring — cross-service observability at the project level.

How is this guide?

On this page