Skip to content

Commit 2cbebf2

Browse files
Merge pull request OffchainLabs#2663 from OffchainLabs/add-checklist-to-valnode
add monitoring to the valnode docs
2 parents a174104 + 15e4d08 commit 2cbebf2

File tree

1 file changed

+15
-1
lines changed

1 file changed

+15
-1
lines changed

docs/run-arbitrum-node/more-types/04-run-split-validator-node.mdx

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,9 +45,12 @@ docker run --rm -it \
4545
--auth.origins 0.0.0.0 \
4646
--auth.jwtsecret /tmp/nitro-val.jwt \
4747
--auth.port 5200
48+
--metrics \
49+
--metrics-server.addr=0.0.0.0 \
50+
--metrics-server.port=6070
4851
```
4952

50-
The validation node will listen on port 5200.
53+
The validation node will listen on port 5200, which will also enable the metrics server on port 6070.
5154

5255
#### Step 2: Set up the staker node
5356

@@ -150,3 +153,14 @@ docker run --rm -it --entrypoint nitro-val @@latestNitroNodeImage=offchainlabs/
150153
### Additional configurations for helm charts
151154

152155
For more advanced helm chart configurations, please refer to the Arbitrum community Helm Chart [README](https://github.com/OffchainLabs/community-helm-charts/blob/main/charts/nitro/README.md)
156+
157+
### Monitoring
158+
159+
To check if your validation node is running correctly, you can check the `rpc_duration_validation_validate_success_count` metric in your metrics server.
160+
161+
This metric is a counter of the number of successful validation calls; if it is increasing, it means your validation node is running correctly.
162+
163+
You can also check where this log (`validation node started`) appears:
164+
165+
- If this log appears on the validation node, it means your validation node is running correctly.
166+
- If this log appears on the staker node (validator node), it means your staker node is still validating itself. It indicates that your staker node is not connecting to the validation node correctly; you need to double-check your configuration.

0 commit comments

Comments
 (0)