Effective mining operations need proactive monitoring: you want to know about a problem before it costs you hashrate. Foreman's Alerts & Triggers page lets you watch for the conditions you care about and respond automatically, whether that's notifying your team, rebooting a miner, or opening a ticket.
What You'll Accomplish
By the end of this module, you will have:
- Learned how a trigger is built: which miners to check, what to check for, and what to do
- Created your first alerts so your team hears about critical problems right away
- Automated common fixes so simple issues resolve without anyone stepping in
Alerts vs. Triggers
In Foreman, everything starts with a trigger, which is a rule that says "when this happens to these miners, do this." An alert is one of the actions a trigger can take.
- Alert only: Pickaxe goes offline → send an alert to your team
- Automatic fix: a miner reports zero hashrate → restart the miner
- Both: a miner's pool settings are changed → put the correct pools back and send an alert
Letting triggers fix routine problems on their own means fewer alerts for your team, and the alerts they do get are the ones that need a person.
Note: If you don't see the Add Trigger button, your role may not have permission to manage triggers. Contact your organization's Foreman administrator.
Step 1: Understand the Parts of a Trigger
Go to Alerts & Triggers in the left-hand menu and click Add Trigger. Every trigger has three parts.
Miners to Check
Choose which miners the trigger watches.
- First box: Any, All, A Count Of, or A Percentage Of. Any fires for each miner that meets the condition. A Count Of and A Percentage Of fire only when that many miners meet it at once, which is useful for spotting site-wide problems.
- Second box: Miner(s) (all miners), Miner(s) Matching, or Miner(s) Excluding. Matching and Excluding let you pick a grouping, such as a site, Pickaxe, or miner type, and then the values to include or leave out.
- Add Condition lets you combine groupings with AND/OR.
Note: If you choose A Count Of or A Percentage Of, Send Alert is the only action available.
What to Check For
Choose Trips a(n) (the condition happens) or Doesn't Trip a(n) (the condition fails to happen, available for some conditions). Then pick the condition:
- Miner Health: a miner reports a warning or failing health status
- Miner Hash Rate / Zero Hash Rate: hashrate falls below your threshold, or to zero
- Not Updating: a miner hasn't sent data for the set period
- No Submitted Shares: a miner has stopped submitting shares to its pool
- Miner Fan Speed / Missing Fan: fan speed is out of range, or a fan isn't detected
- Missing Hash Board / Miner Hardware Errors: hardware problems on the miner
- Miner Rebooted: a miner rebooted unexpectedly
- Pickaxe Offline: a Pickaxe agent has gone offline
- No Pools Configured / Invalid Pools Configured: a miner's pool settings are missing or don't match your trusted pools
- Time Interval, Minute Of Hour, Minute of Day: run on a schedule (times are in UTC)
- Remote File Contains: a specific string appears in a remote file or log
Depending on the condition, you'll also set whether to fire on Failure or Warning, and how many intervals the condition must last before the trigger acts. Each interval is about one minute.
What to Do
Choose one or more actions:
- Send Alert: notify your team. Destinations include All Emails, Specific Emails, Slack, Discord, Google Chat, and Telegram.
- Restart Miners: restart the mining process (fast, software-level)
- Reboot Miners: full power cycle, for unresponsive miners
- Create Ticket: open a ticket with an assignee and priority, so the issue is tracked to resolution
- Change Pools: push a pool configuration to the miner (covered in Module 3)
- Fan Adjustments, Change Overclock, Change Power Mode, Set Power Target: adjust how the miner runs
- Change Client, Factory Reset, Run Script: advanced actions. Use Factory Reset with caution.
When you're done, click Add Trigger to save. New triggers are active by default.
Step 2: Create Your Essential Alerts
Start with these four. They cover the problems that cost the most hashrate when nobody notices them.
1. Pickaxe Offline
- Miners to Check: Any / Miner(s)
- What to Check For: Trips a(n) Pickaxe Offline Trigger, 1–3 intervals
- What to Do: Send Alert to your on-call channel
- Why: If Pickaxe is offline, Foreman can't see or control anything at that site. This is your most important alert.
Step-by-step guide: How To: Set Up A Trigger To Detect When Your Pickaxe Goes Offline
2. Site-Wide Outage
- Miners to Check: A Percentage Of (for example, 10%) / Miner(s) Matching your site
- What to Check For: Trips a(n) Not Updating Trigger, 5 intervals
- What to Do: Send Alert
- Why: Many miners dropping at once usually means a power, network, or cooling problem, not a miner problem. One alert tells you to look at the site.
3. Hardware Problems
- Miners to Check: Any / Miner(s)
- What to Check For: Trips a(n) Missing Hash Board Trigger (create a second trigger for Missing Fan)
- What to Do: Create Ticket, assigned to your repair team
- Why: A restart won't fix missing hardware. A ticket makes sure someone goes to the rack.
Related: How To: Set Up An Alert For Low Fan Speed
4. Low Hashrate
- Miners to Check: Any / Miner(s) Matching a miner type (hashrate expectations differ by model)
- What to Check For: Trips a(n) Miner Hash Rate Trigger, below about 85–90% of the model's expected hashrate, for 15–30 intervals
- What to Do: Send Alert or Create Ticket
- Why: Catches failing hash boards and cooling issues before the miner goes down completely.
Step 3: Automate Common Fixes
1. Restart Miners That Stop Hashing
- Miners to Check: Any / Miner(s)
- What to Check For: Trips a(n) No Submitted Shares Trigger, 10–20 intervals
- What to Do: Restart Miners (or Reboot Miners for models that need a full power cycle)
- Why: Offline miners, miners with no hashrate, and miners with a broken pool connection all stop submitting shares, so one trigger catches all three. This is usually the most valuable trigger you'll create.
Pair it with the Miner Rebooted condition and an alert if you want to know when the same miners keep needing a restart.
2. Reboot on Hardware Errors
- What to Check For: Trips a(n) Miner Hardware Errors Trigger, 10 intervals
- What to Do: Reboot Miners
3. Fix Unauthorized Pool Changes
- What to Check For: Trips a(n) Invalid Pools Configured, 1–5 intervals
- What to Do: Change Pools and Send Alert
- Why: Puts your miners back on your pools if anyone or any other tool changes them. This requires trusted pools, which are set up in Module 3: Managing Mining Pools.
More examples: Best Practices: Configure Foreman To Automatically Fix My Miners
Step 4: Manage and Review Your Triggers
Every trigger appears in the Trigger Data Table. Click the expand button on a row to see its history: when it fired, which miners were involved, which conditions were met, and which actions ran.
From the ellipses menu on each trigger you can:
- View details
- Change status to pause or reactivate a trigger without deleting it
- Edit
- Duplicate to copy a trigger for another site or miner type
- Delete
Best Practices
Avoid Alert Fatigue
- Use a few intervals, not one, for conditions that flicker (hashrate, Not Updating). Brief blips resolve on their own.
- Let restart and reboot triggers handle routine problems, and alert only on what needs a person.
- Send different priorities to different places, such as an on-call Slack channel for critical alerts and email for everything else.
- Review your triggers monthly and adjust or pause any that fire constantly without leading to action.
Tune Your Thresholds
- Start with the suggestions in this module.
- Watch the trigger history for one to two weeks.
- Raise intervals or thresholds on triggers that fire without a real problem.
- Write down what you changed and why, so the next person understands the setup.
Roll Out in Phases
- Week 1: Pickaxe Offline and Site-Wide Outage alerts
- Weeks 2–4: Restart on No Submitted Shares, hardware tickets, and low hashrate alerts
- Month 2+: Pool protection, scheduled actions, and power mode changes
Know How Triggers Interact with Power Controls
Trigger actions that send commands to miners, such as restarts and pool changes, are skipped while a site is in an active demand response dispatch. You'll still be alerted, and the action can run once the dispatch ends.
Common Issues
Trigger isn't firing:
- Check that the trigger's status is active.
- Check that the miners you expect match the Miners to Check settings.
- Check the interval count. The condition has to last the full number of intervals.
Too many alerts:
- Raise the interval count or the threshold.
- Replace per-miner alerts with an automatic fix, or switch to A Count Of / A Percentage Of so you get one alert per event.
Action didn't run:
- Expand the trigger's history to see what happened.
- Make sure Pickaxe is online and can reach the miner.
- Check whether a dispatch was active at the time.
Alert emails aren't arriving:
- Check your spam folder and add Foreman to your allowed senders.
- Confirm that Subscribed to Alert Emails is on in My Account.
- For Slack, follow How To: Receive Alerts Via Slack.
Recommended Starter Setup
- ✓ Pickaxe Offline → Send Alert
- ✓ 10% of a site Not Updating → Send Alert
- ✓ No Submitted Shares (10–20 intervals) → Restart Miners
- ✓ Missing Hash Board / Missing Fan → Create Ticket
- ✓ Low Hash Rate (per miner type) → Send Alert
- ✓ Invalid Pools Configured → Change Pools + Send Alert (after Module 3)
For a full reference of every option, see Quick Guide: Alerts & Triggers.
What's Next?
Your team now hears about problems quickly, and routine problems fix themselves.
Next Article: Module 3: Managing Mining Pools – Change pools across your fleet and protect against unauthorized pool changes.