Choose the tab for your consensus client. Paste the following configuration into the file.
global:
scrape_interval: 15s # By default, scrape targets every 15 seconds.
# Attach these labels to any time series or alerts when communicating with
# external systems (federation, remote storage, Alertmanager).
external_labels:
monitor: 'codelab-monitor'
# A scrape configuration containing exactly one endpoint to scrape:
# Here it's Prometheus itself.
scrape_configs:
- job_name: 'node_exporter'
static_configs:
- targets: ['localhost:9100']
- job_name: 'lighthouse'
metrics_path: /metrics
static_configs:
- targets: ['localhost:8008']
- job_name: 'lighthouse_validator'
metrics_path: /metrics
static_configs:
- targets: ['localhost:8009']
global:
scrape_interval: 15s # By default, scrape targets every 15 seconds.
# Attach these labels to any time series or alerts when communicating with
# external systems (federation, remote storage, Alertmanager).
external_labels:
monitor: 'codelab-monitor'
# A scrape configuration containing exactly one endpoint to scrape:
# Here it's Prometheus itself.
scrape_configs:
- job_name: 'node_exporter'
static_configs:
- targets: ['localhost:9100']
- job_name: 'Nimbus'
metrics_path: /metrics
static_configs:
- targets: ['localhost:8008']
- job_name: 'Nimbus_Validator'
metrics_path: /metrics
static_configs:
- targets: ['localhost:8009']
global:
scrape_interval: 15s # By default, scrape targets every 15 seconds.
# Attach these labels to any time series or alerts when communicating with
# external systems (federation, remote storage, Alertmanager).
external_labels:
monitor: 'codelab-monitor'
# A scrape configuration containing exactly one endpoint to scrape:
# Here it's Prometheus itself.
scrape_configs:
- job_name: 'node_exporter'
static_configs:
- targets: ['localhost:9100']
- job_name: 'Teku'
metrics_path: /metrics
static_configs:
- targets: ['localhost:8008']
- job_name: 'Teku_Validator'
metrics_path: /metrics
static_configs:
- targets: ['localhost:8009']
global:
scrape_interval: 15s # By default, scrape targets every 15 seconds.
# Attach these labels to any time series or alerts when communicating with
# external systems (federation, remote storage, Alertmanager).
external_labels:
monitor: 'codelab-monitor'
# A scrape configuration containing exactly one endpoint to scrape:
# Here it's Prometheus itself.
scrape_configs:
- job_name: 'node_exporter'
static_configs:
- targets: ['localhost:9100']
- job_name: 'validator'
static_configs:
- targets: ['localhost:8009']
- job_name: 'Prysm'
static_configs:
- targets: ['localhost:8008']
global:
scrape_interval: 15s # By default, scrape targets every 15 seconds.
# Attach these labels to any time series or alerts when communicating with
# external systems (federation, remote storage, Alertmanager).
external_labels:
monitor: 'codelab-monitor'
# A scrape configuration containing exactly one endpoint to scrape:
# Here it's Prometheus itself.
scrape_configs:
- job_name: 'node_exporter'
static_configs:
- targets: ['localhost:9100']
- job_name: 'beacon'
metrics_path: /metrics
static_configs:
- targets: ['localhost:8008']
- job_name: 'validator'
metrics_path: /metrics
static_configs:
- targets: ['localhost:8009']
5. Setup prometheus for your execution client
Append the applicable job snippet for your execution client to the end of prometheus.yml.
Spacing matters. Ensure all job_name snippets are in alignment.
Symptom 2: Don't want to use SSH tunnels and you want to expose port 3000 to access Grafana, but understand the security concerns.
Solution 2: Open port 3000 in your ufw firewall. Access grafana at http://<node ipaddress>:3000
sudo ufw allow 3000
Example of Grafana Dashboards for each consensus client.
JSON download link:
Example of Grafana Dashboards for each execution client.
Example of Node-Exporter Dashboard
General system monitoring
Includes: CPU, memory, disk IO, network, temperature and other monitoring metrics。
8. Setup Alert Notifications
Setup alerts to get notified if your validators go offline.
Get notified of problems with your validators. Choose between email, telegram, discord or slack.
Option 1: Email Notifications
Sign up for an account
Verify your email
Search for your validator's public address
Add validators to your watchlist by clicking the bookmark symbol.
Option 2: Telegram Notifications
On the menu of Grafana, select Notification channels under the bell icon.
Click on Add channel.
Give the notification channel a name.
Select Telegram from the Type list.
Create a new telegram group.
Invite the bot to your new group.
Type at least 1 message into the group to initialize it.
In the JSON response, find and copy the Chat ID. Find it between **chat **and title. Example of Chat ID: -1123123123
"chat":{"id":-123123123,"title":
Paste the Chat ID into the corresponding field in Grafana.
Save and test the notification channel for your alerts.
Option 3: Discord Notifications
On the menu of Grafana, select Notification channels under the bell icon.
Click on Add channel.
Add a name to the notification channel.
Select Discord from the Type list.
Enter the Webhook URL in the Discord notification settings panel.
Click Send Test, which will push a confirmation message to the Discord channel.
Option 4: Slack Notifications
On the menu of Grafana, select Notification channels under the bell icon.
Click on Add channel.
Add a name to the notification channel.
Select Slack from the Type list.
Enter the Slack Incoming Webhook URL in the URL field.
Click Send Test, which will push a confirmation message to the Slack channel.
Example of how to create a SSH tunnel in Windows with :
Now you can access Grafana on your local machine by pointing a web browser to
Open
Set URL to
Download and save your consensus client's json file. More json dashboard options available below. [ | | | | | ]
Download and save your execution client's json file [ | | | | ]
Download and save a for general system monitoring
Troubleshooting common Grafana issues
Beacon Chain JSON Download link:
Validator Client JSON download link:
Credits:
JSON Download link:
Credits:
Credits:
Nimbus dashboard by metanull-operator
Credits:
Credits:
Credits:
JSON download link:
Credits:
Credits:
Credits:
Blob enabled dashboard:
Credits:
Credits:
Credits:
Credits:
Credits:
Visit
To complete the Telegram API settings, a Telegram channel and **bot **are required. For instructions on setting up a bot with @Botfather, see of the Telegram documentation. You need to create a BOT API token.
Visit where XXX:YYY is your BOT API Token.
Now you can create custom alerts from your dashboards.
To complete the set up, a Discord server (and a text channel available) as well as a Webhook URL are required. For instructions on setting up a Discord's Webhooks, see of their documentation.
For instructions on setting up a Slack's Incoming Webhooks, see of their documentation.
