bump chronicles to a5c81f3012d7a397e608cfe3d861c02419fa731e (#5634)

- abbreviate `NOTICE` with `NTC` instead of `NOT`

docs/the_nimbus_book/src/el-light-client.md

@@ -161,7 +161,7 @@ You should see logs similar to the following:
 ### Nimbus
 
 ```
-NOT 2022-11-21 18:00:23.666+01:00 Starting light client                      topics="lightcl" trusted_block_root=some(c092a1d110a1c8d630ac2c3fa2565813d43087f42c986855a2cd985b995a328c)
+NTC 2022-11-21 18:00:23.666+01:00 Starting light client                      topics="lightcl" trusted_block_root=some(c092a1d110a1c8d630ac2c3fa2565813d43087f42c986855a2cd985b995a328c)
 ...
 INF 2022-11-21 18:01:24.001+01:00 Slot start                                 slot=1109707 epoch=34678 sync=bootstrapping(c092a1d110a1c8d630ac2c3fa2565813d43087f42c986855a2cd985b995a328c) peers=5 head=fb9b64fe:0 finalized=fb9b64fe:0 delay=1ms495us
 INF 2022-11-21 18:01:24.734+01:00 Exchanged engine configuration             topics="eth1" terminalTotalDifficulty=17000000000000000 terminalBlockHash=0x0000000000000000000000000000000000000000000000000000000000000000 terminalBlockNumber=0
@@ -178,13 +178,13 @@ INF 2022-11-21 18:03:27.984+01:00 New LC optimistic header                   opt
 WRN 2022-11-21 18:03:31.419+01:00 Peer count low, no new peers discovered    topics="networking" discovered_nodes=0 new_peers=@[] current_peers=7 wanted_peers=160
 INF 2022-11-21 18:03:36.001+01:00 Slot start                                 slot=1109718 epoch=34678 sync=synced peers=7 head=c5464508:1109716 finalized=c092a1d1:1109216 delay=1ms98us
 INF 2022-11-21 18:03:40.012+01:00 New LC optimistic header                   optimistic_header="(beacon: (slot: 1109717, proposer_index: 835, parent_root: \"c5464508\", state_root: \"13f823f8\"))"
-NOT 2022-11-21 18:03:40.012+01:00 New LC optimistic block                    opt=99ab28aa:1109717 wallSlot=1109718
+NTC 2022-11-21 18:03:40.012+01:00 New LC optimistic block                    opt=99ab28aa:1109717 wallSlot=1109718
 WRN 2022-11-21 18:03:40.422+01:00 Peer count low, no new peers discovered    topics="networking" discovered_nodes=1 new_peers=@[] current_peers=7 wanted_peers=160
 INF 2022-11-21 18:03:48.001+01:00 Slot start                                 slot=1109719 epoch=34678 sync=synced peers=7 head=99ab28aa:1109717 finalized=c092a1d1:1109216 delay=1ms53us
 WRN 2022-11-21 18:03:50.205+01:00 Peer count low, no new peers discovered    topics="networking" discovered_nodes=0 new_peers=@[] current_peers=7 wanted_peers=160
 INF 2022-11-21 18:04:00.001+01:00 Slot start                                 slot=1109720 epoch=34678 sync=synced peers=7 head=99ab28aa:1109717 finalized=c092a1d1:1109216 delay=1ms145us
 INF 2022-11-21 18:04:03.982+01:00 New LC optimistic header                   optimistic_header="(beacon: (slot: 1109718, proposer_index: 1202, parent_root: \"99ab28aa\", state_root: \"7f7f88d2\"))"
-NOT 2022-11-21 18:04:03.982+01:00 New LC optimistic block                    opt=ab007266:1109718 wallSlot=1109720
+NTC 2022-11-21 18:04:03.982+01:00 New LC optimistic block                    opt=ab007266:1109718 wallSlot=1109720
 ```
 
 !!! note

docs/the_nimbus_book/src/logging.md

@@ -3,9 +3,6 @@
 Nimbus offers several options for logging.
 By default, logs are written to stdout using the [chronicles](https://github.com/status-im/nim-chronicles#introduction) `textlines` format which is convenient to read and can be used with tooling for [heroku/logfmt](https://brandur.org/logfmt).
 
-!!! tip
-    `NOT` at the beginning of a log line means `NOTICE`.
-
 ## Change log level
 
 You can customise Nimbus' verbosity with the `--log-level` option.
@@ -54,4 +51,3 @@ To send logs to a file, you can redirect the stdout logs:
 
 We recommend keeping an eye on the growth of this file with a [log rotator](./log-rotate.md).
 Logs are written in the "JSON Lines" format - one `json` entry per line.
-

docs/the_nimbus_book/src/pi-guide.md

@@ -403,10 +403,10 @@ INF 2023-10-01 11:25:34.556+01:00 Loading block dag from database            top
 INF 2023-10-01 11:25:35.921+01:00 Block dag initialized
 INF 2023-10-01 11:25:37.073+01:00 Generating new networking key
 ...
-NOT 2023-10-01 11:25:45.267+00:00 Local validator attached                   tid=22009 file=validator_pool.nim:33 pubkey=95e3cbe88c71ab2d0e3053b7b12ead329a37e9fb8358bdb4e56251993ab68e46b9f9fa61035fe4cf2abf4c07dfad6c45 validator=95e3cbe8
+NTC 2023-10-01 11:25:45.267+00:00 Local validator attached                   tid=22009 file=validator_pool.nim:33 pubkey=95e3cbe88c71ab2d0e3053b7b12ead329a37e9fb8358bdb4e56251993ab68e46b9f9fa61035fe4cf2abf4c07dfad6c45 validator=95e3cbe8
 ...
-NOT 2023-10-01 11:25:59.512+00:00 Eth1 sync progress                         topics="eth1" tid=21914 blockNumber=3836397 depositsProcessed=106147
-NOT 2023-10-01 11:26:02.574+00:00 Eth1 sync progress                         topics="eth1" tid=21914 blockNumber=3841412 depositsProcessed=106391
+NTC 2023-10-01 11:25:59.512+00:00 Eth1 sync progress                         topics="eth1" tid=21914 blockNumber=3836397 depositsProcessed=106147
+NTC 2023-10-01 11:26:02.574+00:00 Eth1 sync progress                         topics="eth1" tid=21914 blockNumber=3841412 depositsProcessed=106391
 ...
 INF 2023-10-01 11:26:31.000+00:00 Slot start                                 topics="beacnde" tid=21815 file=nimbus_beacon_node.nim:505 lastSlot=96566 scheduledSlot=96567 beaconTime=1w6d9h53m24s944us774ns peers=7 head=b54486c4:96563 headEpoch=3017 finalized=2f5d12e4:96479 finalizedEpoch=3014
 INF 2023-10-01 11:26:36.285+00:00 Slot end                                   topics="beacnde" tid=21815 file=nimbus_beacon_node.nim:593 slot=96567 nextSlot=96568 head=b54486c4:96563 headEpoch=3017 finalizedHead=2f5d12e4:96479 finalizedEpoch=3014

docs/the_nimbus_book/src/run-a-validator.md

@@ -123,12 +123,9 @@ We'll import the signing key of each validator to the [data directory](./data-di
 
 On success, a message will be printed that your keys have been imported:
 ```
-NOT 2022-07-19 17:36:37.578+02:00 Keystore imported
+NTC 2022-07-19 17:36:37.578+02:00 Keystore imported
 ```
 
-!!! note ""
-    `NOT` is short for `NOTICE` and not not :)
-
 After importing keys, it is time to [restart the node](./run-a-validator.md#3-start-validating) and check that the keys have been picked up by the beacon node.
 
 !!! info "All the keys"
@@ -210,7 +207,7 @@ To check that keys were imported correctly, look for `Local validator attached`
 ```
 INF 2020-11-18 11:20:00.181+01:00 Launching beacon node
 ...
-NOT 2020-11-18 11:20:02.091+01:00 Local validator attached
+NTC 2020-11-18 11:20:02.091+01:00 Local validator attached
 ```
 
 Congratulations!

docs/the_nimbus_book/src/start-syncing.md

@@ -49,8 +49,8 @@ INF 2023-10-01 11:25:34.556+01:00 Loading block dag from database            top
 INF 2023-10-01 11:25:35.921+01:00 Block dag initialized
 INF 2023-10-01 11:25:37.073+01:00 Generating new networking key
 ...
-NOT 2023-10-01 11:25:59.512+00:00 Eth1 sync progress                         topics="eth1" tid=21914 blockNumber=3836397 depositsProcessed=106147
-NOT 2023-10-01 11:26:02.574+00:00 Eth1 sync progress                         topics="eth1" tid=21914 blockNumber=3841412 depositsProcessed=106391
+NTC 2023-10-01 11:25:59.512+00:00 Eth1 sync progress                         topics="eth1" tid=21914 blockNumber=3836397 depositsProcessed=106147
+NTC 2023-10-01 11:26:02.574+00:00 Eth1 sync progress                         topics="eth1" tid=21914 blockNumber=3841412 depositsProcessed=106391
 ...
 INF 2023-10-01 11:26:31.000+00:00 Slot start                                 topics="beacnde" tid=21815 file=nimbus_beacon_node.nim:505 lastSlot=96566 scheduledSlot=96567 beaconTime=1w6d9h53m24s944us774ns peers=7 head=b54486c4:96563 headEpoch=3017 finalized=2f5d12e4:96479 finalizedEpoch=3014
 INF 2023-10-01 11:26:36.285+00:00 Slot end                                   topics="beacnde" tid=21815 file=nimbus_beacon_node.nim:593 slot=96567 nextSlot=96568 head=b54486c4:96563 headEpoch=3017 finalizedHead=2f5d12e4:96479 finalizedEpoch=3014

docs/the_nimbus_book/src/suggested-fee-recipient.md

@@ -51,6 +51,6 @@ If this Nimbus node has two validators, one of which has its own suggested fee r
 The configured fee recipient for every validator is logged at startup:
 
 ```
-NOT 2022-11-10 08:27:02.530+01:00 Local validator attached ...
+NTC 2022-11-10 08:27:02.530+01:00 Local validator attached ...
     initial_fee_recipient=70E47C843E0F6ab0991A3189c28F2957eb6d3842
 ```

docs/the_nimbus_book/src/validator-monitor.md

@@ -45,7 +45,7 @@ Other nodes pick it up and package the message into an aggregate and later a blo
 The block is included in the canonical chain and a reward is given two epochs (~13 minutes) later.
 
 The monitor tracks each of these actions and will in detailed mode log each step at the `INF` level.
-If any step is missed (irrespective of detail mode), a `NOT` log is shown instead.
+If any step is missed (irrespective of detail mode), a `NTC` log is shown instead.
 
 The typical life cycle of an attestation might look something like the following:
 
@@ -57,10 +57,10 @@ INF 2021-11-22 11:33:07.193+01:00 Attestation included in block              att
 
 The life cycle of a particular message can be traced by following the `epoch=.... validator=...` fields in the message.
 
-Failures at any point are recorded at a higher logging level, such as `NOT`(ice):
+Failures at any point are recorded at a higher logging level, such as `NTC`:
 
 ```
-NOT 2021-11-17 20:53:42.108+01:00 Attestation failed to match head           topics="chaindag" epoch=81972 validator=...
+NTC 2021-11-17 20:53:42.108+01:00 Attestation failed to match head           topics="chaindag" epoch=81972 validator=...
 ```
 
 Failures are reported with a lag of two epochs (~13 minutes).

ncli/logtrace.nim

@@ -159,7 +159,7 @@ type
     # The message structure is as follows:
     #[
       {
-        "lvl": "NOT",
+        "lvl": "NTC",
         "ts": "2022-11-21 23:02:37.032+02:00",
         "msg": "Block sent",
         "topics": "beacval",