Pi-Node Monitor | Official Websitee

Pi-Node Monitor (Beta 0.01) – Documentation

1. Overview: Performance, Compatibility & Advantages

The Pi-Node Monitor (Beta) is a lightweight, high-performance monitoring solution for Pi Network nodes. The application was specifically developed to provide node operators with maximum transparency regarding the current system status, blockchain synchronization, and network connectivity, packaged in an immersive cyberpunk dashboard.

Performance Features:

  • Real-Time Metrics: Cyclic querying of the local node API in the background without any noticeable system overhead.
  • Resource-Friendly: Thanks to Python 3.11 based on Flask, the container requires minimal CPU cycles and extremely low memory in an idle state.
  • Live Updates: Automatic updating of block height, peer connections, and telemetry data in the frontend via JavaScript (JSON polling), completely without manual page reloads.

Compatibility:

  • Multi-Architecture Support: Native, optimized Docker images for both classic 64-bit server environments (amd64) and resource-efficient single-board computers like the Raspberry Pi (arm64).
  • Container-Native: Seamless integration into existing Docker and Docker-Compose infrastructures without external package dependencies on the host system.

Advantages at a Glance:

  • Fast Error Detection: Immediate visual feedback in case of deviations in quorum lag, the consensus phase, or connection loss.
  • Strict Encapsulation: Version control is firmly anchored at the module level within the app logic (no vulnerable injection or hardcoding in the template).
  • Optimized UI Design: Highly readable monospace typography with a reactive Tailwind CSS cyberpunk theme for professional 24/7 monitoring deployment.

2. System Requirements

ComponentMinimum RequirementRecommended
Processor (CPU)x86_64 (amd64) or ARMv8 (arm64) // 2 Cores4 Cores or more
Operating SystemLinux (e.g., Ubuntu Server, Debian, Raspberry Pi OS) / WINDOWSLinux with systemd / macOS / WINDOWS
Runtime EnvironmentDocker Engine v20.10+ & Docker Compose v2.0+ / WSL 2 with Docker Desktop for WINDOWSLatest stable Docker Desktop / Engine version
NetworkLocal access to the API of the running Pi nodeStable LAN connection with static IP assignment

3. Installation & Configuration

3.1 Provided Docker Images

The container images are provided separately by target architecture via the GitHub Container Registry (ghcr.io):

  • For AMD64/x86_64 Systems: ghcr.io/Klissner/pi-node-monitor:beta-0.01-amd64
  • For ARM64 (e.g., Raspberry Pi, Mac M-Series): ghcr.io/Klissner/pi-node-monitor:beta-0.01-arm64

3.2 Docker-Compose Configuration

Create a docker-compose.yml file in your project directory. Adjust the image tag according to your system architecture (-amd64 or -arm64):

YAML

services:
  pi-monitor:
    image: ghcr.io/klissner/pi-node-monitor:beta-0.01-amd64      # x86 systems
    # image: ghcr.io/klissner/pi-node-monitor:beta-0.01-arm64    # Raspberry Pi / Apple Silicon
    container_name: pi-monitor
    restart: unless-stopped
    ports:
      - "${MONITOR_PORT}:${MONITOR_PORT}"
    env_file:
      - .env
    volumes:
      - ./app-data:/app/data

Description of Content: The configuration defines the pi-monitor service. The port mapping forwards traffic from port 8080 of the host system to the internal Flask port 8080. Environment variables are loaded from the .env file via env_file to dynamically adjust infrastructure parameters. An automatic log rotation limit protects the hard disk space from overflowing.

3.3 Environment Variables (.env)

Create a configuration file named .env (or .inv) in the same directory as the docker-compose.yml and enter all required parameters:

  • NODE_IP=192.168.x.x Defines the IP address of the target host where the Pi network node is running and providing its API.
  • NODE_PORT=11626 The network port through which the local status API of the Pi node is queried.
  • MONITOR_PORT=8080 The external port of the host system under which the web interface of the Pi-Node Monitor can be accessed in the browser.
  • REFRESH_INTERVAL=10 The time interval in seconds in which the backend cyclically queries and updates the data from the Pi node.
  • TIMEZONE=Asia/Bangkok The timezone to use for the correct display and synchronization of timestamps within the application.
  • LANGUAGE=de The default language setting for the localization of the user interface and system messages. The following languages are available: de=German and en=English.
  • UPDATE_API_URL=[https://api.github.com/repos/pi-apps/pi-node-docker/releases/latest](https://api.github.com/repos/pi-apps/pi-node-docker/releases/latest)The API endpoint to the GitHub repository used to automatically check for newer versions or releases of the underlying Docker setup.

3.4 Graphical User Interface (GUI) & Display Fields

The dashboard is divided into an upper status bar, two functional main sections, and an information system in the footer. Below, all values and outputs are described in detail:

Upper Status & Live Bar

  • STATUS: The current synchronization state of the node. Displays ● SYNCED! in bright green when the local node is fully synchronized with the network.
  • AKTUELLER BLOCK (CURRENT BLOCK): The current block number that your local Pi node has processed.
  • GESAMT-BLÖCKE (TOTAL BLOCKS): The official, global total number of blocks in the Pi network to compare the chain.
  • LETZTER BLOCK VOR (LAST BLOCK AGONE): A live timer indicating how many seconds ago the last block was successfully received or processed (e.g., 4s).
  • PEERS: The number of directly connected neighboring nodes (neighbors) in the P2P network (e.g., 6).
  • UPTIME: The continuous operating time of the monitor or container since the last start (e.g., 2d 1h).

Left Panel: SYSTEM-KERNDATEN (SYSTEM CORE DATA)

  • Software-Version: The currently installed core version of the monitored Pi node (e.g., v24.1.0).
  • Netzwerk-Identifikation (Network Identification): The network to which the node is connected (fixed to Pi Network).
  • Protokoll-Version (Protocol Version): The active version of the underlying blockchain protocol (e.g., 24).
  • Wartende Peers (Waiting Peers): The number of incoming or waiting connection requests from other nodes in the network (e.g., 4).
  • Letzter Startzeitpunkt (Last Startup Time): The exact date and time of the last system or node restart (e.g., 6.7.2026, 21:50:33).
  • Letzter Block-Hash (Last Block Hash): The unique cryptographic SHA-256 identification hash of the last processed block, displayed in a dark monospace box.
  • TERMINAL / KONFIG_ÜBERSCHREIBEN (OVERRIDE CONFIG): An interactive input line in the UI used to temporarily or permanently override the target IP, port, and language code (e.g., DE) via a click event (SET).

Right Panel: KONSENS & QUORUM-MATRIX (CONSENSUS & QUORUM MATRIX)

  • Knoten-Identität (Node Identity): The unique, shortened cryptographic identifier (public key) of your specific validator node (e.g., GCCEN).
  • Ertrags-Index (KPI) (Yield Index): The percentage performance and availability index of the node within the consensus group (optimal at 100 %).
  • Konsens-Phase (Consensus Phase): The current status within the Stellar Consensus Protocol (SCP). EXTERNALIZE signals in green that the node is actively participating in the final confirmation and validation of blocks.
  • Ausfalltoleranz (Knoten) (Fail-safe Tolerance): The maximum number of validator nodes within your quorum that may fail simultaneously without your own node losing consensus (e.g., 2).
  • Netzwerk-Verzögerung (Network Delay): The current latency of network messages in the consensus protocol, measured in milliseconds (e.g., 118 ms).
  • Zustimmende Knoten (Agreeing Nodes): The number of active validator nodes in the quorum that agree with the current consensus status (e.g., 3).
  • Fehlende Antworten (Missing Answers): The number of nodes in the configured quorum that are currently not responding or are offline (optimal at 0).
  • Transitive Knotenmenge (Transitive Node Set): The total number of all reachable nodes in the extended, linked trust network (e.g., 8).
  • Sicherheits-Schnittmenge (Security Intersection): Indicator of the mathematical integrity and overlap of the quorum. Dispatched as SECURE_OK in green during a stable condition.

Lower Section (Footer)

  • System-Status aktuell (System Status Current): A green status confirmation at the top right of the footer, signaling the error-free execution of the GUI.
  • Versions-Render (Version Render): The globally anchored version variable in the footer: Pi-Network Monitor Beta: 0.01.

4. Copyright and License (LICENSE.md)

The following official license agreement applies to this project:

Plaintext

MIT License

Copyright (c) 2026 KSC | by Michael Klissner

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

5. Support & Donation Links

If the Pi-Node Monitor helps you and you would like to support the continuous development of the beta phase, we welcome a voluntary contribution:

Thank you for your contribution to maintaining stable and transparent node infrastructures!

Donate Bild

Support / Donation Link for the Channel
If my posts have been helpful or supported you in any way, I’d truly appreciate your support 🙏

PayPal Link
Bank transfer, Bitcoin and Lightning

#PiNetwork #PiNode #Docker #Blockchain #CryptoMonitoring #Mining