:plugin: unix :type: input :default_codec: line /////////////////////////////////////////// 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}s-{plugin}"] === Unix input plugin include::{include_path}/plugin_header.asciidoc[] ==== Description Read events over a UNIX socket. Like `stdin` and `file` inputs, each event is assumed to be one line of text. Can either accept connections from clients or connect to a server, depending on `mode`. [id="plugins-{type}s-{plugin}-ecs"] ==== Compatibility with the Elastic Common Schema (ECS) This plugin adds extra fields about the event's source. Configure the <> option if you want to ensure that these fields are compatible with {ecs-ref}[ECS]. These fields are added after the event has been decoded by the appropriate codec, and will not overwrite existing values. |======== | ECS Disabled | ECS v1 , v8 | Description | `host` | `[host][name]` | The name of the {ls} host that processed the event | `path` | `[file][path]` | The socket path configured in the plugin |======== [id="plugins-{type}s-{plugin}-options"] ==== Unix Input Configuration Options This plugin supports the following configuration options plus the <> described later. [cols="<,<,<",options="header",] |======================================================================= |Setting |Input type|Required | <> |<>|No | <> |<>|No | <> |<>|No | <> |<>, one of `["server", "client"]`|No | <> |<>|Yes | <> |<>|Yes |======================================================================= Also see <> for a list of options supported by all input plugins.   [id="plugins-{type}s-{plugin}-data_timeout"] ===== `data_timeout` * Value type is <> * Default value is `-1` The 'read' timeout in seconds. If a particular connection is idle for more than this timeout period, we will assume it is dead and close it. If you never want to timeout, use -1. [id="plugins-{type}s-{plugin}-ecs_compatibility"] ===== `ecs_compatibility` * Value type is <> * Supported values are: ** `disabled`: uses backwards compatible field names, such as `[host]` ** `v1`, `v8`: uses fields that are compatible with ECS, such as `[host][name]` Controls this plugin's compatibility with the {ecs-ref}[Elastic Common Schema (ECS)]. See <> for detailed information. **Sample output: ECS enabled** [source,ruby] ----- { "@timestamp" => 2021-11-16T13:20:06.308Z, "file" => { "path" => "/tmp/sock41299" }, "host" => { "name" => "deus-ex-machina" }, "message" => "foo" } ----- **Sample output: ECS disabled** [source,ruby] ----- { "@timestamp" => 2021-11-16T13:20:06.308Z, "path" => "/tmp/sock41299", "host" => "deus-ex-machina", "message" => "foo" } ----- [id="plugins-{type}s-{plugin}-force_unlink"] ===== `force_unlink` * Value type is <> * Default value is `false` Remove socket file in case of EADDRINUSE failure [id="plugins-{type}s-{plugin}-mode"] ===== `mode` * Value can be any of: `server`, `client` * Default value is `"server"` Mode to operate in. `server` listens for client connections, `client` connects to a server. [id="plugins-{type}s-{plugin}-path"] ===== `path` * This is a required setting. * Value type is <> * There is no default value for this setting. When mode is `server`, the path to listen on. When mode is `client`, the path to connect to. [id="plugins-{type}s-{plugin}-socket_not_present_retry_interval_seconds"] ===== `socket_not_present_retry_interval_seconds` * This is a required setting. * Value type is <> * Default value is `5` Amount of time in seconds to wait if the socket file is not present, before retrying. Only positive values are allowed. This setting is only used if `mode` is `client`. [id="plugins-{type}s-{plugin}-common-options"] include::{include_path}/{type}.asciidoc[] :default_codec!: