Introduction
Checking every ASIC individually becomes time-consuming as a mining operation grows. A mining pool’s app or web dashboard brings worker status, hashrate, and rejected-share information together so operators can identify which machines need attention.
Start by giving each ASIC a distinct worker name, organizing workers into groups, and checking offline workers, hashrate changes, and rejection patterns. Configure alerts to flag exceptions, then investigate affected machines through their local interfaces or farm-management software.
Pool data shows what the pool observes. Hardware telemetry—such as temperature, fan speed, and hashboard status, where available—helps explain what is happening at the machine. This guide uses ViaBTC’s documented worker-management and alert features to illustrate the workflow.
Start With Clear Worker Names and Groups
Use a distinct worker ID for each ASIC when you want to monitor machines individually. If several devices share a worker identity, their activity can be aggregated under one entry, making it harder to identify an underperforming machine.
Choose names that identify the site, rack, and unit. ViaBTC’s BTC mining guide specifies the format userID.workerID, with the worker ID containing lowercase letters and numbers, up to 64 characters. For example, youraccount.s01r02u03 could identify site 01, rack 02, unit 03. Replace youraccount with your actual mining account name. ViaBTC BTC Mining
ViaBTC automatically creates worker entries after detecting mining activity from correctly configured miners. To organize them on the website:
- Open Pool → Workers.
- Under My group, choose Create group to create a group for a site, rack, or other useful category.
- Open Manage Miners, select the relevant workers, and use Add to to assign them to the group.
Grouping by physical location makes it easier to narrow an investigation when several machines show the same problem. ViaBTC worker-management guide
Read the Worker List in a Useful Order
A consistent sequence helps you find exceptions quickly:
- Worker status: identify workers marked offline or inactive and check whether their absence is expected.
- Hashrate changes: compare account totals with account history, group totals with group history, and individual workers with their own recent baseline. Use comparable measurement periods.
- Rejected-share information: look for sustained increases or unusual patterns rather than reacting to one brief spike.
- Related workers: check whether other machines at the same site or on the same network show a similar change.
- Local diagnostics: open the affected ASIC’s interface or farm-management software to investigate.
This sequence helps distinguish a site-wide interruption from a problem affecting one machine. It also avoids relying only on an account total, which can conceal a drop in one worker’s contribution.
Understand Offline and Inactive Status
A pool’s worker-status label is a signal to investigate, not proof of hardware failure. ViaBTC documents these categories:
Status ViaBTC’s documented meaning Active The worker is connected and contributing hashrate. Offline No hashrate for 20 minutes to one day. Inactive No hashrate for more than one day. A configuration error, network interruption, planned shutdown, or hardware fault can all explain an absence of pool-reported hashrate.
Inactive entries can also represent retired or renamed machines. For entries you have confirmed are no longer needed, open Manage Miners, select the inactive workers, and choose Delete. ViaBTC also documents batch-deletion options. ViaBTC worker-management guide
Compare Pool and Local Hashrate Carefully
Pool and ASIC hashrate readings can differ because they use different data sources and calculation periods. ViaBTC’s real-time pool hashrate uses the previous ten minutes. Its documentation also gives an example of a mining-machine display refreshing every five seconds, but a refresh interval does not tell you how much time the displayed average covers. ViaBTC hashrate explanation
Before comparing readings, check whether the ASIC is displaying a short-term average or an average since startup. Compare the same machine or set of machines over compatible periods. A temporary difference alone does not establish a hardware problem; a persistent gap deserves a check of connectivity, rejected shares, and local hardware status.
For startup checks, ViaBTC’s BTC mining guide recommends checking the Workers and Earnings pages after the miner has stabilized for around 10–15 minutes. Its disconnection troubleshooting guidance separately notes that a worker can take 10–20 minutes of continued operation to return to active status. These are contextual estimates, not guaranteed update deadlines. You can check configuration and connectivity immediately while the pool reading develops. ViaBTC BTC Mining
Configure Account Alerts and Watcher URL Alerts
Alerts reduce the need to refresh the dashboard manually. ViaBTC documents account notifications and app-based Watcher URL alerts separately, so choose the setup that matches how you monitor the operation.
Account Notifications
On the ViaBTC website, open Pool → Dashboard → Alert Settings, configure the relevant parameters, and confirm. Set the receiving details under Notification Method. ViaBTC supports email, app push, and Telegram notifications; its Telegram guide also explains how to deliver worker alerts to a group chat. Account notification setup, Telegram alert setup
Where thresholds are configurable, base them on the monitored account or worker scope, expected hashrate, normal variation, and the size of the loss you want to detect. Review them when machines are added, removed, or intentionally shut down.
Watcher URL Alerts in the App
Watcher URL alerts are available in the ViaBTC app. The documented setup path is My → Watcher → Favorites → Edit. Open the Watcher URL’s Alert Settings, select the relevant account, and enable offline or rejection-rate alerts. An optional Do Not Disturb period suppresses alerts during the selected hours.
For these Watcher URL alerts, ViaBTC documents:
- Worker-offline checks: every ten minutes.
- Worker rejection-rate checks: every hour.
These are check intervals, not guaranteed times from an outage to notification. They should not be generalized to every ViaBTC alert channel. ViaBTC Watcher URL alert guide
Share View-Only Monitoring Access
When technicians, remote operators, or hosting partners need monitoring access, a Watcher URL can provide visibility without account-modification authority. ViaBTC allows anyone holding the link to view the information permitted by that Watcher configuration without logging in.
On the website, open Watcher Favorites → Create a Watcher, set the permissions and note, and complete the verification steps. Share only the visibility required for the work, keep the link secure, and remove access when it is no longer needed. Existing links can be managed through Manage Watcher(s). ViaBTC Watcher URL guide
The recipient can also configure the app-based Watcher alerts described above to support collaborative monitoring.
Troubleshoot Offline Workers and Rising Rejections
When a worker’s status or rejection pattern changes, use the dashboard to establish the scope before adjusting equipment:
- Configuration: confirm the pool address and full worker name against the relevant coin’s setup guide. For ViaBTC BTC mining, the password is optional; do not assume a missing password is the fault.
- Connectivity: check the miner’s connection, network cables, router, switch, and internet access. Compare other workers on the same network.
- Miner condition: inspect available temperature readings, fan operation, hashboard status, hardware errors, and logs. Check whether the machine is intentionally idle.
- Firmware: if the evidence suggests compatibility problems, consult the manufacturer’s guidance for the model and firmware in use.
- Follow-up: after resolving an issue, check that shares are being submitted and allow the pool’s reporting window to reflect the recovery.
ViaBTC’s rejection-rate troubleshooting guide describes a rate within 3% as its normal range. This is ViaBTC’s guidance, not a fixed industry standard or a target to aim for. Consider both the level and the pattern: a sudden increase warrants attention, and a persistently elevated rate should not be ignored simply because it has become the worker’s baseline. If configuration and connectivity appear normal but rejection rates remain high, ViaBTC recommends contacting support. ViaBTC rejection-rate troubleshooting
Use worker status, hashrate, shares, and local diagnostics to assess current operation. Payout history is not a live worker-health indicator because settlement and withdrawal timing can separate mining activity from visible payments.
Conclusion
Effective monitoring starts with distinct worker names, useful groups, and a consistent review of status, hashrate, and rejection patterns. Configure the appropriate alerts, investigate whether changes affect one machine or a wider group, and use local diagnostics to help identify the cause. Comparing readings over compatible periods makes it easier to distinguish normal variation from a problem that needs action.
FAQ
How do I monitor each ASIC separately?
Assign a distinct worker ID to each ASIC and confirm that each appears as a separate entry in the pool dashboard. Group those entries by site or rack to make filtering easier. Reusing one worker identity across machines can aggregate their activity.
Why does my pool dashboard show a different hashrate from my ASIC?
The readings can use different data sources and averaging periods. ViaBTC’s real-time pool reading covers the previous ten minutes. Check what period the ASIC’s displayed average covers; its screen refresh frequency is not the same as its averaging window. Investigate persistent differences alongside rejection rates and connectivity.
How long should I wait before assessing a newly connected worker?
ViaBTC’s BTC guide recommends checking operation after roughly 10–15 minutes of stabilization. It separately gives 10–20 minutes of continued operation for returning to active status after disconnection. You can inspect configuration and connectivity immediately; these waits concern interpreting pool data. ViaBTC BTC Mining
Does offline status mean the ASIC has failed?
No. It means the pool has not observed hashrate for its defined period. Network problems, incorrect configuration, planned downtime, and hardware faults can produce the same label.
Can a teammate receive alerts without full account access?
Yes. ViaBTC’s app supports offline and rejection-rate alerts through a Watcher URL. The link provides viewing access according to its permissions without authority to modify the account. Treat it as sensitive information. Watcher URL alert setup
Is a 3% rejection rate an industry standard?
No. The figure comes from ViaBTC’s troubleshooting guidance. Assess the worker’s rejection level and changes over time, and investigate persistent problems rather than treating 3% as a universal target or cutoff.