ZeroMQ-based Log Message broker
required.
% cmake .
% make
% make install
| command | description |
|---|---|
| zlmb-server | server application |
| name | description |
|---|---|
| mode | execute mode |
| client_frontendpoint | client fronend endpoint |
| client_backendpoints | client backend endpoints |
| client_dumpfile | client error file |
| client_dumptype | client error type |
| publish_frontendpoint | publish frontend point |
| publish_backendpoint | publish backendend point |
| publish_key | publish key string |
| publish_sendkey | enable sending publish key |
| subscribe_frontendpoints | subscribe frontend points |
| subscribe_backendpoint | subscribe backendend point |
| subscribe_key | subscribe key string |
| subscribe_dropkey | enable dropped subscribe key |
| subscribe_dumpfile | subscribe error file |
| subscribe_dumptype | subscribe error type |
| config | config file path |
| info | application information |
| syslog | log to syslog |
| verbose | verbosity log |
| help | help |
-
client
receive messages in a specified value of a client_frontendpoint. send a message to the specified value of the client_backendpoints. (More than one can be specified) client_dumpfile tries to send the message that if you can not connect the client_backendpoints outputs.
Usage
% zlmb-server --mode client --client_frontendpoint tcp://127.0.0.1:5557 --client_backendpoints tcp://127.0.0.1:5558,tcp://127.0.0.1:6668Assumptions used
Daemon to run on the same server and client applications.
-
publish
receive messages in a specified value of a publish_frontendpoint. send a message to the specified value of the publish_backendpoint. sends the publish key to the first frame when it is defined the publish_sendkey. publish key that is sent is specified by the publish_key. (the default value is empty) messages that have been received from the other if there is no connection for the publish_backendpoint are discarded.
Usage
% zlmb-server --mode publish --publish_frontendpoint tcp://127.0.0.1:5558 --publish_backendpoint tcp://127.0.0.1:5559 (--publish_key test --publish_sendkey)Assumptions used
Distributed to the server that distributes the message from the client server to handle.
-
subscribe
receive messages in a specified value of a subscribe_frontendpoints. (More than one can be specified) send a message to the specified value of the subscribe_backendpoint. subscribe_dumpfile tries to send the message that if you can not connect the subscribe_backendpoints outputs. subscribe key that is receive is specified by the subscribe_key. (the default value is empty) not send backendpoint the first frame received is defined if you subscribe_dropkey.
Usage
% zlmb-server --mode subscribe --subscribe_frontendpoints tcp://127.0.0.1:5559,tcp://127.0.0.1:6669 --subscribe_backendpoint tcp://127.0.0.1:5560 (--subscribe_key test --subscribe_dropkey)Assumptions used
Send me worker program for the received message.
-
client-publish
run a server that has the function of publish and client.
Usage
% zlmb-server --mode client-publish --client_frontendpoint tcp://127.0.0.1:5557 --publish_backendpoint tcp://127.0.0.1:5559 (--publish_key test --publish_dropkey) -
publish-subscribe
run a server that has the function of publish and subscribe.
Usage
% zlmb-server --mode publish-subscribe --publish_frontendpoint tcp://127.0.0.1:5558 --subscribe_backendpoint tcp://127.0.0.1:5560 -
client-subscribe
run a server that has the function of client and subscribe.
Usage
% zlmb-server --mode client-subscribe --client_frontendpoint tcp://127.0.0.1:5557 --client_backendpoints tcp://127.0.0.1:5558 --subscribe_frontendpoint tcp://127.0.0.1:5559 --subscribe_backendpoint tcp://127.0.0.1:5560 (--subscribe_key test --subscribe_dropkey) -
stand-alone
run a server that has the function of client, publish and subscribe.
Usage
zlmb-server --mode stand-alone --client_frontendpoint tcp://127.0.0.1:5557 --subscribe_backendpoint tcp://127.0.0.1:5560
You can also read from a file format that is specified in the config yaml configuration options.
Best options that you specified earlier in the option argument is used on a priority basis.
Usage
% zlmb-server --mode client --config config.yml
Configuration file, see config.yml.
If the syslog option is set, a log message is output via syslog.
If I were to take effect (snappy) compress option at compile time, to compress the message at the time sent from the client to publish message will be thawed in time to be sent to the worker from subscribe. (cmake -DUSE_SNAPPY=ON)
| command | description |
|---|---|
| zlmb-cli | client application |
| zlmb-dump | dump message application |
| zlmb-worker | worker server |
send a message to zlmb-server from the command line.
zlmb-cli [-e ENDPOINT] [-f FILE] [-m NUM] [ARGS ...]
| name | description |
|---|---|
| endpoint (e) | connect server endpoint (DEFAULT: tcp://127.0.0.1:5557) |
| filename (f) | input file name or 'stdin' |
| multipart (m) | send multi-part message size |
-
send to 'test' and 'message'.
% zlmb-cli -e tcp://127.0.0.1:5557 test message
-
send to 2 part message.
% zlmb-cli -e tcp://127.0.0.1:5557 -m 2 test message
-
send to file (filename: test.txt).
send one line at a time.
% zlmb-cli -e tcp://127.0.0.1:5557 -f test.txt
-
send to stdin.
% echo 'message' | zlmb-cli -e tcp://127.0.0.1:5557 -f stdin
-
send to stdin and multi part.
% echo 'message' | zlmb-cli -e tcp://127.0.0.1:5557 -f stdin -m 2 tag
% cat test.txt | zlmb-cli -e tcp://127.0.0.1:5557 -f stdin -m 2 tag
Reprocess messages that have been output by the dumpfile(dumptype:binary) of zlmb-server. Processing can be performed or retransmission of the message. Please note that from being truncated is read dumpfile.
zlmb-dump [-e ENDPOINT] [-c] FILE
| name | description |
|---|---|
| endpoint (e) | send server endpoint |
| continue (c) | continue end of file |
% zlmb-dump /tmp/zlmb-client-dump.dat
% zlmb-dump -e tcp://127.0.0.1:5557 /tmp/zlmb-client-dump.dat
Because you will need to restart the program itself as well each time you update the processing for messages that are received by the above-mentioned cases of Worker, Worker server becomes a simple program to call the CGI.
zlmb-worker [-e ENDPOINT] [-c COMMAND] [-t NUM] [ARGS ...]
| name | description |
|---|---|
| endpoint (e) | server endpoint |
| command (c) | command path |
| thread (t) | command thread count (DEFAULT: 1) |
% zlmb-worker --endpoint tcp://127.0.0.1:5560 -c path/to/exec -t 3
Input information to the worker program, the environment variable is done by standard input.
Worker program (path/to/exec) is executed the message was received.
Worker programs (path/to/exec) can be run a few minutes maximum thread count.
- ZLMB_FRAME: The number of frames received on ZeroMQ
- ZLMB_FRAME_LENGTH: The length of each frame ZeroMQ (separator ":")
- ZLMB_LENGTH: The length of the message received by the ZeroMQ (Total of ZLMB_FRAME_LENGTH)
Message received by the ZeroMQ
Client program sends a message to connect to the client_frontendpoint.
Worker program to receive messages connected to subscribe_backendpoint, do any processing.
Example of worker program to start at zlmb-worker.