Opened 17 years ago

Closed 17 years ago

#49 closed enhancement (fixed)

log publisher should provide access to stored messages, not just new ones

Reported by: Brian Warner Owned by:
Priority: major Milestone: 0.2.5
Component: logging Version: 0.2.4
Keywords: Cc:

Description

The logport currently only offers subscribe(), which arranges for all subsequent log messages to be send to the subscriber. We need to offer a catchup= option, to get access to previously recorded messages that are still sitting in the circular buffers.

This would let the log gatherer see boot-time messages in Tahoe nodes, including the one that mentions version numbers.

It might be a good idea to have the log publisher emit a version-number log event immediately after the gatherer is subscribed, or provide a separate protocol method to deliver this information to the gatherer.

Change History (1)

comment:1 Changed 17 years ago by Brian Warner

Resolution: fixed
Status: newclosed

Fixed, in [1622117fa7e9f9f39d617a423b0a2edd7fba12ee].

There already exists a separate method to retrieve version numbers. It remains an open issue as to whether 'flogtool tail' ought to grab the versions or not. We might want a separate mode (flogtool query-version?) to just retrieve this information. Alternatively, it might be useful to have a header stored in the event pickle files that contains version information.

Note: See TracTickets for help on using tickets.