How to use RigOnline for management? (Feature Guide)

Understanding RigOnline Dashboard Navigation

1. The main dashboard displays real-time hash rate metrics across all connected mining rigs, updated every 15 seconds without manual refresh.

2. Each rig appears as a tile with status indicators: green for active, yellow for warning, red for offline or error state.

3. Clicking a rig tile opens a dedicated view showing GPU temperature, fan speed, power draw, and accepted/rejected share counts.

4. The left sidebar contains collapsible sections labeled “Rigs”, “Pools”, “Alerts”, and “Reports”, each accessible with single-click navigation.

5. Hovering over any metric triggers a tooltip showing historical context—such as 1-hour deviation from baseline or 24-hour average comparison.

Configuring Mining Pools and Failover Settings

1. Under the “Pools” section, users can add up to eight primary pool entries per rig group, each requiring URL, port, wallet address, and worker name fields.

2. Failover logic is defined by priority order: if Pool A fails three consecutive connection attempts, RigOnline automatically switches to Pool B within 8.2 seconds.

3. Each pool supports custom difficulty settings—users may set static difficulty or enable auto-adjust based on rig hashrate stability over the last 30 minutes.

4. Pool authentication tokens are encrypted at rest using AES-256-GCM and never exposed in plain text, even in debug logs.

5. A live pool latency monitor runs continuously, displaying round-trip time in milliseconds next to each configured endpoint.

Managing Firmware and Driver Updates Remotely

1. The “Firmware & Drivers” tab lists all compatible versions for detected hardware models, including NVIDIA A100, AMD RX 7900 XTX, and Bitmain Antminer S19j Pro variants.

2. Updates are staged in batches: users select rigs by tag (e.g., “Basement-Cluster” or “GPU-Alpha”), then initiate deployment with a single confirmation.

3. Every firmware update includes a rollback snapshot taken automatically before flashing; restoration requires only selecting the prior version and clicking “Revert”.

4. Driver updates are verified via SHA-384 checksums before installation, and execution halts if signature validation fails.

5. Update progress is visible per rig with percentage completion, estimated time remaining, and current phase label such as “Verifying”, “Flashing”, or “Rebooting”.

Setting Up Custom Alert Triggers

1. Alerts support 12 condition types including GPU temp > 85°C, hash rate drop > 22% over 5 minutes, rejected shares > 3.7%, and power supply voltage variance > ±5%.

2. Notification channels include email, Telegram webhook, and SMS via Twilio integration—each configured independently per alert rule.

3. Alert suppression windows can be scheduled: for example, disable thermal alerts between 02:00–05:00 UTC to avoid false positives during low-load maintenance hours.

4. Each alert event generates a unique incident ID logged with timestamp, affected rig ID, triggering value, and contextual sensor readings from that exact moment.

5. Users may assign severity levels—Low, Medium, High, Critical—with corresponding color-coded badges and escalation paths defined in team permissions.

Frequently Asked Questions

Q: Can RigOnline manage ASICs and GPUs simultaneously in the same interface?Yes. RigOnline natively supports heterogeneous fleets. ASIC detection uses stratum protocol handshake analysis, while GPU rigs rely on NVML and ADL SDK hooks. Both appear under unified views with hardware-specific metrics.

Q: Is it possible to restrict access to certain rig groups for specific team members?Yes. Role-based access control allows administrators to assign permissions per rig group tag. A user assigned to “Test-Rigs” cannot view, modify, or trigger actions on rigs tagged “Production-Mainnet”.

Q: Does RigOnline store raw sensor data beyond 30 days?No. Raw telemetry is retained for exactly 30 calendar days. Aggregated hourly summaries persist for 365 days. Data deletion follows ISO/IEC 27001-compliant automated purging schedules.

Q: How does RigOnline handle time synchronization across globally distributed rigs?All rigs sync time via NTP servers hosted on RigOnline’s infrastructure. Each rig performs a time drift check every 90 seconds and adjusts system clock using slew mode to prevent abrupt jumps affecting mining software stability.