> For the complete documentation index, see [llms.txt](https://docs.swttoken.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.swttoken.com/getting-started/network-node/step-10-running-the-monitoring-tools.md).

# STEP 10:RUNNING THE MONITORING TOOLS

Under Linux, you have a countless list of more powerful monitoring tools than any other. You are of course free to choose to use all those who will suit you. In this tutorial, we will introduce four tools:

* **htop:** overview and manage running process on the VPS
* **nmon:** indicate the processor load
* **nload:** check the bandwidth used
* **df command:** indicate the free space on your disk

### HTOP

Move to an unused panel and type:

```bash
htop
```

<figure><img src="/files/fLgWFQK47dTLNoXIawCy" alt=""><figcaption></figcaption></figure>

You will be able to sort all process by pressing a function key. For example, if you press **F6** function key, a panel will appear on the left side of the htop panel, and it will allow you to sort the process by memory consumption.

<figure><img src="/files/bhl1Rtkz6s7b6RqG9de8" alt=""><figcaption></figcaption></figure>

You can also directly see the uptime, cpu load, free memory. **But one of the most useful function with htop is to be able to stop/kill a process if needed.** You just have to highlight in blue a process and then press the **F9** function key. A menu will also appear on the left side and just move to option **‘9 SIGKILL’** and press **Enter** to kill the selected process.

<figure><img src="/files/EznaMp7XcVHrDSX5hHjk" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/eGWZhK8IYPmNvvQFWHKL" alt=""><figcaption></figcaption></figure>

### NMON (CPU LOAD)

Move to an unused panel and type:

```bash
nmon
```

Then type “**C**” key, and you will be able to see your VPS CPU load.

<figure><img src="/files/ZiCUW6nasvzD1nahAkUk" alt=""><figcaption></figcaption></figure>

### NLOAD (NETWORK TRAFFIC)

Move to another unused panel and type:

```bash
nload
```

You will then see the network traffic of your VPS:

<figure><img src="/files/nAlzJ8VwHlpOuSu6BaTh" alt=""><figcaption></figcaption></figure>

### DF COMMAND (DISK SPACE)

You can also use the “**df**” command to visualize the disk space used by the **SWT** database, which will grow with time.

```
df -h
```

<figure><img src="/files/oRpxe0xXN0IQzwPOfTHD" alt=""><figcaption></figcaption></figure>

### USEFUL TMUX COMMANDS

#### **1. If you want to list your current sessions:**

```bash
tmux ls
```

#### **2. If you want to access to the right session (replace “myname” by your session name):**

```
tmux a -t myname
```

#### **3. If you want to visit your different sessions:**

```bash
tmux w
```

#### **4. If you want to restart programs from the beginning:**

```bash
sudo reboot
```

#### **5. If you want to kill a specific session (replace “myname” by your session name):**

```bash
tmux kill-session -t myname
```

#### **6. Then, the following line will be enough to access to your current session:**

```bash
tmux a
```

#### **7. If you want to open another Tmux window**

```
CTRL-B + C
```

#### **8. If you want to close a Tmux window**

```
CTRL-B + &
```

### USEFUL APPLICATION

#### **Creating an apport application to get the core dumped file**

The apport application automatically reports only managed packaged applications. When application crash, the core dump files are put in **/var/crash.**

The SWT client app is not a packaged application, so let's configure apport to get the core dump file. It helps SWT team to identify issues when you get some troubles with your node.

#### **1. Create and edit an apport settings file in .config**

```bash
sudo mkdir ~/.config/apport/
sudo nano ~/config/apport/settings
```

#### **2. Put this in the settings file**

```bash
[main]
unpackaged=true
```

Save changes by **CTRL +X**, type **Y** and then press **ENTER**.

#### **3. Restart apport**

```bash
sudo service apport restart
```

#### **4. After a crash, unpack the crash file generated by apport:**

```bash
cd /var/crash
mkdir /tmp/report
apport unpack _home_swt_swtnode_client.1000.crash /tmp/report
```

{% hint style="info" %}
The previous line has to be written in a single line, beginning with “apport-unpack”, then SPACE, then “\_home\_swt\_swtnode\_client.1000.crash /tmp/report”
{% endhint %}

#### **5. Then, type this last line:**

```bash
ls -l /tmp/report
```

Then you will have your core dumped file (it can take a while to unpack: \~1 or 2 min).

**NB: The pattern of the core dumped file is here. You can modify it if you want, but it's not recommended:**

```bash
cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c %d %P
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.swttoken.com/getting-started/network-node/step-10-running-the-monitoring-tools.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.