> For the complete documentation index, see [llms.txt](https://computenetwork.gitbook.io/technical-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://computenetwork.gitbook.io/technical-documentation/2-network-architecture/2.4-monitoring/2.4.1-comprehensive-monitoring-for-cloud-and-proprietary-servers.md).

# 2.4.1 Comprehensive Monitoring for Cloud and Proprietary Servers

* **Performance Monitoring:** We continuously monitor the performance metrics of our cloud and proprietary servers, including CPU usage, memory consumption, and network throughput. This helps in maintaining efficiency and identifying potential bottlenecks.
* **System Health Checks:** Regular health checks are conducted to ensure all critical systems and services are functioning correctly. This includes monitoring for hardware malfunctions, software crashes, and other operational issues.
* **Security Monitoring:** Our security monitoring involves constant surveillance for potential threats or breaches. This includes intrusion detection, abnormal traffic patterns, and unusual access attempts.


---

# 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:

```
GET https://computenetwork.gitbook.io/technical-documentation/2-network-architecture/2.4-monitoring/2.4.1-comprehensive-monitoring-for-cloud-and-proprietary-servers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.