[zeromq-dev] Monitoring and management question

Martin Sustrik sustrik at 250bpm.com
Thu Dec 23 09:32:40 CET 2010

On 12/23/2010 12:47 AM, Paul Colomiets wrote:

> Or even maybe socket type, which could look like:
>      sock = ctx.socket(zmq.MONITOR)
>      sock.bind('inproc://connections')
>      realsock = ctx.socket(zmq.REQ)
>      realsock.connect('inproc://connections')
>      realsock.send("active")
>      print realsock.recv()

Yes. It's done that way. The only difference is that you use zmq.SUB 
instead of zmq.MONITOR and "sys://log" instead of "inproc://connections".

> This way monitoring capabilities can be directly exposed to the
> monitoring software on the network.
> This way you will make improper usage of this information more hard.

It's not particularly hard. I mean, as hard as to prevent unappropriate 

What would do would be reporting is such a format that it can't be 
parsed by a machine, say "There are three hundred and twenty three 
connections and seven thousand five hundred and seven messages queued 
altogether." with some randomisation in the word order and spelling as 
to confuse parsers.

Not really a neat solution :)


More information about the zeromq-dev mailing list