Write events over a TCP socket.
Each event json is separated by a newline.
Can either accept connections from clients or connect to a server,
depending on mode
.
output {
tcp {
codec => ... # codec (optional), default: "plain"
host => ... # string (required)
mode => ... # string, one of ["server", "client"] (optional), default: "client"
port => ... # number (required)
reconnect_interval => ... # number (optional), default: 10
workers => ... # number (optional), default: 1
}
}
The codec used for output data. Output codecs are a convenient method for encoding your data before it leaves the output, without needing a separate filter in your Logstash pipeline.
Only handle events without any of these tags. Note this check is additional to type and tags.
When mode is server
, the address to listen on.
When mode is client
, the address to connect to.
The format to use when writing events to the file. This value supports any string and can include %{name} and other dynamic strings.
If this setting is omitted, the full json representation of the event will be written as a single line.
Mode to operate in. server
listens for client connections,
client
connects to a server.
When mode is server
, the port to listen on.
When mode is client
, the port to connect to.
When connect failed,retry interval in sec.
Only handle events with all of these tags. Note that if you specify a type, the event must also match that type. Optional.
The type to act on. If a type is given, then this output will only act on messages with the same type. See any input plugin’s “type” attribute for more. Optional.
The number of workers to use for this output. Note that this setting may not be useful for all outputs.