Add Fleet/Agent 8.6.0 release notes #2450
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,243 @@ | ||
| // Use these for links to issue and pulls. | ||
| :kibana-issue: https://github.com/elastic/kibana/issues/ | ||
| :kibana-pull: https://github.com/elastic/kibana/pull/ | ||
| :beats-issue: https://github.com/elastic/beats/issues/ | ||
| :beats-pull: https://github.com/elastic/beats/pull/ | ||
| :agent-libs-pull: https://github.com/elastic/elastic-agent-libs/pull/ | ||
| :agent-issue: https://github.com/elastic/elastic-agent/issues/ | ||
| :agent-pull: https://github.com/elastic/elastic-agent/pull/ | ||
| :fleet-server-issue: https://github.com/elastic/fleet-server/issues/ | ||
| :fleet-server-pull: https://github.com/elastic/fleet-server/pull/ | ||
|
|
||
| [[release-notes]] | ||
| = Release notes | ||
|
|
||
| This section summarizes the changes in each release. | ||
|
|
||
| * <<release-notes-8.6.0>> | ||
|
|
||
| Also see: | ||
|
|
||
| * {kibana-ref}/release-notes.html[{kib} release notes] | ||
| * {beats-ref}/release-notes.html[{beats} release notes] | ||
|
|
||
| // begin 8.6.0 relnotes | ||
|
|
||
| [[release-notes-8.6.0]] | ||
| == {fleet} and {agent} 8.6.0 | ||
|
|
||
| Review important information about the {fleet} and {agent} 8.6.0 release. | ||
|
|
||
| [discrete] | ||
| [[breaking-changes-8.6.0]] | ||
| === 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. | ||
|
|
||
| [discrete] | ||
| [[breaking-1994]] | ||
| .Each input in an agent policy must have a unique ID | ||
| [%collapsible] | ||
| ==== | ||
| *Details* + | ||
| Each input in an agent policy must have a unique ID, like `id: my-unique-input-id`. | ||
| This change only affects standalone agents. Unique IDs are automatically generated in | ||
| agent policies managed by {fleet}. For more information, refer to | ||
| {agent-pull}/1994[#1994] | ||
|
|
||
| *Impact* + | ||
| Make sure that your standalone agent policies have a unique ID. | ||
| ==== | ||
|
|
||
| [discrete] | ||
| [[breaking-1140]] | ||
| .Diagnostics `--pprof` argument has been removed and is now always provided | ||
| [%collapsible] | ||
| ==== | ||
| *Details* + | ||
| The `diagnostics` command gathers diagnostic information about the {agent} and | ||
| each component/unit it runs. Starting in 8.6.0, the `--pprof` | ||
| argument is no longer available because `pprof` information is now always | ||
| provided. For more information, refer to {agent-pull}1140[#1140]. | ||
|
|
||
| *Impact* + | ||
| Remove the `--pprof` argument from any scripts or commands you use. | ||
| ==== | ||
|
|
||
| [discrete] | ||
| [[known-issues-8.6.0]] | ||
| === Known issues | ||
|
|
||
| [discrete] | ||
| [[known-issue-issue-2066]] | ||
| .Osquery live query results can take up to five minutes to show up in {kib} | ||
| [%collapsible] | ||
| ==== | ||
| *Details* + | ||
| A known issue in {agent} may prevent live query results from being available | ||
| in the {kib} UI even though the results have been successfully sent to {es}. | ||
| For more information, refer to {agent-issue}2066[#2066]. | ||
|
|
||
| *Impact* + | ||
| Be aware that the live query results shown in {kib} may be delayed by up to 5 minutes. | ||
| ==== | ||
|
|
||
| [discrete] | ||
| [[new-features-8.6.0]] | ||
| === New features | ||
|
|
||
| The 8.6.0 release adds the following new and notable features. | ||
|
|
||
| {fleet}:: | ||
| * Differentiate kubernetes integration multipage experience {kibana-pull}145224[#145224] | ||
| * Add prerelease toggle to Integrations list {kibana-pull}143853[#143853] | ||
| * Add link to allow users to skip multistep add integration workflow {kibana-pull}143279[#143279] | ||
| * Add new action for single agents to request diagnostics {kibana-pull}142369[#142369] | ||
|
|
||
| {agent}:: | ||
| * Upgrade Node to version 18.12.0 {agent-pull}1657[#1657] | ||
| * Add experimental support for running the elastic-agent-shipper {agent-pull}1527[#1527] {agent-issue}219[#219] | ||
| * Collect logs from sub-processes via stdout and stderr and write them to a single, unified Elastic Agent log file {agent-pull}1702[#1702] {agent-issue}221[#221] | ||
| * Remove inputs when all streams are removed {agent-pull}1869[#1869] {agent-issue}1868[#1868] | ||
| * No longer restart {agent} on log level change {agent-pull}1914[#1914] {agent-issue}1896[#1896] | ||
| * Add `inspect components` command to inspect the computed components/units model of the current configuration (for example, `elastic-agent inspect components`) {agent-pull}1701[#1701] {agent-issue}836[#836] | ||
| * Add support for the Common Expression Language (CEL) {filebeat} input type {agent-pull}1719[#1719] | ||
| * Only support {es} as an output for the beta synthetics integration {agent-pull}1491[#1491] | ||
| * New control protocol between the {agent} and its subprocesses enables per integration health reporting and simplifies new input development {agent-issue}836[#836] {agent-pull}1701[#1701] | ||
|
Contributor
Author
There was a problem hiding this comment. @pierrehilbert I've added the missing changelog items here. However, the change to the internal directory structure does not seem like a "feature" to me. Should it be covered under breaking changes instead?
Contributor
Author
There was a problem hiding this comment. At this point, we should get this content merged and do follow-up PRs if additional changes are required. I just need approval....
Contributor
There was a problem hiding this comment. I wanted to put it into "upgrade" kind but seems to be not working that's why I changed to "feature". But yes "breaking-change" makes probably more sense.
Member
There was a problem hiding this comment. The internal directory structure change shouldn't be a breaking change, in that the user shouldn't need to take any action to account for it. Agent should keep working. It is definitely notable though. |
||
| * Change internal directory structure: add a components directory to contain binaries and associated artifacts, and remove the downloads directory {agent-issue}836[#836] {agent-pull}1701[#1701] | ||
| * All binaries for every supported integration are now bundled in the {agent} by default {agent-issue}836[#836] {agent-pull}126[#126] | ||
|
|
||
| [discrete] | ||
| [[enhancements-8.6.0]] | ||
| === Enhancements | ||
|
|
||
| {fleet}:: | ||
| * Add `?full` option to get package info endpoint to return all package fields {kibana-pull}144343[#144343] | ||
|
|
||
| {agent}:: | ||
| * Health Status: {agent} now indicates detailed status information for each sub-process and input type {fleet-server-pull}1747[#1747] {agent-issue}100[#100] | ||
|
|
||
| [discrete] | ||
| [[bug-fixes-8.6.0]] | ||
| === Bug fixes | ||
|
|
||
| {fleet}:: | ||
| * Only show {fleet}-managed data streams on data streams list page {kibana-pull}143300[#143300] | ||
dedemorton marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| * Fix synchronization bug in {fleet-server} that can lead to {es} being flooded by requests to `/.fleet-actions/_fleet/_fleet_search` {fleet-server-pull}2205[#2205]. | ||
|
|
||
| {agent}:: | ||
| * {agent} now uses the locally bound port (8221) when running {fleet-server} instead of the external port (8220) {agent-pull}1867[#1867] | ||
| * Correctly preserve the {filebeat} registry and other persistent input states during upgrades to eliminate event duplication after upgrades {agent-pull}1701[#1701] {agent-issue}836[#836] | ||
| // end 8.6.0 relnotes | ||
|
|
||
|
|
||
| // --------------------- | ||
| //TEMPLATE | ||
| //Use the following text as a template. Remember to replace the version info. | ||
|
|
||
| // begin 8.6.x relnotes | ||
|
|
||
| //[[release-notes-8.6.x]] | ||
| //== {fleet} and {agent} 8.6.x | ||
|
|
||
| //Review important information about the {fleet} and {agent} 8.6.x release. | ||
|
|
||
| //[discrete] | ||
| //[[security-updates-8.6.x]] | ||
| //=== Security updates | ||
|
|
||
| //{fleet}:: | ||
| //* add info | ||
|
|
||
| //{agent}:: | ||
| //* add info | ||
|
|
||
| //[discrete] | ||
| //[[breaking-changes-8.6.x]] | ||
| //=== 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. | ||
|
|
||
| //[discrete] | ||
| //[[breaking-PR#]] | ||
| //.Short description | ||
| //[%collapsible] | ||
| //==== | ||
| //*Details* + | ||
| //<Describe new behavior.> For more information, refer to {kibana-pull}PR[#PR]. | ||
|
|
||
| //*Impact* + | ||
| //<Describe how users should mitigate the change.> For more information, refer to {fleet-guide}/fleet-server.html[Fleet Server]. | ||
| //==== | ||
|
|
||
| //[discrete] | ||
| //[[known-issues-8.6.x]] | ||
| //=== Known issues | ||
|
|
||
| //[[known-issue-issue#]] | ||
| //.Short description | ||
| //[%collapsible] | ||
| //==== | ||
|
|
||
| //*Details* | ||
|
|
||
| //<Describe known issue.> | ||
|
|
||
| //*Impact* + | ||
|
|
||
| //<Describe impact or workaround.> | ||
|
|
||
| //==== | ||
|
|
||
| //[discrete] | ||
| //[[deprecations-8.6.x]] | ||
| //=== Deprecations | ||
|
|
||
| //The following functionality is deprecated in 8.6.x, and will be removed in | ||
| //8.6.x. Deprecated functionality does not have an immediate impact on your | ||
| //application, but we strongly recommend you make the necessary updates after you | ||
| //upgrade to 8.6.x. | ||
|
|
||
| //{fleet}:: | ||
| //* add info | ||
|
|
||
| //{agent}:: | ||
| //* add info | ||
|
|
||
| //[discrete] | ||
| //[[new-features-8.6.x]] | ||
| //=== New features | ||
|
|
||
| //The 8.6.x release adds the following new and notable features. | ||
|
|
||
| //{fleet}:: | ||
| //* add info | ||
|
|
||
| //{agent}:: | ||
| //* add info | ||
|
|
||
| //[discrete] | ||
| //[[enhancements-8.6.x]] | ||
| //=== Enhancements | ||
|
|
||
| //{fleet}:: | ||
| //* add info | ||
|
|
||
| //{agent}:: | ||
| //* add info | ||
|
|
||
| //[discrete] | ||
| //[[bug-fixes-8.6.x]] | ||
| //=== Bug fixes | ||
|
|
||
| //{fleet}:: | ||
| //* add info | ||
|
|
||
| //{agent}:: | ||
| //* add info | ||
|
|
||
| // end 8.6.x relnotes | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.