> For the complete documentation index, see [llms.txt](https://engineering.umh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://engineering.umh.app/product/who-we-build-for/it-system-administration.md). # IT: system administration The team that runs the network and servers UMH is installed on. **The system administration team wants UMH to need few firewall changes and few resources.** The team runs the network and the servers. UMH needs only one outgoing connection. The team often runs its own servers on site with limited resources. **UMH has to fit into the team's alerting.** The team often monitors its systems around the clock and runs a helpdesk. If UMH raises an alert for high CPU usage, someone there gets woken up in the middle of the night. If that keeps happening, they switch UMH's alerts off. UMH integrates with the team's monitoring, for example through [Prometheus metrics](https://docs.umh.app/production/metrics). Because of [opinionated simplicity](/product/product-standards/opinionated-simplicity.md), UMH should have only one health status. With monitoring, it is easy to end up with a second one that the monitoring team builds itself. So the monitoring team should only alert when a metric shows that something in UMH is degraded. **In companies that treat IT as a cost center, a project can wait a couple of months for its servers.** --- # 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://engineering.umh.app/product/who-we-build-for/it-system-administration.md?ask=&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.