- Fleet and Elastic Agent Guide: other versions:
- Fleet and Elastic Agent overview
- Beats and Elastic Agent capabilities
- Quick starts
- Migrate from Beats to Elastic Agent
- Set up Fleet Server
- Install Elastic Agents
- Secure connections
- Manage Elastic Agents in Fleet
- Manage integrations
- Add an Elastic Agent integration to a policy
- View Elastic Agent integration policies
- Edit or delete an Elastic Agent integration policy
- Install and uninstall Elastic Agent integration assets
- View Elastic Agent integration assets
- Upgrade an Elastic Agent integration
- Uninstall an Elastic Agent integration
- Air-gapped environments
- Configure standalone Elastic Agents
- Command reference
- Troubleshoot
- Release notes
IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Configure outputs for standalone Elastic Agents
editConfigure outputs 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 outputs
section of the elastic-agent.yml
file specifies where to
send data. You can specify multiple outputs to pair specific inputs with
specific outputs.
This example configures two outputs: default
and monitoring
:
outputs: default: type: elasticsearch hosts: [127.0.0.1:9200] username: elastic password: changeme monitoring: type: elasticsearch api_key: VuaCfGcBCdbkQm-e5aOx:ui2lp2axTNmsyakw9tvNnw hosts: ["localhost:9200"] ca_sha256: "7lHLiyp4J8m9kw38SJ7SURJP4bXRZv/BNxyyXkCcE/M="
Notice that they use different authentication methods. The first one uses a username and password pair, and the second one contains an API key.
A default output configuration is required.
Elastic Agent currently supports these outputs:
- Elasticsearch
- Logstash (standalone mode only)
Was this helpful?
Thank you for your feedback.