> For the complete documentation index, see [llms.txt](https://docs.pritunl.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pritunl.com/kb/zero/general/endpoint-monitoring.md).

# Endpoint Monitoring

Configure endpoint monitoring

Pritunl Endpoint is an endpoint security and monitoring system in development. Currently only monitoring of basic system metrics on Linux is available. The system will be expanded to support full system metric monitoring, system error alerts, security vulnerability monitoring and protection on Linux, macOS and Windows. The system is ready for production and can be deployed now. Future updates will expand the functionality without disruption to existing configurations.

### Create Endpoint

To create an endpoint click *New* in the endpoints tab.

![](https://github.com/pritunl/pritunl-docs/blob/master/pritunl-zero/.gitbook/assets/endpoint0.png)

Next install the `pritunl-endpoint` package on the server using the [Repositories](doc:repo). The copy the *Registration URI* from the previous step and use it in the command below.

```shell
sudo pritunl-endpoint register pritunl://demo.zero.pritunl.com/21558628109314cf389d77ec_YBREIGJsemWFYL2irNF0kRYyMBNw3fYiTsOKfO2C2QZiIIjL8AnqnzpWSTlCAu3s
sudo systemctl restart pritunl-endpoint
sudo journalctl -u pritunl-endpoint -f
```

After about 5 minutes enough data will be collected for the endpoint charts to show up.

![](https://github.com/pritunl/pritunl-docs/blob/master/pritunl-zero/.gitbook/assets/endpoint_charts.png)


---

# 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://docs.pritunl.com/kb/zero/general/endpoint-monitoring.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.