- 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
- Install Elastic Agents in a containerized environment
- Run Elastic Agent in a container
- Run Elastic Agent on Kubernetes managed by Fleet
- Install Elastic Agent on Kubernetes using Helm
- Example: Install standalone Elastic Agent on Kubernetes using Helm
- Example: Install Fleet-managed Elastic Agent on Kubernetes using Helm
- Advanced Elastic Agent configuration managed by Fleet
- Configuring Kubernetes metadata enrichment on Elastic Agent
- 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
- Run Elastic Agent as an OTel Collector
- Run Elastic Agent without administrative privileges
- Install Elastic Agent from an MSI package
- 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 with Elastic Cloud Serverless to monitor nginx
- Example: Use standalone Elastic Agent with Elasticsearch Service to monitor nginx
- Debug standalone Elastic Agents
- Kubernetes autodiscovery with Elastic Agent
- Monitoring
- Reference YAML
- Manage integrations
- Package signatures
- Add an integration to an Elastic Agent policy
- View integration policies
- Edit or delete an integration policy
- Install and uninstall integration assets
- View integration assets
- Set integration-level outputs
- Upgrade an integration
- Managed integrations content
- Best practices for integration assets
- Data streams
- 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.
Fleet and Elastic Agent 8.17.4
edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.
Fleet and Elastic Agent 8.17.4
editReview important information about the 8.17.4 release.
Known issues
editInaccurate option to upgrade across major releases appears in Fleet UI
Details
In late 8.x releases, there’s a bug in the Fleet UI that causes 9.0.0 to appear as an option for Elastic Agent upgrades. This option results in an error when selected, as upgrades across major releases are not supported for Elastic Agent. For example, an agent can’t be upgraded to version 9.0 while Kibana and Fleet Server are on version 8.x.
The Elastic Agent upgrade is not selectable:
The Fleet Server upgrade is selectable, with an inconsistent UI state and error on submit:
Impact
In the 9.x releases, the option that appears in the UI for an upgrade across a major release should be ignored.
New features
editThe 8.17.4 release adds the following new and notable features.
- Elastic Agent
-
- Add managed OTLP endpoint sample configurations. #6630
Enhancements
edit- Elastic Agent
Bug fixes
edit- Elastic Agent
-
-
Add conditions to the
copy_fieldsprocessors used with Elastic Agent self-monitoring to prevent spamming the debug logs. #6730 #5299 - Improve message when Fleet Server’s audit API endpoint returns a 401 Unauthorized response. #6735 #6711
-
Fix
secret_pathsredaction along complex paths in diagnostics. #6710 -
Make enroll command backoff more conservative and add backoff when using
--delay-enroll. #6983 #6761 -
Fix an issue where
fixpermissionson Windows incorrectly returned an error message due to improper handling of Windows API return values. #7059 #6917 - Support IPv6 hosts in enroll URL. #7036
- Support IPv6 hosts in GRPC configuration. #7035
- Rotate logger output file when writing to a symbolic link. #6938
- Do not fail Windows permission updates on missing files or paths. #7305 #7301
-
Make
otelcolscript executable in the Docker image. #7345 -
Fix Elasticsearch exporter configuration in
kube-stackvalues. #7380
-
Add conditions to the
On this page
Was this helpful?
Thank you for your feedback.