> For the complete documentation index, see [llms.txt](https://docs.fluentbit.io/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fluentbit.io/manual/1.0/input.md).

# Input Plugins

The *input plugins* defines the source from where [Fluent Bit](http://fluentbit.io) can collect data, it can be through a network interface, radio hardware or some built-in metric. As of this version the following input plugins are available:

| name                                    | title             | description                                            |
| --------------------------------------- | ----------------- | ------------------------------------------------------ |
| [cpu](/manual/1.0/input/cpu.md)         | CPU Usage         | measure total CPU usage of the system.                 |
| [disk](/manual/1.0/input/disk.md)       | Disk Usage        | measure Disk I/Os.                                     |
| [dummy](/manual/1.0/input/dummy.md)     | Dummy             | generate dummy event.                                  |
| [exec](/manual/1.0/input/exec.md)       | Exec              | executes external program and collects event logs.     |
| [forward](/manual/1.0/input/forward.md) | Forward           | Fluentd forward protocol.                              |
| [head](/manual/1.0/input/head.md)       | Head              | read first part of files.                              |
| [health](/manual/1.0/input/health.md)   | Health            | Check health of TCP services.                          |
| [kmsg](/manual/1.0/input/kmsg.md)       | Kernel Log Buffer | read the Linux Kernel log buffer messages.             |
| [mem](/manual/1.0/input/mem.md)         | Memory Usage      | measure the total amount of memory used on the system. |
| [mqtt](/manual/1.0/input/mqtt.md)       | MQTT              | start a MQTT server and receive publish messages.      |
| [netif](/manual/1.0/input/netif.md)     | Network Traffic   | measure network traffic.                               |
| [proc](/manual/1.0/input/proc.md)       | Process           | Check health of Process.                               |
| [random](/manual/1.0/input/random.md)   | Random            | Generate Random samples.                               |
| [serial](/manual/1.0/input/serial.md)   | Serial Interface  | read data information from the serial interface.       |
| [stdin](/manual/1.0/input/stdin.md)     | Standard Input    | read data from the standard input.                     |
| [syslog](/manual/1.0/input/syslog.md)   | Syslog            | read syslog messages from a Unix socket.               |
| [systemd](/manual/1.0/input/systemd.md) | Systemd           | read logs from Systemd/Journald.                       |
| [tail](/manual/1.0/input/tail.md)       | Tail              | Tail log files                                         |
| [tcp](/manual/1.0/input/tcp.md)         | TCP               | Listen for JSON messages over TCP.                     |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fluentbit.io/manual/1.0/input.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.