Read events over a 0MQ SUB socket.
You need to have the 0mq 2.1.x library installed to be able to use this input plugin.
The default settings will create a subscriber binding to tcp://127.0.0.1:2120 waiting for connecting publishers.
input {
zeromq {
add_field => ... # hash (optional), default: {}
address => ... # string (optional), default: "tcp://127.0.0.1:2120"
debug => ... # boolean (optional)
format => ... # ["plain", "json", "json_event"] (optional)
message_format => ... # string (optional)
mode => ... # ["server", "client"] (optional), default: "client"
queue => ... # string (optional), default: ""
queue_size => ... # number (optional), default: 20
tags => ... # array (optional)
type => ... # string (required)
}
}
Add a field to an event
0mq socket address to connect or bind to
Set this to true to enable debugging on an input.
The format of input data (plain, json, json_event)
If format is "json", an event sprintf string to build what the display @message should be given (defaults to the raw JSON). sprintf format strings look like %{fieldname} or %{@metadata}.
wether to bind ("server") or connect ("client") to the socket
0mq topic (Used with ZMQSUBSCRIBE, see http://api.zeromq.org/2-1:zmq-setsockopt for 'ZMQSUBSCRIBE: Establish message filter')
0mq queue size
Add any number of arbitrary tags to your event.
This can help with processing later.
Label this input with a type. Types are used mainly for filter activation.
If you create an input with type "foobar", then only filters which also have type "foobar" will act on them.
The type is also stored as part of the event itself, so you can also use the type to search for in the web interface.