2

Log levels

Mamy Ratsimbazafy edited this page 2020-11-05 17:43:03 +01:00

Table of Contents

• Description/Philosophy

from

• https://github.com/status-im/nim-beacon-chain/issues/205
• https://github.com/status-im/nimbus-eth2/pull/1788

Description/Philosophy

• Fatal: ???
• Error: Bugs or critical unexpected behaviors, node cannot proceed with task, consistency compromised
• Warning: Expected behavior (file not found), node cannot proceed with task but can recover
• Notice: Start/quit, validator funds, own attestations, own blocks, finality checkpoints, (any) slashings
• Info: Important networking issues
• Debug: Common networking (new peers, kick peers, timeouts), consensus stages, block/attestation validation
• Trace: Keep-alive, routine schedule

Note: it is important not to fill disk with logs, this prevent analyzing them visually. Logs done at high frequency should be summarized even at trace level to avoid drowning other subsystem For example they can use an uint8 counter with

proc myHighFreqProc() =
  var counter {.threadvar.}: uint8
  if counter == 255:
    trace "Total of 255 myHighFreqProc call"
  counter += 1