https://devendevour.iankulin.com/tags/flask/Recent content in Flask on dev.endevourHugoen-AUFri, 15 Sep 2023 00:00:00 +0000https://devendevour.iankulin.com/lightweight-web-servers/Fri, 15 Sep 2023 00:00:00 +0000https://devendevour.iankulin.com/lightweight-web-servers/<p><img src="https://devendevour.iankulin.com/images/dreamshaper_v7_a_web_server_floating_away_because_it_is_so_lig_0.jpg" alt="" class="img-responsive"> </p> <p><img src="https://devendevour.iankulin.com/images/screen-shot-2023-08-02-at-9.09.48-pm-2.png" alt="" class="img-responsive"> </p> <p>I&rsquo;ve been using the excellent <a href="https://github.com/louislam/uptime-kuma" target="_blank" rel="noopener">Uptime Kuma</a> for my monitoring, but a couple of recent incidents - an external USB mount disappeared on a remote machine, an NVME drive filled up on a different node and stopped backups working because of a configuration error - have made me start to think about more robust monitoring.</p> <p>The are many great tools for this - <a href="https://www.nagios.org/" target="_blank" rel="noopener">Nagios</a> , <a href="https://prometheus.io/" target="_blank" rel="noopener">Prometheus</a> etc. but they are pretty substantial time investments for the excellent power. They can save time series data and display them beautifully. However, all I really want is to add some extra ability to Uptime Kuma.</p>