:plugin: gelf :type: input /////////////////////////////////////////// START - GENERATED VARIABLES, DO NOT EDIT! /////////////////////////////////////////// :version: %VERSION% :release_date: %RELEASE_DATE% :changelog_url: %CHANGELOG_URL% :include_path: ../../../../logstash/docs/include /////////////////////////////////////////// END - GENERATED VARIABLES, DO NOT EDIT! /////////////////////////////////////////// [id="plugins-{type}-{plugin}"] === Gelf input plugin include::{include_path}/plugin_header.asciidoc[] ==== Description This input will read GELF messages as events over the network, making it a good choice if you already use Graylog2 today. The main use case for this input is to leverage existing GELF logging libraries such as the GELF log4j appender. A library used by this plugin has a bug which prevents it parsing uncompressed data. If you use the log4j appender you need to configure it like this to force gzip even for small messages: [id="plugins-{type}s-{plugin}-options"] ==== Gelf Input Configuration Options This plugin supports the following configuration options plus the <> described later. [cols="<,<,<",options="header",] |======================================================================= |Setting |Input type|Required | <> |<>|No | <> |<>|No | <> |<>|No | <> |<>|No |======================================================================= Also see <> for a list of options supported by all input plugins.   [id="plugins-{type}s-{plugin}-host"] ===== `host` * Value type is <> * Default value is `"0.0.0.0"` The IP address or hostname to listen on. [id="plugins-{type}s-{plugin}-port"] ===== `port` * Value type is <> * Default value is `12201` The port to listen on. Remember that ports less than 1024 (privileged ports) may require root to use. [id="plugins-{type}s-{plugin}-remap"] ===== `remap` * Value type is <> * Default value is `true` Whether or not to remap the GELF message fields to Logstash event fields or leave them intact. Remapping converts the following GELF fields to Logstash equivalents: * `full\_message` becomes `event.get("message")`. * if there is no `full\_message`, `short\_message` becomes `event.get("message")`. [id="plugins-{type}s-{plugin}-strip_leading_underscore"] ===== `strip_leading_underscore` * Value type is <> * Default value is `true` Whether or not to remove the leading `\_` in GELF fields or leave them in place. (Logstash < 1.2 did not remove them by default.). Note that GELF version 1.1 format now requires all non-standard fields to be added as an "additional" field, beginning with an underscore. e.g. `\_foo` becomes `foo` [id="plugins-{type}s-{plugin}-common-options"] include::{include_path}/{type}.asciidoc[]