Use the System page

The System page shows host and container health from Link’s monitoring stack. Use it to check whether the Link server and containers have enough CPU, memory, and disk capacity.

Open the System page

1. Sign in to Powercode Link.
2. Select System in the page selector.

Read the summary cards

The top cards show:

• Avg CPU: average host CPU utilization.
• Avg Memory: average host memory utilization.
• Disk Used: root filesystem utilization.
• Containers: number of containers reporting metrics.
• Container Memory: aggregate memory reported by containers.

A dash (—) means the metric is unavailable.

Review system usage history

The System Usage chart shows recent CPU and memory trends. Select a time window:

• 15m
• 1h
• 6h

The chart includes CPU busy, CPU mode lines when available, and memory utilization.

The status lines below the chart explain whether host and disk history are fresh, stale, unavailable, or failed.

View CPU breakdown

Use CPU breakdown to inspect current host CPU details.

1. Select Expand.
2. Review CPU busy percentage, CPU core count, per-mode CPU time, and per-core CPU busy values.
3. Select Collapse when done.

This is useful when the summary CPU number is high and you need to see whether the load is system time, user time, I/O wait, or a specific core.

Review top containers

The Top containers table shows container CPU and memory usage.

• Use Sort to order by CPU, Memory, or Name.
• Select Show all to display every reporting container.
• Select a container row to focus it and show CPU and memory details above the table.

When to use this page

Use the System page when:

• The UI is slow or metrics are delayed.
• DHCP or probe services appear unhealthy.
• Disk usage may be high.
• You need to identify a high-CPU or high-memory container.

Troubleshooting

• If system history is unavailable, the monitoring stack may still be starting or Prometheus may not have enough samples yet.
• If container metrics are unavailable, confirm the monitoring containers are running.
• If you are not authorized, ask for gateway:observability:read access.