11.8 Monitoring Settings

Within the network configuration files, validators can adjust which metrics are exposed to allow more detailed Grafana Dashboard insights. By default, the LUKSO Network Configuration already exposes Ports and APIs for every consensus client. Extended access or data can be enabled individually.

Support

The Nimbus-Eth2 client is not supported for Staking within the LUKSO CLI. Additionally, the consensus client requires a custom --validator-monitor-details flag to expose regular blockchain metrics. When using the LUKSO CLI, the dashboard will still lack metrics until staking is fully supported.

tip

Further details on client versions and support can be found on the Client Providers page in the 🧠 Theory section.

info

The following steps are performed on your 📟 node server.

Add Validator Metrics

If you are running the Nimbus-Eth2 consensus client and lack dashboard metrics, you can enable advanced validator monitoring.

👾 LUKSO CLI

1. Stop Node Operation: Depending on your setup method, there are different ways to stop your node to adjust configurations.

LUKSO CLI

cd <lukso-working-directory>
lukso stop

info

Exchange <lukso-working-directory> with the path of the node folder.

Service Automation

sudo systemctl stop lukso-validator

Force Client Shutdown

Geth

sudo pkill geth

Erigon

sudo pkill erigon

Nethermind

nethermind --version

Besu

besu --version

Nimbus-Eth2

sudo pkill nimbus_beacon_node
sudo pkill nimbus_validator_client

2. Adjust Validator Metrics: Modify the default validator configuration of Nimbus-Eth2 using your preferred editor.

Vim

cd <lukso-working-directory>/configs/<network>
vim nimbus2/nimbus.toml

Nano

cd <lukso-working-directory>/configs/<network>
nano nimbus2/nimbus.toml

info

Exchange <lukso-working-directory> and <network> with the path of the node folder and the network type.

Add the validator monitor details setting to enable extended metrics.

validator-monitor-details = true

Save the file and exit the editor.

3. Restart the Node: Depending on your setup, there are different ways to start your node with the updated configuration.

LUKSO CLI Node

cd <lukso-working-directory>
lukso start --checkpoint-sync

info

Exchange <lukso-working-directory> with the path of the node folder.

LUKSO CLI Validator

cd <lukso-working-directory>
lukso start --validator --transaction-fee-recipient "<your-fee-recipient-address>" --checkpoint-sync

info

The following properties need to be exchanged:

• <lukso-working-directory> with the path of the node folder
• <your-fee-recipient-address> with the wallet address receiving staking profits

Service Automation

sudo systemctl start lukso-validator

After the clients were started, verify that their services are still up.

sudo lukso status

🐳 Docker Image

1. Stop Node Operation: Stop the docker containers for both execution and consensus clients.

2. Adjust Validator Metrics: Open the docker-compose.yml file of Nimbus-Eth2, add validator monitoring, and safe the file.

  --validator-monitor-details

3. Restart the Node: Restart the docker containers for execution and consensus clients.

🗂️ Custom Setup

1. Stop Node Operation: Stop the execution and consensus services.

File Configuration

2. Adjust Validator Metrics: Adjusting the nimbus.toml_ file within your setup using your preferred text editor.

Vim

vim nimbus2/nimbus.toml

Nano

nano nimbus2/nimbus.toml

Add the validator monitor details setting to enable extended metrics.

validator-monitor-details = true

Save the file and exit the editor.

3. Restart the Node: Restart the execution and consensus services.

Flag Customization

2. Custom Restart: Restart the service and attach a customization flag for your monitor setting.

  --validator-monitor-details