Triggers overview

There are several triggers available on minerstat that can help you solve the different situations and improve your rig's overall performance.

Each trigger can be applied either to all workers or to certain groups of workers. If you want it to get apply only to one worker, you can put that worker in its special group on the worker's config page.

GPU temperature

GPU temperature trigger is checked every minute and gets fired once the temperature reaches a certain level that is selected in the trigger.

Possible actions: Restart software, Reboot machine, Shut down machine, Power cycle, Stop mining, Start mining, Set fans, and Webhook.

Note: If you select set fans for a trigger, we strongly recommend setting up at least two triggers: one for lower temperatures and one for higher temperatures.

Memory temperature

Memory temperature trigger works the same way as GPU temperatures trigger, but checks the memory temperatures of the GPU if this value is reported.

Possible actions: Restart software, Reboot machine, Shut down machine, Power cycle, Stop mining, Start mining, Set fans, and Webhook.

Note: If you select set fans for a trigger, we strongly recommend setting up at least two triggers: one for lower temperatures and one for higher temperatures.

GPU count

GPU count trigger is checked every 10 minutes and gets fired if the number of GPUs detected by the system is different than what you defined in the worker's config.

Possible actions: Reboot machine, Shut down machine, Power cycle, Stop mining, and Webhook.

Note: The number of GPUs has to be defined in the worker's config manually and doesn't get updated automatically by the system. Keep in mind to update the value, if you add or remove GPUs from the rig.

ASIC temperature

ASIC temperature trigger is checked every minute and gets fired once the temperature reaches a certain level that is selected in the trigger.

Possible actions: Reboot machine and Webhook.

Hashrate

Hashrate trigger is checked every 10 minutes and gets fired once there is a hashrate drop detected in comparison to the last hour of mining.

Possible actions: Restart software, Reboot machine, Shut down machine, Power cycle, Stop mining, Start mining, and Webhook.

Note: Since hashrate drop trigger checks charts and historical data of the rig, it won't get fired immediately, but with a minimum 10-minute delay. If hashrate drops to 0 MH/s, this means that the rig stopped mining and the event isn't detected as a hashrate drop.

Efficiency

The efficiency trigger is checked every 10 minutes and gets fired once there is an efficiency drop detected.

Possible actions: Restart software, Reboot machine, Shut down machine, Power cycle, Stop mining, Start mining, and Webhook.

Note: Since efficiency drop triggers checks charts and historical data of the rig, it won't get fired immediately, but with a minimum 10-minute delay. If efficiency drops to 0%, this means that the rig didn't function properly (as no accepted shares were detected) and the event isn't detected as an efficiency drop.

Consumption

The consumption trigger is checked every 10 minutes and gets fired once there is a consumption drop detected in comparison to the last hour of mining.

Possible actions: Restart software, Reboot machine, Shut down machine, Power cycle, Stop mining, Start mining, and Webhook.

Note: Since power drop triggers checks charts and historical data of the rig, it won't get fired immediately, but with a minimum 10-minute delay. If power drops to 0 W, this means that the rig stopped mining and the event isn't detected as a power drop.

Rejected shares

Rejected shares trigger is checked every 10 minutes and gets fired once the rejected shares are higher than a certain number that is selected in the trigger.

Possible actions: Restart software, Reboot machine, Shut down machine, Power cycle, Stop mining, Start mining, and Webhook.

Note: Since rejected shares trigger checks charts and historical data of the rig, it won't get fired immediately, but with a minimum 10-minute delay.

Time

Time trigger gets fired once the time is the same as the selected hour in the trigger.

Possible actions: Restart software, Reboot machine, Shut down machine, Power cycle, Stop mining, Start mining, Set fans, Set ClockTune, and Webhook.

Note: Time trigger is only available for full hours.

Unresponsive

The unresponsive trigger is checked every minute and gets fired once the unresponsive state is detected for the selected amount of time. An unresponsive state is also denoted with an offline state on your minerstat dashboard. The worker is unresponsive or offline when the minerstat software isn't responding. This state happens when the rig is shut down, in the first few seconds of boot, if there is no internet connection, or if minerstat software isn't properly running on the rig (even if the mining client is running).

Possible actions: Send email and Webhook.

Note: Unresponsive trigger can be used for sending yourself an email or firing a webhook, which can fire a hardware watchdog.

Idle

The idle trigger is checked every minute and gets fired once the idle state is detected for the selected amount of time. The worker is idle when the minerstat software is running, while the mining client isn't running (the worker is not mining). The idle state is normal in the first few seconds when you have just booted your rig. If an idle state happens after that, there is something unusual going on.

Possible actions: Restart software, Reboot machine, Shut down machine, and Webhook.

Inactive

The inactive trigger is checked every minute and gets fired once the inactive state is detected for a selected amount of time. The worker is inactive when the minerstat software and mining client are running, but the mining client reports 0 H/s (the worker is trying to mine, but there is an error that is interrupting it).

Possible actions: Restart software, Reboot machine, Shut down machine, Power cycle, and Webhook.

Earnings

The earnings trigger is checked every 10 minutes and gets fired once there is an earnings drop detected in comparison to the last hour of mining.

Possible actions: Restart profit switch and Webhook.

Note: Earnings drop trigger is useful if you have a profit switch with a longer minimum mining time and want to escape sudden profit drops that happen in between.

It's easy to get started and it's free

Use minerstat software and improve your mining operation

Sign up for free

Dashboard