- Fleet and Elastic Agent Guide: other versions:
- Fleet and Elastic Agent overview
- Beats and Elastic Agent capabilities
- Quick start: Get logs, metrics, and uptime data into the Elastic Stack
- Quick start: Get application traces into the Elastic Stack
- Integrations
- Elastic Agents
- Install Elastic Agents
- Uninstall Elastic Agent
- Run Elastic Agent standalone (advanced users)
- Run Elastic Agent in a container
- Run Elastic Agent on Kubernetes managed by Fleet
- Run Elastic Agent standalone on Kubernetes
- Upgrade Elastic Agent
- Start Elastic Agent
- Stop Elastic Agent
- Unenroll Elastic Agent
- View status of Elastic Agents
- Variables and conditions in input configurations
- Environment variables
- Configure logging for Fleet-managed Elastic Agents
- Policies
- Elastic Agent standalone configuration
- Fleet UI settings
- Fleet Server
- Fleet enrollment tokens
- Encrypt traffic in clusters with a self-managed Fleet Server
- Data streams
- Command reference
- Troubleshoot common problems
- Frequently asked questions
- Release notes
- Fleet APIs
IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Configure inputs for standalone Elastic Agents
editConfigure inputs for standalone Elastic Agents
editRunning Elastic Agent in standalone mode is an advanced use case. The documentation is incomplete and not yet mature. When possible, we recommend using Fleet-managed agents instead of standalone mode.
The inputs
section of the elastic-agent.yml
file specifies how Elastic Agent
locates and processes input data.
By default Elastic Agent collects system metrics, such as cpu, memory, network, and filesystem metrics, and sends them to the default output. For example:
inputs: - type: system/metrics data_stream.namespace: default use_output: default streams: - metricset: cpu data_stream.dataset: system.cpu - metricset: memory data_stream.dataset: system.memory - metricset: network data_stream.dataset: system.network - metricset: filesystem data_stream.dataset: system.filesystem
If use_output
is not specified, the default
output is used.
Was this helpful?
Thank you for your feedback.