The adoption of Internet of Things (IoT) practices holds great potential for the industry. Nonetheless, ensuring reliability and maintaining high-quality service is paramount

Information Restructured: In the realm of database design, a relational database schema has been carefully crafted, and two tables have been brought into existence to enable the storage of real-time data seamlessly. The initial table serves as a repository for all currently active probing results, while the second table is dedicated to housing the daily average values computed by the monitoring system. For a comprehensive understanding of these schemas, please refer to Figure 5 below, which elucidates the specifics of both.

Given that the proposed system continually observes and instantly archives results, the database design places significant emphasis on data aggregation. This practice contributes to the diminishment of the database's size and enhances query execution speed, ultimately leading to an enhanced system performance.
Graphical User Interface (GUI): In order to visually present real-time data, it is essential to employ a graphical user interface (GUI). Since there is a need to monitor multiple networks, we organize them into a grid format. Each grid entry contains specific details about an individual endpoint. Besides network status, the GUI also showcases additional information, such as device signal strength and current data usage. Moreover, site-specific data, including the site's IP address, the necessary port number for remote access, and the responsible individual's identity, is also displayed. This site-specific information is crucial for enhancing proactive maintenance procedures.
The current GUI design caters to a control room setup, but it can be adapted for other monitoring configurations. A typical control room comprises multiple monitors that enable personnel to carry out their tasks efficiently. Considering that the control room serves multiple service personnel, it's the ideal location to operate multiple client versions of the system. From this central location, personnel can access their designated remote sites and monitor their real-time statuses at any given moment. For an overview of the system's implementation architecture, please refer to Figure 6. Distributing client versions of the system across multiple workstations is imperative.
The system's implementation architecture has been meticulously crafted to incorporate a singular server application hosted on a dedicated server. The primary purpose of this server application is to facilitate real-time monitoring of communication uplinks and store data in the relational database, as elaborated in the preceding section. The client applications have direct database access, a necessity for delivering a continuous, live-feed view of each remote endpoint's status.