Uptime Kuma is a self-hosted monitoring tool that allows you to track the status and availability of services, websites, and applications. Version 2.3 introduces several new features and improvements that expand its monitoring and notification capabilities.

This guide is useful for system administrators, developers, and technical users who want to monitor their services efficiently and receive timely notifications of any issues. With the new features introduced in version 2.3, Uptime Kuma becomes even more powerful and flexible.

  • Extended monitoring: The new OracleDB monitor extends database monitoring capabilities.
  • Notification improvements: Support for Telnyx messaging, VK notifications, MAX Messenger notifications, and custom templates for Evolution.
  • Improved organization: Collapsible groups on the status page for better organization.
  • Bug fixes: Correction of various issues, including uptime calculation, domain expiry checks, and Prometheus metrics management.

Prerequisites

  • Hardware: A device compatible with Uptime Kuma, such as a Raspberry Pi or a dedicated server.
  • Software: Docker installed on the device.
  • Version: Uptime Kuma 2.3.

Procedure to Upgrade to Uptime Kuma 2.3

Following this guide, you will upgrade Uptime Kuma to version 2.3, benefiting from the new features and fixes.

  • Log in to the server hosting Uptime Kuma.
  • Perform a full backup of the current database and configuration.
  • Upgrade Uptime Kuma using the original installation method (e.g., Docker, npm, etc.).
  • If you are using a Raspberry Pi, modify the configuration file to add the option UPTIMEKUMASQLITESINGLECONNECTION and set it to true.
  • Restart the Uptime Kuma service to apply the changes.
  • Verify that all critical features are operational.

For more details, check the official changelog.

Verification and Troubleshooting

After upgrading Uptime Kuma to version 2.3, it is important to verify the correct operation of the system and resolve any issues. Follow these steps to test the system and address common problems.

Functionality Test

  • Check the monitors: Access the Uptime Kuma interface and ensure that all monitors are active and functioning. Make sure the new OracleDB monitors are configured correctly.
  • Check notifications: Verify that notifications are configured and working. Try sending a test notification for each provider, including Telnyx, VK, MAX Messenger, and Home Assistant.
  • Examine the status page: Check that the status pages are organized correctly and that the collapsible groups work as expected.
  • Check Prometheus metrics: Verify that the Prometheus metrics are correct and that there are no duplicate series for monitors with tags.

Problem Solving

  • SQLite issues on Raspberry Pi: If you are using a Raspberry Pi, set the option UPTIMEKUMASQLITESINGLECONNECTION to true to avoid database lock issues.
  • Status page ordering: If you used the status page ordering feature, note that it has been removed due to performance issues.
  • Notification issues: If you encounter problems with notifications, check the provider configuration and ensure that custom message templates are correct.
  • Uptime issues: If you notice discrepancies in uptime calculations, ensure that missing time buckets are handled correctly.
  • Domain expiry issues: If domain expiry checks do not update correctly, verify the monitor configuration.
  • Prometheus metrics issues: If Prometheus metrics produce duplicate series, verify that tags are configured correctly.
  • Monitor creation issues: If you encounter errors when creating a monitor, ensure that all required parameters are set correctly.

At the end of this guide, you will have a comprehensive overview of the new features introduced in Uptime Kuma 2.3 and know how to best leverage its updated features.

Educational Summary

  • WebSocket handling: Improved with support for authentication.
  • Status page: Collapsible groups for better organization, but sorting removed due to performance issues.
  • Bug fixes: Corrections for uptime calculations, domain expiry checks, SSL handling, Prometheus metrics, and more.

Call to Action

If you haven't tried Uptime Kuma yet, follow the detailed guide for quick installation with Docker here.

Editorial Note and Disclaimer

The guides and content published on GoYou are the result of independent research and analysis activities, for informational, educational, and in-depth purposes.

GoYou does not constitute a journalistic publication or an editorial product pursuant to Law No. 62/2001 and does not engage in real-time information activities.

The GoYou project does not provide professional, technical, legal, or financial advice and disclaims any liability for the misuse of the information published.

In the Crypto sector, every investment involves risks: readers are invited to always inform themselves independently before making any decision.