Checking Correct Operation

Validators can check this dashboard to see whether they are executing Jito properly. Note, there is some lag since it requires a leader slot to confirm full functionality.

In order to check correct operation of the validator from logs when connected to the relayer and block engine, one can look for the following metrics emitted in the validator logfile:

• block_engine_stage-stats: emitted once per second when connected to the block engine.

• relayer_stage-stats: emitted once per second when connected to the relayer.

The validator will periodically re-authenticate with the block engine and relayers. To ensure that's happening, you can look for:

• auth_tokens_update_loop-tokens_generated: emitted infrequently when the validator authenticates with the block engine and relayer.

• auth_tokens_update_loop-refresh_access_token: emitted semi-frequently when the validator refreshes access tokens.

If the above log lines aren't being emitted, you can look for the following log lines:

• relayer_stage-wait_for_auth + block_engine_stage-wait_for_auth: emitted when waiting to authenticate with the relayer and block engine.

• auth_tokens_update_loop-refresh_connect_error: emitted when the validator can't connect to the relayer and/or relayer. check the url for which one is having issues connecting.

• auth_tokens_update_loop-refresh_loop_error: emitted when there's an error refreshing authentication tokens.

• relayer_stage-connect_error + block_engine_stage-connect_error:errors connecting to the relayer or block engine.

• relayer_stage-stream_error + block_engine_stage-stream_error: errors streaming from the relayer or block engine.

Note: As always, this code is expected to change. Please check out block_engine_stage.rs and relayer_stage.rs for the most up-to-date metrics.