# Advice on self-hosted, self-deployed, no internet, monitoring of multiple servers

**URL:** <https://community.netdata.cloud/t/advice-on-self-hosted-self-deployed-no-internet-monitoring-of-multiple-servers/3200>\
**Category:** Help\
**Tags:** cloud, installation, agent, streaming, update\
**Created:** [August 15, 2022, 1:46pm UTC](https://community.netdata.cloud/t/advice-on-self-hosted-self-deployed-no-internet-monitoring-of-multiple-servers/3200 "2022-08-15T13:46:12Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![underhood](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/underhood/32/798_2.png) [@underhood](https://community.netdata.cloud/u/underhood)\
**Post date:** [August 15, 2022, 3:06pm UTC](https://community.netdata.cloud/t/advice-on-self-hosted-self-deployed-no-internet-monitoring-of-multiple-servers/3200/2 "2022-08-15T15:06:50Z")

</div>

When it comes to packaging related questions those are really dependent on your distribution of choice.

As for centralized monitoring without any internet connection take a look @[Streaming and replication reference | Learn Netdata](https://learn.netdata.cloud/docs/agent/streaming)

The parent netdata node then allows you to store/see charts for children as well. This is not as full featured as netdata cloud but should do.

Parent node can run alarms. You can make children headless (as you noticed already) and make only parent store the data.

> - I want to be able to update the packages, so hopefully there is a way to automate the process somewhat. (i.e. bash script that runs git clone, install-netdata.sh, etc).

This again depends on your distribution of choice and/or some admin/management solution used.  
Currently netdata itself is “read-only” monitoring solution and does not provide tools for remote administration of your servers.

---

_[View the full topic](https://community.netdata.cloud/t/advice-on-self-hosted-self-deployed-no-internet-monitoring-of-multiple-servers/3200)._
