Skip to content

Latest commit

 

History

History
350 lines (257 loc) · 10 KB

release-notes-8.4.asciidoc

File metadata and controls

350 lines (257 loc) · 10 KB

Release notes

This section summarizes the changes in each release.

Also see:

  • {kibana-ref}/release-notes.html[{kib} release notes]

  • {beats-ref}/release-notes.html[{beats} release notes]

{fleet} and {agent} 8.4.3

Review important information about the {fleet} and {agent} 8.4.3 release.

Bug fixes

{fleet}

  • {fleet-server} no longer silently discards user-specified values for cache and server limits when defaults are loaded #1841 #1912

{agent}

  • Use at least warning level for all status logs #1218

  • Fix unintended reset of source URI when downloading components #1252

  • Create separate status reporter for local only events so that degraded {fleet} checkins no longer affect health on successful {fleet} checkins #1157 #1285

  • Add success log message after previous checkin failures #1327

  • Fix Unix socket connection errors when using diagnostics command #2201

Enhancements

{fleet}

  • No enhancements for this release

{agent}

  • Improve logging during upgrades #1287

{fleet} and {agent} 8.4.2

Review important information about the {fleet} and {agent} 8.4.2 release.

Bug fixes

{fleet}

  • Apply fixes for package policy upgrade API with multiple ids #140069

  • Improve performance for many integration policies #139648

{agent}

  • No bug fixes for this release

{fleet} and {agent} 8.4.1

Review important information about the {fleet} and {agent} 8.4.1 release.

Known issues

Credentials error prevents {agent} from ingesting AWS logs

Details

{agent}s configured to use the AWS integration may return an error similar to the following:

sqs ReceiveMessage failed: operation error SQS: ReceiveMessage, https response
error StatusCode: 403, RequestID: cb57783a-505f-5099-9160-23b8eea8ddbb,
api error SignatureDoesNotMatch: Credential should be scoped to a valid region.

This error was introduced by a breaking change in the AWS library.

Impact

{agent} is unable to ingest AWS logs and some metrics. To resolve this error:

  • If you are using the default domain amazonaws.com, upgrade the AWS integration package to version 1.23.4 to apply the temporary fix added in PR #4103. If this does not solve your problem, set the AWS region (either from an environment variable, credentials or instance profile) where {agent} is running.

  • Otherwise, wait to upgrade until the permanent fix added by PR #32921 is available in an upcoming stack release.

Bug fixes

There are no bug fixes for {fleet} or {agent} in this release.

{fleet} and {agent} 8.4.0

Review important information about the {fleet} and {agent} 8.4.0 release.

Breaking changes

Breaking changes can prevent your application from optimal operation and performance. Before you upgrade, review the breaking changes, then mitigate the impact to your application.

xpack.agents.* are uneditable in UI when defined in kibana.yml

Details
When you configure setxpack.fleet.agents.fleet_server.hosts and xpack.fleet.agents.elasticsearch.hosts in kibana.yml, you are unable to update the fields on the Fleet UI. For more information, refer to #135669.

Impact
To configure setxpack.fleet.agents.fleet_server.hosts and xpack.fleet.agents.elasticsearch.hosts on the Fleet UI, avoid configuring the settings in kibana.yml.

Known issues

New features

The 8.4.0 release adds the following new and notable features.

{fleet}

  • Allow user to force install an unverified package #136108

  • Add tag rename and delete feature #135712

  • Add UI to bulk update agent tags #135646

  • Add API to bulk update agent tags #135520

  • Add UI to add and remove agent tags #135320

  • Support sorting agent list #135218

  • Promote Logstash output support to GA #135028

  • Create new API to manage download_source setting for agent binary downloads #134889

{agent}

  • Add @metadata.input_id and @metadata.stream_id when applying the inject stream processor #527

  • Improve {agent} status reporting: add a liveness endpoint, allow the fleet-gateway component to report degraded state, and add the status update time and messages to the status output #390 #569

  • Redact sensitive information collected by the elastic-agent diagnostics collect command #241 #566

Enhancements

{fleet}

  • Remove Kubernetes package granularity #136622

  • Align {agent} manifests with the elastic-agent repo and add comments #136394

  • Configure source URI in global settings and in agent policy settings #136263

  • Add Kubernetes in platforms selection list and update managed agent installation steps #136109

  • Enable user to write custom ingest pipelines for {fleet}-installed datastreams #134578

  • Update manifests for agent on Kubernetes with new permissions #133495

  • Add support for a textarea type in integrations #133070

{agent}

There are no enhancements beyond the new features added in this release

Bug fixes

{fleet}

  • Use point in time for agent status query to provide accurate reporting #135816

{agent}

  • Change default value of VerificationMode from empty string to full #184 #59

  • Add filemod times to contents of diagnostics collect command #570

  • Allow colon (:) characters in dynamic variables #624 #680

  • Allow dash (-) characters in variable names in EQL expressions #709 #710

  • Allow slash (/) characters in variable names in EQL and transpiler #715 #718

  • Fix problem with {agent} incorrectly creating a {filebeat} redis input when a policy contains a {packetbeat} redis input #427 #700

  • Fix data duplication for standalone {agent} on Kubernetes using the default manifest #31512 #742

  • {agent} upgrades now clean up unneeded artifacts #693 #694 #752

  • Fix a panic caused by a race condition when installing the {agent} #806 #823