# Docker Events

The **docker events** input plugin uses the docker API to capture server events. A complete list of possible events returned by this plugin can be found [here](https://docs.docker.com/engine/reference/commandline/events/)

## Configuration Parameters

This plugin supports the following configuration parameters:

| Key          | Description                                                                                                 | Default              |
| ------------ | ----------------------------------------------------------------------------------------------------------- | -------------------- |
| Unix\_Path   | The docker socket unix path                                                                                 | /var/run/docker.sock |
| Buffer\_Size | The size of the buffer used to read docker events (in bytes)                                                | 8192                 |
| Parser       | Specify the name of a parser to interpret the entry as a structured message.                                | None                 |
| Key          | When a message is unstructured (no parser applied), it's appended as a string under the key name *message*. | message              |

### Command Line

```bash
$ fluent-bit -i docker_events -o stdout
```

### Configuration File

In your main configuration file append the following **Input** & **Output** sections:

```yaml
[INPUT]
    Name   docker_events

[OUTPUT]
    Name   stdout
    Match  *
```


---

# 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.fluentbit.io/manual/1.5/pipeline/inputs/docker-events.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.