Read gelf messages as events over the network.
This input is a good choice if you already use graylog2 today.
The main reasoning for this input is to leverage existing GELF logging libraries such as the gelf log4j appender
input {
gelf {
add_field => ... # hash (optional), default: {}
debug => ... # boolean (optional)
format => ... # ["plain", "json", "json_event"] (optional)
host => ... # string (optional), default: "0.0.0.0"
message_format => ... # string (optional)
port => ... # number (optional), default: 12201
remap => ... # boolean (optional), default: true
tags => ... # array (optional)
type => ... # string (required)
}
}
Add a field to an event
Set this to true to enable debugging on an input.
The format of input data (plain, json, json_event)
The address to listen on
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}.
The port to listen on. Remember that ports less than 1024 (privileged ports) may require root to use.
Whether or not to remap the gelf message fields to logstash event fields or leave them intact.
Default is true
Remapping converts the following gelf fields to logstash equivalents:
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.