Software Update

This document explains the update process of the Bloonix software, as there are a few things to consider when updating via the respective repositories.

Updating the Bloonix-Agent

Updating the Bloonix-Agent is straightforward, and the software is compatible with the Bloonix-Server in every version. This is important because it’s nearly impossible to update the Bloonix-Server and thousands of Bloonix-Agents on monitored hosts at the same time.

Updating the Bloonix-Satellite

There are no concerns when it comes to updating the Bloonix-Satellite. It can be updated at any time.

Updating the Bloonix-WebGUI and the Bloonix-Server

Updating the Bloonix-WebGUI and the Bloonix-Server is a bit different. Both components are closely linked through the database schema. For example, if the schema changes—such as when a new column is added to a table or an existing column is removed or modified—then the versions of the Bloonix-WebGUI and the Bloonix-Server must be compatible with each other.

Schema updates are usually performed by the Bloonix-WebGUI. The database controller of the WebGUI locks the database and applies the update. This ensures that no race conditions occur, even when the Bloonix-WebGUI runs in a cluster.

As soon as the Bloonix-WebGUI has been updated, the Bloonix-Server must also be updated immediately, since the old version of the Bloonix-Server may not be compatible with the updated schema. This could cause the Bloonix-Server to enter a loop, continuously writing error messages to the log file. If both components are running standalone on the same server, this is not a problem, since all packages are updated together and the services restarted during an update (apt-get upgrade / dnf update). However, if the services run on separate servers, the update should be performed simultaneously if possible.