Skip to content

Monitor an Instance

The instance detail page shows the current health and resource usage of your service instance. Disk usage, CPU and memory usage, and the log viewer are all available in the Technical Details accordion.

Open the Technical Details

  1. Navigate to the instance detail page.
  2. Expand the Technical Details accordion.

Technical Details accordion showing the Pods and Persistent Volumes tables

Check CPU and memory usage

The Pods table lists the running pods of your service instance. For each pod you see:

  • Phase: the lifecycle state of the pod (for example Running).
  • Ready: whether the pod is ready to serve requests.
  • CPU: current CPU usage as a percentage, with the absolute values below it (usage / request / limit, for example 11m / 250m / 250m).
  • Memory: current memory usage as a percentage, with the absolute values below it (usage / request / limit, for example 129.0 MiB / 1.0 GiB / 1.0 GiB).

The percentage is measured against the configured limit. If a pod consistently runs close to its CPU or memory limit, consider moving to a larger compute plan.

Check disk usage

The Persistent Volumes table shows the storage attached to your instance. For each volume you see:

  • Status: whether the volume is bound and in use (for example Bound).
  • Capacity: the total provisioned size (for example 10Gi).
  • Usage: how much of the volume is used, as a percentage and in absolute terms (for example 350.6 MiB / 9.7 GiB).
  • Storage Class: the storage class backing the volume.

You may notice that the available size shown under Usage is slightly smaller than the provisioned Capacity (for example 9.7 GiB available on a 10Gi volume). This is expected. When the volume is formatted with a filesystem, part of the raw capacity is taken up by filesystem metadata (such as the journal and inode tables) and by blocks the filesystem reserves for internal use. The remaining space is what your service can actually write to, so the usage percentage is calculated against this usable size rather than the raw provisioned size.

When a volume approaches its capacity, plan to increase the storage size. See Scaling for details.

Warning

A full data volume can cause the service to stop accepting writes or fail to start. Act before the volume reaches its capacity.

View logs

Each pod in the Pods table has a log viewer button in the Actions column.

  1. In the Pods table, find the pod whose logs you want to inspect.
  2. Click the log viewer button in the Actions column.

If the service runs multiple containers in a pod, the log viewer lets you choose which container to show logs for.

For downloading logs and troubleshooting tips, see the View Logs guide.