[zeromq-dev] Logging format for sys://log transport
Mikko Koppanen
mikko.koppanen at gmail.com
Mon Nov 15 21:30:48 CET 2010
Hello,
short background (and correct me if something is wrong here):
The sys://log transport is an internal transport, a PUB socket
providing logging information on what happens inside 0MQ. The
information has not yet been defined but probably contains things such
as severity, event type and message associated with the event.
The question is how structure this information in the most effective
way? One way would be to use severity as the topic and allow user to
subscribe to all events above let's say level warning but this still
leaves the question about the data format inside the message. My
current thinking leans on something like:
struct zmq_event_t {
uint8_t severity;
uint16_t type;
char *message;
};
where type could be something like ZMQ_EVENT_CONNECT,
ZMQ_EVENT_DISCONNECT, ZMQ_EVENT_HWM_REACHED and so on.
However this probably doesn't include all possible use-cases so it
would be nice to hear ideas on what would be the best way to organise
this information.
--
Mikko Koppanen
More information about the zeromq-dev
mailing list