diff --git a/blog/2021/09/06/what-to-do-with-a-homelab/index.html b/blog/2021/09/06/what-to-do-with-a-homelab/index.html
index 58097187..823b7901 100644
--- a/blog/2021/09/06/what-to-do-with-a-homelab/index.html
+++ b/blog/2021/09/06/what-to-do-with-a-homelab/index.html
@@ -186,6 +186,7 @@ Containers have much less overhead in terms of boot time and storage allocation.
 <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>As mentioned above, <a href=https://github.com/louislam/uptime-kuma>Uptime Kuma</a> is a convenient way to track uptime and monitor the availability of your services.</p>
+<p><img src=/images/uptime-kuma.png alt=uptime-kuma></p>
 <h2 id=in-summary>In Summary</h2>
 <p>Building out a homelab can be a rewarding experience and it doesn&rsquo;t require buying a rack full of expensive servers to get a significant amount of utility. There are many services that you can run that require very minimal setup, making it possible to get a server up and running in a short period of time, with monitoring, and that can be securely connected to remotely.</p>
 </div>
diff --git a/images/uptime-kuma.png b/images/uptime-kuma.png
new file mode 100644
index 00000000..f6009f7b
Binary files /dev/null and b/images/uptime-kuma.png differ