> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Node's work page

> Metrics, processes, systemd services and logs, connection, limitations, and the history of a particular server.

Click the server name in **Park nod**. Its page collects daily work with the machine: from status check to access, terminal, files and history. The availability of tabs and actions depends on your rights.

## Where to find the right one

| Tab | Content | |
| - | - | - |
| **Review** | Basic information and condition of the node | |
| **Connection** | Address, SSH port, transport and bastion | |
| **Metrics** | CPU, memory, disk and graphics | |
| **Processes** | Processes, owner, parent, memory and executable file | |
| **Services** | Systemd, Launch, Stop, Restart, and | Magazine |
| **Location and tags** | Location and classification of the machine | |
| **Access.** | User Permissions and Roles | |
| \*\*\*\* | SSH logins, SFTP directories, | session limits |
| **Prohibits** | Prohibitions | |
| **Agent** | Communication, version, readiness and preparation of agent | |
| **Sessions**, **Audit** | Connections and events of this machine | |

## Metrics and processes

Metrics show the CPU, memory and disk. The snapshot is collected once per minute, periods are available **1**, **6** and **24 hours**. The history of the node metrics is stored in the memory of the Telepúrte server: after restarting the panel, it accumulates again. Check the time of the last shot.

Processes are updated every five seconds. Search helps find the process; the card shows the owner, the parent, the memory usage and the executable. This is a view screen: the service is managed in the **Service** tab.

**Pause** stops the automatic screen update, not the server. **UAGEZZ** requests data again. If the interface crashes, the interface can leave the previous shot with a warning; the absence of a new value does not mean zero load.

## Management of systemd

Open **Services**, find the unit by name or description, and if necessary, filter by status. The service card provides its status and journal. You can select the period and level of messages for the journal.

1. Select an exact unit, such as `nginx.service`.
2. Select **Run**, **Stop** or **Restart**.
3. Check the preliminary summary: node, unit and operation.
4. Confirm the action and wait for the result.
5. Update the status and log, then check the app from the outside.

It's done through the agent and its permissions. There are separate lists of authorized units to stop and start; restarting requires both. Right to see a service doesn't mean right to change its state. If the action is forbidden by policy, correct the exact permission.

## Example: The app has stopped responding

First, look at metric time, free memory, and disk. Then open the application process and the systemd-unit you want. In the log, select the errors in the last 15 minutes, which will help distinguish between a misconfiguration and a lack of resources or a process failure.

If you want to change the configuration, go to [file](https://docs.axottle.com/en/telepurte/files.md), save the original copy and make a change. Editor check helps you find errors, but before restarting, perform a regular check of the service itself. After a confirmed restart, check unit status, fresh log and app availability. \*\*Audit.\*\*Manual work in the terminal - in **Sessions**.

## Connection and limitations

**Transport Direct SSH** uses the address and port of the node. **Tunnel through agent** uses the already installed channel of the agent and is useful when the incoming SSH from the outside is not available. The choice of transport does not cancel the verification of the SSH key and user rights.

Constraints define valid system logins, Web SFTP directories, number of concurrent sessions, and duration. These settings limit access already given. They do not create a role or give the user Linux rights to the file.

## Verification

Check the time of the image and the status of the agent. After the action with the service, make sure that the final state corresponds to the expectation, there is no new error in the log and the application check passes. The status of `active` does not confirm the correct operation of the application.

## Rollback

Return the previous configuration and perform the desired reverse operation with the service after checking. Stop the task does not cancel the restart performed. Return the access restrictions by clearly preserving the previous values; check the rights of the ordinary user.

Older panel assemblies, bastions, and agents may not contain the features described.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.