Millisecond log timestamp (option) #27313

1. 
   Sjors commented at 2:21 pm on March 23, 2023: member

   Please describe the feature you’d like to see added.

   For some events, like two blocks at the same height being announced by multiple peers at the same time, it’s nice to have millisecond precision on the log entries.

   Is your feature related to a problem, if so please describe it.

   E.g. one of the ForkMonitor nodes saw two blocks at height 782,129 within the same second: https://twitter.com/BitMEXResearch/status/1638875082943520769

   Other nodes saw those blocks in the opposite order.

   Describe the solution you’d like

   Something like -logtimestampprecision= which would second by default, with millisecond as an option.

   Log entries would look like:

   02023-03-22T15:53:29Z
   

   Describe any alternatives you’ve considered

   A more fancy solution would allow a custom date formatter.

   Please leave any additional context

   No response

2. Sjors added the label Feature on Mar 23, 2023
3. 
   fanquake commented at 2:26 pm on March 23, 2023: member

   Does -logtimemicros not work
4. 
   Sjors commented at 2:33 pm on March 23, 2023: member

   Ah oops, I only searched for documented options. Yes that works.
5. Sjors closed this on Mar 23, 2023

   ---

6. 
   Sjors commented at 2:39 pm on March 23, 2023: member

   Might be worth promoting this from OptionsCategory::DEBUG_TEST to OptionsCategory::OPTIONS, since it’s useful beyond debugging the software.
7. bitcoin locked this on Mar 22, 2024

Contributors
Sjors fanquake

Labels
Feature