|
1 | 1 | { |
2 | | - ##### The Basics ##### |
3 | | - |
4 | 2 | # Enable or disable logging overall |
5 | 3 | TurnOnLogging = true; |
6 | 4 |
|
|
11 | 9 | # Use the modern tracing system instead of the legacy tracing system. |
12 | 10 | UseTraceDispatcher = true; |
13 | 11 |
|
14 | | - ##### TODO: TITLE ##### |
15 | | - |
16 | 12 | # Match the metrics prefix of the legacy tracing system to minimize breaking |
17 | 13 | # changes. |
18 | 14 | TraceOptionMetricsPrefix = "cardano.node.metrics."; |
|
27 | 23 | # The frequency of resource messages. |
28 | 24 | TraceOptionResourceFrequency = 1000; |
29 | 25 |
|
30 | | - # TODO: Fix up following calcs in description |
31 | | - # |
32 | | - # Queue size control: |
33 | | - # In case of a missing forwarding service consumer, traces messages will be |
| 26 | + # Queue size control: y |
| 27 | + # In case of a missing forwarding service consumer, trace messages will be |
34 | 28 | # buffered. This mitigates short forwarding interruptions, or delays at |
35 | 29 | # startup time. |
36 | 30 | # |
37 | 31 | # The queue capacity should thus correlate to the expected log lines per |
38 | 32 | # second given a particular tracing configuration - to avoid unnecessarily |
39 | 33 | # increasing memory footprint. |
40 | 34 | # |
41 | | - # The default values here are chosen to accommodate verbose tracing output |
42 | | - # (i.e., buffering 1min worth of trace data given ~32 messages per second). A |
43 | | - # config that results in less than 5 msgs per second should also provide |
44 | | - # TraceOptionForwarder queue size values considerably lower. The |
45 | | - # `disconnQueueSize` is the hard limit in that case. |
46 | | - # |
47 | | - # The queue sizes tie in with the max number of trace objects cardano-tracer |
48 | | - # requests periodically, the default for that being 100. Here, the basic |
49 | | - # queue can hold enough traces for 10 subsequent polls. |
| 35 | + # The maxReconnectDelay config option specifies the maximum delay in seconds |
| 36 | + # between (re-)connection attempts of a forwarder (default: 60s). |
50 | 37 | TraceOptionForwarder = { |
51 | 38 | connQueueSize = 64; |
52 | 39 | disconnQueueSize = 128; |
| 40 | + maxReconnectDeplay = 60; |
53 | 41 | }; |
54 | 42 |
|
| 43 | + # Tracing options for node |
55 | 44 | TraceOptions = { |
| 45 | + # The default tracer configuration |
56 | 46 | "" = { |
57 | 47 | backends = [ |
58 | | - "Stdout HumanFormatColoured" |
| 48 | + # None, any combination, or all of the following backends can be |
| 49 | + # enabled, where `EKGBackend` forwards EKG resource status to |
| 50 | + # cardano-tracer, `Forwarder` forwards message traces and |
| 51 | + # `PrometheusSimple` serves cardano-node metrics directly from |
| 52 | + # cardano-node. |
59 | 53 | "EKGBackend" |
60 | 54 | "Forwarder" |
| 55 | + "PrometheusSimple 127.0.0.1 12799" |
| 56 | + |
| 57 | + # Only one of the following can be enabled, which determines for format |
| 58 | + # of node logging to stdout. |
| 59 | + "Stdout HumanFormatColoured" |
| 60 | + # "Stdout HumanFormatUncoloured" |
| 61 | + # "Stdout MachineFormat" |
61 | 62 | ]; |
62 | 63 |
|
| 64 | + # Each tracer can specify the level of details for printing messages. |
| 65 | + # Options include `DMinimal`, `DNormal`, `DDetailed`, and `DMaximum`. If |
| 66 | + # no implementation is given, `DNormal` is chosen. |
63 | 67 | detail = "DNormal"; |
| 68 | + |
| 69 | + # The severity levels, ranging from the least severe (`Debug`) to the |
| 70 | + # most severe (`Emergency`), provide a framework for ignoring messages |
| 71 | + # with severity levels below a globally configured severity cutoff. |
| 72 | + # |
| 73 | + # The full list of severities are: |
| 74 | + # `Debug`, `Info`, `Notice`, `Warning`, `Error`, `Critical`, `Alert` and |
| 75 | + # `Emergency`. |
| 76 | + # |
| 77 | + # To enhance severity filtering, there is also the option of `Silence` |
| 78 | + # which allows for the unconditional silencing of a specific trace, |
| 79 | + # essentially representing the deactivation of tracers -- a semantic |
| 80 | + # continuation of the functionality in the legacy system. |
64 | 81 | severity = "Notice"; |
65 | 82 | }; |
66 | 83 |
|
| 84 | + # The following tracer configurations are configured to closely match the |
| 85 | + # default logging seen in the legacy cardano-node tracing system. |
67 | 86 | "BlockFetch.Decision" = { |
68 | 87 | severity = "Silence"; |
69 | 88 | }; |
|
120 | 139 | severity = "Info"; |
121 | 140 | }; |
122 | 141 |
|
| 142 | + |
| 143 | + |
123 | 144 | "Net.Mux.Remote" = { |
124 | 145 | severity = "Info"; |
125 | 146 | }; |
|
141 | 162 | }; |
142 | 163 |
|
143 | 164 | "ChainDB.AddBlockEvent.AddedBlockToQueue" = { |
| 165 | + # A frequency limit for the number of messages per second may also be |
| 166 | + # provided for any tracer. |
144 | 167 | maxFrequency = 2.0; |
145 | 168 | }; |
146 | 169 |
|
|
159 | 182 | "BlockFetch.Client.CompletedBlockFetch" = { |
160 | 183 | maxFrequency = 2.0; |
161 | 184 | }; |
| 185 | + |
| 186 | + # Uncomment UTXO-HD tracer adjustments for cardano-node 10.4 |
| 187 | + # |
| 188 | + # These messages are UTxO-HD specific. On a regular node, the tracing |
| 189 | + # system might warn at startup about config inconsistencies as those |
| 190 | + # tracers do not exist. This warning is expected, and can be safely |
| 191 | + # ignored. Silencing the tracers below aims at having a comparable log line |
| 192 | + # rates in messages per second on both the UTxO-HD and regular node. |
| 193 | + # "ChainDB.LedgerEvent.Forker".severity = "Silence"; |
| 194 | + # "Mempool.AttemptAdd".severity = "Silence"; |
| 195 | + # "Mempool.AttemptingSync".severity = "Silence"; |
| 196 | + # "Mempool.LedgerFound".severity = "Silence"; |
| 197 | + # "Mempool.LedgerNotFound".severity = "Silence"; |
| 198 | + # "Mempool.SyncDone".severity = "Silence"; |
| 199 | + # "Mempool.SyncNotNeeded".severity = "Silence"; |
| 200 | + |
| 201 | + # Enable this to investigate transaction validation errors. |
| 202 | + # "Mempool.RejectedTx".detail = "DDetailed"; |
162 | 203 | }; |
163 | 204 | } |
0 commit comments