History log of /dovecot/src/lib/lib-event-private.h
Revision Date Author Comments Expand
ddd5a0932db39f7336123f5089fdd77f6a38bce6 17-Dec-2017 Timo Sirainen <timo.sirainen@dovecot.fi>

lib: Add event_send()

68f5234e8c0a79b72546e1b1013aae4b86f394a4 17-Dec-2017 Timo Sirainen <timo.sirainen@dovecot.fi>

lib: Rename event_send() to event_vsend()

b63e20ea9bc84f1aa90a551f217d01385e070b73 13-Dec-2017 Timo Sirainen <timo.sirainen@dovecot.fi>

lib-master: Add stats-client Enable it if MASTER_SERVICE_FLAG_SEND_STATS is set

c6ab22366939966e59492b29fd42a350d54331f0 13-Dec-2017 Timo Sirainen <timo.sirainen@dovecot.fi>

lib: Add event filtering to debug logging

53ea4ad7b37e6c78a834151cdc30374316da4e34 13-Dec-2017 Timo Sirainen <timo.sirainen@dovecot.fi>

lib: Add event_import() and event_export()

b8a1347a9ea2cecf0d16f24748c2600fea8c7158 13-Dec-2017 Timo Sirainen <timo.sirainen@dovecot.fi>

lib: Add event API The events are hierarchical and the child events inherit the parents' fields. The events will be attached to "objects", which gives them some context. For example each mail user, mailbox and mail will have its own event. The events can also have a log prefix, so logging events to e.g. mail will always log a consistent prefix that identifies which mail is being logged about. The events will also be used for statistics. Typically this is done by logging a debug event, which contains fields that are interesting for statistics. The interesting events will have a name, which can be used to identify them when configuring which statistics are wanted to be tracked. It's possible to also track events that have no name, but that requires using the source code's filename:line as the event name. That of course may change between releases, so it's not very reliable.