deploy: 21e145a44f

blog/2021/09/06/what-to-do-with-a-homelab/index.html

@@ -161,6 +161,7 @@ Containers have much less overhead in terms of boot time and storage allocation.
 <h2 id=vpn>VPN</h2>
 <p>You could certainly setup and manage your own VPN by using something like <a href=https://openvpn.net/community-downloads/>OpenVPN</a>, but there is also something else you can try: <a href=https://tailscale.com/>tailscale</a>. It is a very quick way to create fully-encrypted connections between clients. And by using its <a href=https://tailscale.com/kb/1081/magicdns/>MagicDNS</a>, it is a truly magical solution. If one of your nodes has a hostname of <code>plex</code>, you can simply access it by referring to its hostname (i.e <code>ssh plex@plex</code>). This way you can create a secure tunnel to your homelab from anywhere in the world!</p>
 <h2 id=monitoring>Monitoring</h2>
+<p><img src=https://user-images.githubusercontent.com/4519234/133014770-4b799051-e34f-4b29-86c0-fbb9480cd63f.png alt=dashboard></p>
 <p>Monitoring can become an important aspect of your homelab after it starts to become something that is relied upon. One of the simplest ways to setup some monitoring is using <a href=https://www.netdata.cloud/>netdata</a>. It can be installed on individual containers, VMs, and also a hypervisor (such as Proxmox). All of the monitoring works out of the box by detecting disks, memory, network interfaces, etc.</p>
 <p>Additionally, agents installed on different machines can all be centrally viewed in netdata, and it can alert you when some of your infrastructure is down or in a degraded state. Adding additional nodes to netdata is as simple as a 1-line shell command.</p>
 <p><a href=https://grafana.com/>Grafana</a> is another open source analytics and monitoring solution. If you are looking for ideas, check out <a href=https://www.wikimedia.org/>Wikimedia</a>&rsquo;s <a href=https://grafana.wikimedia.org/>public Grafana</a>.</p>