I'm hosting a few Wordpress websites on my server for various people. Recently after setting up my Log monitoring with loki (https://blog.marcel-aust.de/monitoring-with-prometheus-loki-alloy-grafana-2/) I noticed a lot of login attempts by various bots there to the wp-login.php endpoint. I'm running the Wordpress
Recently I updated my monitoring with Prometheus (https://prometheus.io/), Grafana (https://grafana.com/), Loki (https://grafana.com/oss/loki/) and Grafana Alloy (https://grafana.com/docs/alloy/latest/). Grafana Alloy is a relatively new software from Grafana combining node_exporter and promtail in one binary. Setting up PLG-Stack As
In my previous blog post on backups done right with Restic (https://blog.marcel-aust.de/backups-done-right-with-restic-2/ ), one crucial element of a robust backup strategy was missing: monitoring. While a well-configured backup setup is essential, it is equally important to ensure that the backups are functioning correctly and running as scheduled.
... or at least good enough! Restic (https://restic.net/ ) is a modern backup program designed to back up your files. Written in Go, it can be compiled and used on Linux, Windows, macOS, and BSD systems. Restic features end-to-end encryption, supports a wide range of storage backends, and includes deduplication
At work, we use the Go Echo framework (https://echo.labstack.com/ ) for our API services. This HTTP framework is powerful and highly customizable. Sometimes, however, we need to register routes more dynamically at build time. We have a few feature flags in our software that are supposed to disable