> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/maintenance/800-series-maintenance-guide/centos-check-cpu-usage.md).

# Check CPU Usage

This procedure is used to check the CPU usage.

Since this is a standard distribution of linux, customers can use other available commands.

### Check CPU usage

From the web interface you can see the CPU usage:

```
Hosts -> Status -> Select Host -> Processor Usage tab
```

![Processor usage](https://docs.telcobridges.com/w/images/4/49/Processor_usage.png)

From the [SSH access](/tmedia-documentation/other-pages/operations/accessing-device.md#ssh), here are the available commands.

With the **top** command you can see the total CPU usage (and Memory usage) of the host:

1. top top - 14:16:25 up 22 days, 6:35, 1 user, load average: 0.00, 0.02, 0.06 Tasks: 143 total, 1 running, 142 sleeping, 0 stopped, 0 zombie Cpu(s): 0.5%us, 0.3%sy, 0.0%ni, 99.1%id, 0.0%wa, 0.0%hi, 0.1%si, 0.0%st Mem: 2041616k total, 1998588k used, 43028k free, 413676k buffers Swap: 4458028k total, 152k used, 4457876k free, 879748k cached

   PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 6718 root 15 0 375m 26m 9740 S 0.7 1.3 88:31.47 tboamapp 7126 root 15 0 352m 30m 5060 S 0.7 1.5 4:43.39 tbstreamserver 7281 root 15 0 338m 27m 10m S 0.7 1.4 18:35.59 toolpack\_sys\_ma 2815 mysql 15 0 389m 60m 5132 S 0.3 3.0 189:01.28 mysqld 6943 root 15 0 301m 11m 4272 S 0.3 0.6 3:15.30 tblogtrace 7421 root 16 0 161m 14m 5156 S 0.3 0.7 13:42.17 snmpd 7425 root 15 0 265m 11m 3732 S 0.3 0.6 57:09.81 tbsnmpmux ... Here we see the CPU usage is at 99% idle.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/maintenance/800-series-maintenance-guide/centos-check-cpu-usage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.