input-configuration.asciidoc

Configure inputs for standalone {agent}s

Inputs

The inputs section of the elastic-agent.yml file specifies how {agent} locates and processes input data.

• Sample metrics input configuration

• Sample log files input configuration

Sample metrics input configuration

By default {agent} collects system metrics, such as CPU, memory, network, and file system metrics, and sends them to the default output. For example, to define datastreams for cpu, memory, network and filesystem metrics, this is the configuration:

- type: system/metrics (1)
  id: unique-system-metrics-id (2)
  data_stream.namespace: default (3)
  use_output: default (4)
  streams:
    - metricsets: (5)
      - cpu
      data_stream.dataset: system.cpu (6)
    - metricsets:
      - memory
      data_stream.dataset: system.memory
    - metricsets:
      - network
      data_stream.dataset: system.network
    - metricsets:
      - filesystem
      data_stream.dataset: system.filesystem

1. The name of the input. Refer to [elastic-agent-inputs-list] for the list of what’s available.

2. A unique ID for the input.

3. A user-defined namespace.

4. The name of the output to use. If not specified, default will be used.

5. The set of enabled module metricsets.

   Refer to the {metricbeat} {metricbeat-ref}/metricbeat-module-system.html[System module] for a list of available options. The metricset fields can be configured.

6. A user-defined dataset. It can contain anything that makes sense to signify the source of the data.

Sample log files input configuration

To enable {agent} to collect log files, you can use a configuration like the following.

- type: filestream (1)
  id: your-input-id (2)
  streams:
    - id: your-filestream-stream-id (3)
      data_stream: (4)
        dataset: generic
      paths:
        - /var/log/*.log

1. The name of the input. Refer to [elastic-agent-inputs-list] for the list of what’s available.

2. A unique ID for the input.

3. A unique ID for the data stream to track the state of the ingested files.

4. The streams block is required only if multiple streams are used on the same input. Refer to the {filebeat} {filebeat-ref}/filebeat-input-filestream.html[filestream] documentation for a list of available options. Also, specifically for the filestream input type, refer to the simplified log ingestion for an example of ingesting a set of logs specified as an array.

The input in this example harvests all files in the path /var/log/*.log, that is, all logs in the directory /var/log/ that end with .log. All patterns supported by Go Glob are also supported here.

To fetch all files from a predefined level of subdirectories, use this pattern: /var/log//.log. This fetches all .log files from the subfolders of /var/log. It does not fetch log files from the /var/log folder itself. Currently it is not possible to recursively fetch all files in all subdirectories of a directory.