feat!: Enable Traefik metrics, rename common label var, README fixes

This commit is contained in:
hatemosphere
2024-03-06 15:25:59 +01:00
parent 41f491a0bd
commit 478c3f7ab9
5 changed files with 46 additions and 51 deletions

View File

@ -1,12 +1,21 @@
# ansible-en-role # ansible-en-role
Ansible role for setup external node.
Ansible role to deploy and configure zkSync Era External Node, including DB isntance setup on the same machine, Traefik as reverse proxy, and Prometheus monitoring (PostgreSQL exporter, Node exporter, cAdvisor, Traefik, External Node native metrics, and VictoriaMetrics vmagent to scrape all of them).
Make sure to configure Prometheus remote write endpoint to send metrics to centralized metrics storage.
Role has been tested and used internally on bare metal Hetzner instances.
## Requirements ## Requirements
This role has been tested on: This role has been tested on:
* Ubuntu 22.04, Jammy Jellyfish; Ansible 2.13.9 * Ubuntu 22.04, Jammy Jellyfish; Ansible 2.13.9
## Usage ## Usage
This role contains variables which has to be set: This role contains variables which has to be set:
```yaml ```yaml
database_name: "" database_name: ""
database_username: "" database_username: ""
@ -17,7 +26,8 @@ l1_chain_id: ""
l2_chain_id: "" l2_chain_id: ""
``` ```
If you want to use monitoring, you can use next variables: If you want to use monitoring (which we highly recommend), you have to change these variables:
```yaml ```yaml
# Monitoring options section # Monitoring options section
enable_monitoring: false enable_monitoring: false
@ -27,11 +37,11 @@ prometheus_remote_write_url: ""
prometheus_remote_write_auth: false prometheus_remote_write_auth: false
prometheus_remote_write_auth_username: "" prometheus_remote_write_auth_username: ""
prometheus_remote_write_auth_password: "" prometheus_remote_write_auth_password: ""
prometheus_remote_write_label: "" prometheus_remote_write_common_label: ""
``` ```
This role also has option to secure your server and allow traffic only from specified ip in case if you want This role also has option to secure your server and allow traffic only from specified IP address in case if you want
to use some load balancer in front of your node: to use some load balancer in front of your node, while not having fancy cloud security groups at your disposal:
```yaml ```yaml
# Security options # Security options
@ -40,13 +50,13 @@ disable_ssh_password_auth: false
iptables_packages: iptables_packages:
- iptables - iptables
- iptables-persistent - iptables-persistent
# Variable can be used in case with accept external traffic only from one ip # Variable to be used to accept external traffic only from single specified IP
loadbalancer_ip: "" loadbalancer_ip: ""
``` ```
In some cases, you may need to change postgres parameters, so you can do it using `postgres_arguments` variable: In most of cases, you'd want to change PostgreSQL parameters (we recommend to use <https://pgtune.leopard.in.ua/> with "Online transaction processing system" preset as sane defaults), so you can do it using `postgres_arguments` variable, eg:
```yaml
```yaml
postgres_arguments: postgres_arguments:
- log_error_verbosity=terse - log_error_verbosity=terse
- -c - -c
@ -54,49 +64,24 @@ postgres_arguments:
- -c - -c
- shared_buffers=47616MB - shared_buffers=47616MB
- -c - -c
- effective_cache_size=142848MB
- -c
- maintenance_work_mem=2GB
- -c
- checkpoint_completion_target=0.9
- -c
- wal_buffers=16MB
- -c
- default_statistics_target=500
- -c
- random_page_cost=1.1
- -c
- effective_io_concurrency=200
- -c
- work_mem=2573kB
- -c
- huge_pages=try
- -c
- min_wal_size=4GB
- -c
- max_wal_size=16GB
- -c
- max_worker_processes=74
- -c
- max_parallel_workers_per_gather=37
- -c
- max_parallel_workers=74
- -c
- max_parallel_maintenance_workers=4
- -c
- checkpoint_timeout=1800
``` ```
We recommend to use [pgtune](https://github.com/le0pard/pgtune) to choose optimal config for your hardware.
We recommend using [online]<https://pgtune.leopard.in.ua/> or [self-hosted](https://github.com/le0pard/pgtune) version with with "Online transaction processing system" preset as a good starting point for generating optimal config for your hardware.
## Step-by-step guide ## Step-by-step guide
1. Install ansible collection on your machine from where you will run ansible: 1. Install ansible collection on your machine from where you will run ansible:
`ansible-galaxy collection install community.general` `ansible-galaxy collection install community.general`
2. Prepare latest database backup on your host. you can download it from our [public GCS bucket](https://storage.googleapis.com/zksync-era-mainnet-external-node-backups/external_node_latest.pgdump). 2. Prepare latest database backup on your host. you can download it from our [public GCS bucket](https://storage.googleapis.com/zksync-era-mainnet-external-node-backups/external_node_latest.pgdump).
you should place it to `{{ storage_directory }}/pg_backups` directory. By default, `{{ storage_directory }}` is `/usr/src/en` you should place it to `{{ storage_directory }}/pg_backups` directory. By default, `{{ storage_directory }}` is `/usr/src/en`
3. **OPTIONAL**: If you already have external-node, you can copy tree directory to new host. Copy external-node database tree to `{{ storage_directory }}/db`.
**Keep in mind, tree should be older than postgres database backup.** 3. **OPTIONAL**: If you already have external-node, you can copy tree directory to new host. Copy external-node database tree to `{{ storage_directory }}/db`.
**Keep in mind, tree should be older than PostgreSQL database backup.**
4. Run ansible-playbook using this role. We recommend to encrypt next variables with ansible-vault or some another way: 4. Run ansible-playbook using this role. We recommend to encrypt next variables with ansible-vault or some another way:
``` ```
database_username database_username
database_password database_password
@ -104,8 +89,8 @@ eth_l1_url
vm_auth_username vm_auth_username
vm_auth_password vm_auth_password
``` ```
5. Connect to your host, and see status of postgres container. It can take a lot of time before postgres database backup will be restored
and postgres server will be ready for use. After postgres goes healty status, external-node runs automatically. 5. Connect to your host, and see status of `postgres` container. It can take a lot of time before PostgreSQL database backup will be restored (hours to days, depending on your disk throughput and IOPS), after which PostgreSQL server will be ready for use. Once `postgres` becomes "healthy", `external_node` runs automatically.
## Example Playbook ## Example Playbook
@ -131,9 +116,9 @@ and postgres server will be ready for use. After postgres goes healty status, ex
## License ## License
Ansible role for external node is distributed under the terms of either Ansible role for zkSync Era External Node is distributed under the terms of either
- Apache License, Version 2.0, ([LICENSE-APACHE](LICENSE-APACHE) or <http://www.apache.org/licenses/LICENSE-2.0>) * Apache License, Version 2.0, ([LICENSE-APACHE](LICENSE-APACHE) or <http://www.apache.org/licenses/LICENSE-2.0>)
- MIT license ([LICENSE-MIT](LICENSE-MIT) or <https://opensource.org/blog/license/mit/>) * MIT license ([LICENSE-MIT](LICENSE-MIT) or <https://opensource.org/blog/license/mit/>)
at your option. at your option.

View File

@ -57,7 +57,6 @@ postgres_arguments:
- -c - -c
- checkpoint_timeout=1800 - checkpoint_timeout=1800
# Enable TLS for traefik # Enable TLS for traefik
enable_tls: false enable_tls: false
acme_email: "" acme_email: ""
@ -87,7 +86,7 @@ prometheus_remote_write_url: ""
prometheus_remote_write_auth: false prometheus_remote_write_auth: false
prometheus_remote_write_auth_username: "" prometheus_remote_write_auth_username: ""
prometheus_remote_write_auth_password: "" prometheus_remote_write_auth_password: ""
prometheus_remote_write_label: "" prometheus_remote_write_common_label: ""
# Security options # Security options
use_predefined_iptables: false use_predefined_iptables: false

View File

@ -16,6 +16,9 @@ services:
- "--certificatesresolvers.en_resolver.acme.storage=/letsencrypt/acme.json" - "--certificatesresolvers.en_resolver.acme.storage=/letsencrypt/acme.json"
- "--certificatesresolvers.myresolver.acme.email={{ acme_email }}" - "--certificatesresolvers.myresolver.acme.email={{ acme_email }}"
{% endif %} {% endif %}
- "--metrics.prometheus=true"
- "--metrics.prometheus.entryPoint=metrics"
- "--entryPoints.metrics.address=:8080"
volumes: volumes:
- "/var/run/docker.sock:/var/run/docker.sock" - "/var/run/docker.sock:/var/run/docker.sock"
{% if enable_tls %} {% if enable_tls %}

View File

@ -9,7 +9,7 @@ services:
command: command:
{% if prometheus_remote_write %} {% if prometheus_remote_write %}
- "--remoteWrite.url={{ prometheus_remote_write_url }}" - "--remoteWrite.url={{ prometheus_remote_write_url }}"
- "--remoteWrite.label={{ prometheus_remote_write_label }}" - "--remoteWrite.label={{ prometheus_remote_write_common_label }}"
{% if prometheus_remote_write_auth %} {% if prometheus_remote_write_auth %}
- "--remoteWrite.basicAuth.username={{ prometheus_remote_write_auth_username }}" - "--remoteWrite.basicAuth.username={{ prometheus_remote_write_auth_username }}"
- "--remoteWrite.basicAuth.password={{ prometheus_remote_write_auth_password }}" - "--remoteWrite.basicAuth.password={{ prometheus_remote_write_auth_password }}"

View File

@ -38,3 +38,11 @@ scrape_configs:
- source_labels: [instance] - source_labels: [instance]
target_label: instance target_label: instance
replacement: '{{ node_name | mandatory }}' replacement: '{{ node_name | mandatory }}'
- job_name: traefik
static_configs:
- targets:
- "traefik:8080"
relabel_configs:
- source_labels: [instance]
target_label: instance
replacement: '{{ node_name | mandatory }}'