Page locked

This page is currently locked for editing by another user. You have to wait until this user finishes editing or the lock expires.

Currently locked by: 172.71.222.225,40.77.167.19
Lock expires at: 2024/04/23 08:21 (14 min)

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

===== Dashboard - Harvesters =====

In the Harvesters tab, you can find useful information on your individual harvesters' performance in order to help you improve your farm. Specifically, it shows 
  * your last 24h points per harvester, 
  * your average time taken per harvester over 24h,
  * your last proof,
  * a timeline of the quality and quantity of your proofs in the last 24h


You can set the name for your harvesters in the [[poolinfo/dashboard/personalize|settings page]].

{{ :poolinfo:dashboard:dashboard_-_harvestersv2.png?800 |}}

If you select Partials (time) from the dropdown, you can see the time taken of your partials per harvester. By clicking a partial, you can even see from what plot the partial originated. There's no better way to monitor and improve your farm than this! 
{{:poolinfo:dashboard:dashboard_-_harvestersv2_partials.png|}}

If you are using docker or machinaris, your harester ID will by default reset on every start up.To prevent this: 

==== Official Docker ====
**Step 1:** On the first run of a harvester, launch of the container with the following  environment variables
    * ''keys'' set to ''copy''
    * ''ca'' mapping a copy of the ''.chia/mainnet/config/ssl/ca'' directory of the **farmer node**
This will create what's needed for the harvester to be authenticated with the farmer node with a ''chia init -c "ca"''

**Step 2:** If the communication between the harvester and the farmer is properly established, stop the container, and set ''keys'' to ''persistent''.
The harvester ID is now persistent, and will be perserved even when the container is upgraded.

==== Machinaris ====
  - Follow the instructions to run a remote harvester, machinaris automates the step 1 above
  - Stop the container, edit the ''docker-compose.yml'' and add ''- keys=persistent'' in the environment section. Rebuild the container (''docker compose up -d --force-recreate machinaris''), and you're done as above.