Highlights of ZKRush — Exclusive Monitoring System for Aleo Mining


As the premier Zero-Knowledge track technology solution and mining service provider, ZKRush’s design incorporates Kubernetes, load balancing, virtualization, virtual networking, and other cutting-edge technologies. Our operations and maintenance team has set up all parts of monitoring the Aleo mining pool for different latitudes. Meanwhile, depending on the type, it is presented on various monitoring dashboards in real time.

Kubernetes Cluster Resource Monitoring

This section primarily displays the resource utilization of the master and nodes in a Kubernetes cluster. In the cluster, all node resources are treated as a whole, and we don’t care which node the business application is deployed on, but the scheduling is done automatically and uniformly by the cluster master. The only thing we need to worry about in terms of resources is if our cluster’s aggregate resources can satisfy our business demands, which the monitoring dashboard clearly shows. The present cluster resource status is fairly good, as seen below. The monitoring screen also displays the basic resource information for each node. Each dimension, such as CPU, memory, network, and IO, is presented independently. In actual production, any anomaly in any one indicator can have a ripple effect on the entire cluster and business, thus it is vital to subdivide the different indicators in order to swiftly and effectively alter business settings, programs, clusters, and so on.


Kubernetes Cluster Business-Level Monitoring

In addition to resource-level monitoring, Kubernetes business-level monitoring is critical, and the operation of various components of ZKRush is clearly displayed on the monitoring panel, including Namespace, nodes, deployment, Pod, and other dimensions and controller dimensions, which are sorted and displayed, prioritizing the applications with higher resource usage. If an anomalous application is detected, it may be the first time in the troubleshooting process. In addition to the business components, the diagram shows that the cluster incorporates several network, logging, scheduling, and monitoring components. The regular operation of these components is equally vital to that of the Aleo mining pool. Therefore, we must guarantee that all sorts of components are functioning well, and we can monitor their health status in real time through the overall dashboard.


Load Balancing & Network Monitoring

After Phase 2 of Aleo Testnet 3, and especially after the launch of the mainnet, network-level monitoring becomes necessary in order to handle the huge number of user accesses. The mining pool has significant network needs since it is responsible for node synchronization, task distribution, and receiving. The ZKRush team pays close attention to indicators including hashrate, user volume, and active miners. Furthermore, we have made several improvements to the packets that disperse the burden. The smallest amount of network overhead is employed to connect to as many people as feasible. We also offer a Proxy program for high-volume clients that allows all of the user’s miners to access the mining pool in a uniform manner, eliminating income loss due to network instability. At the network level, we concentrate on monitoring and showing inflow/outflow traffic, load balancing components, and load balancing back-end carrying capacity so that the pool’s network carrying capacity may be updated and enlarged the first time it is required.


Server Metrics Monitoring

ZKRush has some business components deployed on standalone servers, which also have some key components, such as Aleo node-related components, observer nodes for chain data, Aleo mining pool components, and, of course, Kubernetes node servers, in addition to the business within the Kubernetes cluster. As a result, server-level monitoring is available, including CPU, RAM, connection count, and other information. The private chain test phase resources of the Aleo mining pool are illustrated in the example below.


A robust and comprehensive resource monitoring system is required for a mining pool’s stable functioning and allows us to better serve all miner groups. As promised, our continual goal is to maximize client income while decreasing information gaps. In the coming days, we will also offer the latest analysis of the official code revisions on GitHub, so stay tuned.

Link copied!