This video explores some of the practical pros and cons between open source self-hosted Glances, Dozzle and Beszel for the monitoring of running Docker containers in terms of their performance stats, error logs, automated alerting, and troubleshooting of issues.

It concludes with an overview of the Docker compose configuration files to run Beszel. Note that the linked Docker configuration file below will be more up to date than the once I showed in the video.

I did not unpack the Hub vs Agent relationship for Beszel in the video (as I delved into that only the following day), but note that an agent is required for monitoring of services, but an agent will only connect to one Beszel Hub using a unique token and key combination (created in the Hub when adding a System, and then transferred into the Agent's config file). So if an Agent is running on a remote VPS you can link it to a local Beszel Hub, but if you also want to link it to a Beszel Hub running on that remote VPS, then you must create a second Agent container and link that to the VPS's Beszel Hub.

Subsequent to this video, Beszel also helped identify a warning I had in two PostgreSQL databases for collation mismatches: The collation version mismatch warning in my PostgreSQL databases occurred because the database was created with an older version of the system's collation library (glibc version 2.36), but my current system now provides a newer version (2.41). It was just a matter of running a command inside each database to fix that.

Intro 00:00

Glances https://nicolargo.github.io/glances/

My daily tech blog at https://gadgeteer.co.za/blog

#technology #opensource #selfhosting #docker