7

I've found references in a few places to some internal logging capabilities of ZMQ. The functionality that I think might exist is the ability to connect to either or both of a inproc or ipc SUB socket and listen to messages that give information about the internal state of ZMQ. This would be quite useful when debugging a distributed application. For instance, if messages are missing/being dropped, it might shed some light on why they're being dropped.

The most obvious mention of this is here: http://lists.zeromq.org/pipermail/zeromq-dev/2010-September/005724.html, but it's also referred to here: http://lists.zeromq.org/pipermail/zeromq-dev/2011-April/010830.html. However, I haven't found any documentation of this feature.

Is some sort of logging functionality truly available? If so, how is it used?

scott
  • 1,127
  • 1
  • 12
  • 21

1 Answers1

7

Some grepping through the git history eventually answered my question. The short answer is that a way for ZMQ to transmit logging messages to the outside world was implemented, but it was never used to actually send logging messages by the rest of the code base. After a while it was removed since nothing used it.

The commit that originally added it making use of an inproc socket:

The commit that added a new "sys" socket type specifically to support the logging:

JIRA issue, pull request, and commit to remove the functionality:

scott
  • 1,127
  • 1
  • 12
  • 21
  • Glad you hunted it down. For what it's worth, `ZMQ_MONITOR` socket option can be used for some insight into the zmq internals, though not as much as this functionality would have allowed. – Michael Greene Apr 09 '13 at 19:02