# unix

The `in_unix` Input plugin enables Fluentd to retrieve records from the Unix Domain Socket. The wire protocol is the same as [`in_forward`](https://docs.fluentd.org/input/forward), but the transport layer is different.

It is included in Fluentd's core.

## Example Configuration

```
<source>
  @type unix
  path /path/to/socket.sock
</source>
```

Refer to the [Configuration File](https://docs.fluentd.org/configuration/config-file) article for the basic structure and syntax of the configuration file.

## Parameters

### `@type` (required)

The value must be `unix`.

### `path`

|  type  |                  default                  | version |
| :----: | :---------------------------------------: | :-----: |
| string | `/var/run/fluent/fluent.sock` (see below) |  0.14.0 |

The path to your Unix Domain Socket.

Fluentd will use the environment variable `FLUENT_SOCKET` if defined.

### `backlog`

|   type  | default | version |
| :-----: | :-----: | :-----: |
| integer |   1024  |  0.14.0 |

The backlog of Unix Domain Socket.

### `tag`

| type   | default | version |
| ------ | ------- | ------- |
| string | nil     | 1.11.0  |

`in_unix` uses incoming event's tag by default. If the `tag` parameter is set, its value is used instead.

If this article is incorrect or outdated, or omits critical information, please [let us know](https://github.com/fluent/fluentd-docs-gitbook/issues?state=open). [Fluentd](http://www.fluentd.org/) is an open-source project under [Cloud Native Computing Foundation (CNCF)](https://cncf.io/). All components are available under the Apache 2 License.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fluentd.org/input/unix.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.