- 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
- Deployment models
- Install Elastic Agents
- Install Fleet-managed Elastic Agents
- Install standalone Elastic Agents (advanced users)
- Install Elastic Agents in a containerized environment
- Run Elastic Agent in a container
- Run Elastic Agent on Kubernetes managed by Fleet
- Run Elastic Agent on GKE managed by Fleet
- Run Elastic Agent on Amazon EKS managed by Fleet
- Run Elastic Agent on Azure AKS managed by Fleet
- Run Elastic Agent Standalone on Kubernetes
- Scaling Elastic Agent on Kubernetes
- Using a custom ingest pipeline with the Kubernetes Integration
- Environment variables
- Installation layout
- Air-gapped environments
- Using a proxy server with Elastic Agent and Fleet
- Uninstall Elastic Agents from edge hosts
- Start and stop Elastic Agents on edge hosts
- Elastic Agent configuration encryption
- Secure connections
- Manage Elastic Agents in Fleet
- Configure standalone Elastic Agents
- Create a standalone Elastic Agent policy
- Structure of a config file
- Inputs
- Providers
- Outputs
- SSL/TLS
- Logging
- Feature flags
- Agent download
- Config file examples
- Grant standalone Elastic Agents access to Elasticsearch
- Example: Use standalone Elastic Agent to monitor nginx
- Debug standalone Elastic Agents
- Kubernetes autodiscovery with Elastic Agent
- Monitoring
- Reference YAML
- Manage integrations
- Define processors
- Processor syntax
- add_cloud_metadata
- add_cloudfoundry_metadata
- add_docker_metadata
- add_fields
- add_host_metadata
- add_id
- add_kubernetes_metadata
- add_labels
- add_locale
- add_network_direction
- add_nomad_metadata
- add_observer_metadata
- add_process_metadata
- add_tags
- community_id
- convert
- copy_fields
- decode_base64_field
- decode_cef
- decode_csv_fields
- decode_duration
- decode_json_fields
- decode_xml
- decode_xml_wineventlog
- decompress_gzip_field
- detect_mime_type
- dissect
- dns
- drop_event
- drop_fields
- extract_array
- fingerprint
- include_fields
- move_fields
- parse_aws_vpc_flow_log
- rate_limit
- registered_domain
- rename
- replace
- script
- syslog
- timestamp
- translate_sid
- truncate_fields
- urldecode
- 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.
Installation layout
editInstallation layout
editElastic Agent files are installed in the following locations. You cannot override these installation paths because they are required for upgrades.
-
/Library/Elastic/Agent/* - Elastic Agent program files
-
/Library/Elastic/Agent/elastic-agent.yml - Main Elastic Agent configuration
-
/Library/Elastic/Agent/fleet.enc - Main Elastic Agent Fleet encrypted configuration
-
/Library/Elastic/Agent/data/elastic-agent-*/logs/elastic-agent-json.log - Log files for Elastic Agent[1]
-
/Library/Elastic/Agent/data/elastic-agent-*/logs/default/*-json.log - Log files for Beats shippers[1]
-
/usr/local/bin/elastic-agent - Shell wrapper installed into PATH
-
/opt/Elastic/Agent/* - Elastic Agent program files
-
/opt/Elastic/Agent/elastic-agent.yml - Main Elastic Agent configuration
-
/opt/Elastic/Agent/fleet.enc - Main Elastic Agent Fleet encrypted configuration
-
/opt/Elastic/Agent/data/elastic-agent-*/logs/elastic-agent-json.log - Log files for Elastic Agent[1]
-
/opt/Elastic/Agent/data/elastic-agent-*/logs/default/*-json.log - Log files for Beats shippers
-
/usr/bin/elastic-agent - Shell wrapper installed into PATH
-
C:\Program Files\Elastic\Agent* - Elastic Agent program files
-
C:\Program Files\Elastic\Agent\elastic-agent.yml - Main Elastic Agent configuration
-
C:\Program Files\Elastic\Agent\fleet.enc - Main Elastic Agent Fleet encrypted configuration
-
C:\Program Files\Elastic\Agent\data\elastic-agent-*\logs\elastic-agent-json.log - Log files for Elastic Agent[1]
-
C:\Program Files\Elastic\Agent\data\elastic-agent-*\logs\default\*-json.log* - Log files for Beats shippers
-
/usr/share/elastic-agent/* - Elastic Agent program files
-
/etc/elastic-agent/elastic-agent.yml - Main Elastic Agent configuration
-
/etc/elastic-agent/fleet.enc - Main Elastic Agent Fleet encrypted configuration
-
/var/lib/elastic-agent/data/elastic-agent-*/logs/elastic-agent-json.log - Log files for Elastic Agent[1]
-
/var/lib/elastic-agent/data/elastic-agent-*/logs/default/*-json.log* - Log files for Beats shippers
-
/usr/bin/elastic-agent - Shell wrapper installed into PATH
-
/usr/share/elastic-agent/* - Elastic Agent program files
-
/etc/elastic-agent/elastic-agent.yml - Main Elastic Agent configuration
-
/etc/elastic-agent/fleet.enc - Main Elastic Agent Fleet encrypted configuration
-
/var/lib/elastic-agent/data/elastic-agent-*/logs/elastic-agent-json.log - Log files for Elastic Agent[1]
-
/var/lib/elastic-agent/data/elastic-agent-*/logs/default/*-json.log* - Log files for Beats shippers
-
/usr/bin/elastic-agent - Shell wrapper installed into PATH
[1] Logs file names end with a date and optional number: log-date.ndjson, log-date-1.ndjson, and so on as new files are created during rotation.
Was this helpful?
Thank you for your feedback.