Uptime Kuma 2.0: Monitoring tool now with MariaDB support

The monitoring software Uptime Kuma has been released in version 2.0. This is a major version with breaking changes; administrators should definitely create backups and consult the migration guide before upgrading, according to developer Louis Lam.

MariaDB on board

The most important new feature is support for MariaDB as an alternative database. Previously, Uptime Kuma exclusively used SQLite, which could lead to performance problems in larger deployments. With MariaDB, administrators can now use a more robust database infrastructure with better scalability. However, switching from SQLite to MariaDB requires a manual data migration.

For notification systems, version 2.0 has integrated three new providers: Nextcloud Talk, Brevo (formerly Sendinblue), and Evolution API. Additionally, Uptime Kuma receives an environment variable that allows most notification providers to work behind a proxy – for example, for corporate environments with restrictive network policies.

Another focus was on container security: the Alpine-based Docker images have been removed, and instead, there are now rootless Docker images for increased security. Furthermore, the dependency on proxy-agent has been replaced with a secure alternative after a vulnerability was discovered in the used vm2 library.

Many further changes had already been presented by Uptime Kuma in the beta versions. These include, among others, LiquidJS templates with HTML support and better variable processing for email notifications, SMTP monitoring for mail servers, and public monitor URLs.

Breaking Changes during Upgrade

Uptime Kuma 2.0 is available for download on GitHub. Here, the project also points to a not always easy upgrade: the developers recommend reading all changelogs of the beta versions before the update and validating your own monitoring setups in a test environment.

(fo)