boot: turn trace logs for boot-01 nodes

> Configuration for status.sharding.bootstrap
> 1 node in this fleet should preferably be set up with trace-level message logs, in order
> to facilitate future end-to-end message tracing and debugging

https://github.com/status-im/infra-shards/issues/2
This commit is contained in:
Anton Iakimov 2023-09-29 13:09:53 +02:00
parent 6d0c2c49e5
commit 5d78944b7b
No known key found for this signature in database
GPG Key ID: DEA1FE58DD8BF7FA
2 changed files with 1 additions and 3 deletions

View File

@ -3,8 +3,7 @@
# Tag dependent on fleet: test
nim_waku_cont_tag: 'deploy-shards-{{ stage }}'
nim_waku_cont_name: 'nim-waku-boot'
# TODO: switch for traces foe 1 node in host_vars
nim_waku_log_level: 'debug'
nim_waku_log_level: "{{ 'trace' if ansible_hostname == 'boot-01' else 'debug' }}"
nim_waku_protocols_enabled: ['relay', 'filter', 'lightpush', 'peer-exchange']
nim_waku_disc_v5_enabled: true
nim_waku_dns4_domain_name: '{{ dns_entry }}'

View File

@ -3,7 +3,6 @@
# Tag dependent on fleet: test
nim_waku_cont_tag: 'deploy-shards-{{ stage }}'
nim_waku_cont_name: 'nim-waku-store'
# TODO: switch for traces foe 1 node in host_vars
nim_waku_log_level: 'debug'
nim_waku_protocols_enabled: ['relay', 'store']
nim_waku_disc_v5_enabled: true