From 198f5af89083bc784c3305e36ea1efc3b30afd5b Mon Sep 17 00:00:00 2001 From: Lisa Cawley Date: Mon, 3 Feb 2025 14:24:40 -0800 Subject: [PATCH 01/14] Revert "github-action: Add AsciiDoc freeze warning (#2910)" (#2945) This reverts commit 1acc08da4044b1849db71467faffbb3c2316e3bc. --- .../workflows/comment-on-asciidoc-changes.yml | 21 ------------------- 1 file changed, 21 deletions(-) delete mode 100644 .github/workflows/comment-on-asciidoc-changes.yml diff --git a/.github/workflows/comment-on-asciidoc-changes.yml b/.github/workflows/comment-on-asciidoc-changes.yml deleted file mode 100644 index 8e5f836b1..000000000 --- a/.github/workflows/comment-on-asciidoc-changes.yml +++ /dev/null @@ -1,21 +0,0 @@ ---- -name: Comment on PR for .asciidoc changes - -on: - # We need to use pull_request_target to be able to comment on PRs from forks - pull_request_target: - types: - - synchronize - - opened - - reopened - branches: - - main - - master - - "9.0" - -jobs: - comment-on-asciidoc-change: - permissions: - contents: read - pull-requests: write - uses: elastic/docs-builder/.github/workflows/comment-on-asciidoc-changes.yml@main From 3cb7af904f7452b32ecf681d1ab42d7c44e3190b Mon Sep 17 00:00:00 2001 From: Lisa Cawley Date: Mon, 3 Feb 2025 17:07:27 -0800 Subject: [PATCH 02/14] Add serverless changelog (#2943) --- docs/en/install-upgrade/index.asciidoc | 11 +- .../serverless-changelog.asciidoc | 322 ++++++++++++++++++ 2 files changed, 324 insertions(+), 9 deletions(-) create mode 100644 docs/en/install-upgrade/serverless-changelog.asciidoc diff --git a/docs/en/install-upgrade/index.asciidoc b/docs/en/install-upgrade/index.asciidoc index 962c0f702..298950e73 100644 --- a/docs/en/install-upgrade/index.asciidoc +++ b/docs/en/install-upgrade/index.asciidoc @@ -1,15 +1,6 @@ [[elastic-stack]] = Elastic Installation and Upgrade Guide -:apm-repo-dir: {apm-server-root}/docs -:beats-repo-dir: {beats-root}/libbeat/docs -:es-repo-dir: {elasticsearch-root}/docs/reference -:hadoop-repo-dir: {elasticsearch-hadoop-root}/docs/src/reference/asciidoc -:security-repo-dir: {security-docs-root}/docs -:kib-repo-dir: {kibana-root}/docs -:ls-repo-dir: {logstash-root}/docs -:obs-repo-dir: {observability-docs-root}/docs/en/observability - include::{docs-root}/shared/versions/stack/{source_branch}.asciidoc[] include::{docs-root}/shared/attributes.asciidoc[] @@ -43,4 +34,6 @@ include::upgrading-kibana.asciidoc[] include::breaking.asciidoc[] +include::serverless-changelog.asciidoc[] + include::redirects.asciidoc[] diff --git a/docs/en/install-upgrade/serverless-changelog.asciidoc b/docs/en/install-upgrade/serverless-changelog.asciidoc new file mode 100644 index 000000000..23c40bb45 --- /dev/null +++ b/docs/en/install-upgrade/serverless-changelog.asciidoc @@ -0,0 +1,322 @@ +[[serverless-changelog]] +== Elastic Cloud Serverless changelog +++++ +Serverless changelog +++++ + +Review the latest improvements and changes to Elastic Cloud Serverless. + +For serverless API changes, refer to https://www.elastic.co/docs/api/changes[APIs Changelog]. + +For serverless changes in Cloud Console, refer to https://www.elastic.co/guide/en/cloud/current/ec-release-notes.html[Elasticsearch Service Documentation: Release notes]. + +[discrete] +[[serverless-changelog-02032025]] +=== February 3, 2025 + +[discrete] +[[deprecations-02032025]] +==== Deprecation + +* Rename plugin to automatic import ({kibana-pull}207325[#207325]). + +[discrete] +[[features-02032025]] +==== Features and enhancements + +* Rework saved query privileges ({kibana-pull}202863[#202863]). +* In-table search ({kibana-pull}206454[#206454]). +* Refactor RowHeightSettings component to EUI layout ({kibana-pull}203606[#203606]). +* Chat history details in conversation list ({kibana-pull}207426[#207426]). +* Cases assignees sub feature ({kibana-pull}201654[#201654]). +* Adds preview logged requests for new terms, threshold, query, ML rule types ({kibana-pull}203320[#203320]). +* Adds in-text citations to security solution AI assistant responses ({kibana-pull}206683[#206683]). +* Remove Tech preview badge for GA ({kibana-pull}208523[#208523]). +* Adds new View job detail flyouts for Anomaly detection and Data Frame Analytics ({kibana-pull}207141[#207141]). +* Rule gaps ({kibana-pull}206313[#206313]). +* Adds a default "All logs" temporary data view in the Observability Solution view ({kibana-pull}205991[#205991]). +* Adds Knowledge Base entries API ({kibana-pull}206407[#206407]). +* Adds Kibana Support for Security AI Prompts Integration ({kibana-pull}207138[#207138]). +* Changes to support event.ingested as a configurable timestamp field for init and enable endpoints ({kibana-pull}208201[#208201]). +* Adds Spaces column to Anomaly Detection, Data Frame Analytics and Trained Models management pages ({kibana-pull}206696[#206696]). +* Adds simple flyout based file upload to Search ({kibana-pull}206864[#206864]). +* Bump kube-stack Helm chart onboarding version ({kibana-pull}208217[#208217]). +* Log deprecated api usages ({kibana-pull}207904[#207904]). +* Added support for human readable name attribute for saved objects audit events ({kibana-pull}206644[#206644]). +* Enhanced Role management to manage larger number of roles by adding server side filtering, pagination and querying ({kibana-pull}194630[#194630]). +* Added Entity Store data view refresh task ({kibana-pull}208543[#208543]). +* Increase maximum Osquery timeout to 24 hours ({kibana-pull}207276[#207276]). + +[discrete] +[[fixes-02032025]] +==== Fixes + +* Remove use of `fr` unit ({kibana-pull}208437[#208437]). +* Fixes load more request size ({kibana-pull}207901[#207901]). +* Persist `runPastTimeout` setting ({kibana-pull}208611[#208611]). +* Allow panel to extend past viewport on resize ({kibana-pull}208828[#208828]). +* Knowledge base install updates ({kibana-pull}208250[#208250]). +* Fixes conversations test in MKI ({kibana-pull}208649[#208649]). +* Fixes ping heatmap regression when Inspect flag is turned off !! ({kibana-pull}208726[#208726]). +* Fixes monitor status rule for empty kql query results !! ({kibana-pull}208922[#208922]). +* Fixes multiple flyouts ({kibana-pull}209158[#209158]). +* Adds missing fields to input manifest templates ({kibana-pull}208768[#208768]). +* "Select a Connector" popup does not show up after the user selects any connector and then cancels it from Endpoint Insights ({kibana-pull}208969[#208969]). +* Logs shard failures for eql event queries on rule details page and in event log ({kibana-pull}207396[#207396]). +* Adds filter to entity definitions schema ({kibana-pull}208588[#208588]). +* Fixes missing ecs mappings ({kibana-pull}209057[#209057]). +* Apply the timerange to the fields fetch in the editor ({kibana-pull}208490[#208490]). +* Update java.ts - removing serverless link ({kibana-pull}204571[#204571]). + +[discrete] +[[serverless-changelog-01272025]] +=== January 27, 2025 + +[discrete] +[[deprecations-01272025]] +==== Deprecation +* Deprecates a subset of Elastic Security Serverless endpoint management APIs ({kibana-pull}206903[#206903]). + +[discrete] +[[features-enhancements-01272025]] +==== Features and enhancements +* Breaks out timeline and note privileges in Elastic Security Serverless ({kibana-pull}201780[#201780]). +* Adds service enrichment to the detection engine in Elastic Security Serverless ({kibana-pull}206582[#206582]). +* Updates the Entity Store Dashboard to prompt for the Service Entity Type in Elastic Security Serverless ({kibana-pull}207336[#207336]). +* Adds `enrichPolicyExecutionInterval` to entity enablement and initialization APIs in Elastic Security Serverless ({kibana-pull}207374[#207374]). +* Introduces a lookback period configuration for the Entity Store in Elastic Security Serverless ({kibana-pull}206421[#206421]). +* Allows pre-configured connectors to opt into exposing their configurations by setting `exposeConfig` in Alerting ({kibana-pull}207654[#207654]). +* Adds selector syntax support to log source profiles in Elastic Observability Serverless ({kibana-pull}206937[#206937]). +* Displays stack traces in the logs overview tab in Elastic Observability Serverless ({kibana-pull}204521[#204521]). +* Enables the use of the rule form to create rules in Elastic Observability Serverless ({kibana-pull}206774[#206774]). +* Checks only read privileges of existing indices during rule execution in Elastic Security Serverless ({kibana-pull}177658[#177658]). +* Updates KNN search and query template autocompletion in Elasticsearch Serverless ({kibana-pull}207187[#207187]). +* Updates JSON schemas for code editors in Machine Learning ({kibana-pull}207706[#207706]). +* Reindexes the `.kibana_security_session_1` index to the 8.x format in Security ({kibana-pull}204097[#204097]). + +[discrete] +[[fixes-01272025]] +==== Fixes +* Fixes editing alerts filters for multi-consumer rule types in Alerting ({kibana-pull}206848[#206848]). +* Resolves an issue where Chrome was no longer hidden for reports in Dashboards and Visualizations ({kibana-pull}206988[#206988]). +* Updates library transforms and duplicate functionality in Dashboards and Visualizations ({kibana-pull}206140[#206140]). +* Fixes an issue where drag previews are now absolutely positioned in Dashboards and Visualizations ({kibana-pull}208247[#208247]). +* Fixes an issue where an accessible label now appears on the range slider in Dashboards and Visualizations ({kibana-pull}205308[#205308]). +* Fixes a dropdown label sync issue when sorting by "Type" ({kibana-pull}206424[#206424]). +* Fixes an access bug related to user instructions in Elastic Observability Serverless ({kibana-pull}207069[#207069]). +* Fixes the Open Explore in Discover link to open in a new tab in Elastic Observability Serverless ({kibana-pull}207346[#207346]). +* Returns an empty object for tool arguments when none are provided in Elastic Observability Serverless ({kibana-pull}207943[#207943]). +* Ensures similar cases count is not fetched without the proper license in Elastic Security Serverless ({kibana-pull}207220[#207220]). +* Fixes table leading actions to use standardized colors in Elastic Security Serverless ({kibana-pull}207743[#207743]). +* Adds missing fields to the AWS S3 manifest in Elastic Security Serverless ({kibana-pull}208080[#208080]). +* Prevents redundant requests when loading Discover sessions and toggling chart visibility in ES|QL ({kibana-pull}206699[#206699]). +* Fixes a UI error when agents move to an orphaned state in Fleet ({kibana-pull}207746[#207746]). +* Restricts non-local Elasticsearch output types for agentless integrations and policies in Fleet ({kibana-pull}207296[#207296]). +* Fixes table responsiveness in the Notifications feature of Machine Learning ({kibana-pull}206956[#206956]). + +[discrete] +[[serverless-changelog-01132025]] +=== January 13, 2025 + +[discrete] +[[deprecations-01132025]] +==== Deprecations +* Remove all legacy risk engine code and features ({kibana-pull}201810[#201810]). + +[discrete] +[[features-enhancements-01132025]] +==== Features and enhancements +* Adds last alert status change to Elastic Security Serverless flyout ({kibana-pull}205224[#205224]). +* Case templates are now GA ({kibana-pull}205940[#205940]). +* Adds format to JSON messages in Elastic Observability Serverless Logs profile ({kibana-pull}205666[#205666]). +* Adds inference connector in Elastic Security Serverless AI features ({kibana-pull}204505[#204505]). +* Adds inference connector for Auto Import in Elastic Security Serverless ({kibana-pull}206111[#206111]). +* Adds Feature Flag Support for Cloud Security Posture Plugin in Elastic Security Serverless ({kibana-pull}205438[#205438]). +* Adds the ability to sync Machine Learning saved objects to all spaces ({kibana-pull}202175[#202175]). +* Improves messages for recovered alerts in Machine Learning Transforms ({kibana-pull}205721[#205721]). + +[discrete] +[[fixes-01132025]] +==== Fixes +* Fixes an issue where "KEEP" columns are not applied after an Elasticsearch error in Discover ({kibana-pull}205833[#205833]). +* Resolves padding issues in the document comparison table in Discover ({kibana-pull}205984[#205984]). +* Fixes a bug affecting bulk imports for the knowledge base in Elastic Observability Serverless ({kibana-pull}205075[#205075]). +* Enhances the Find API by adding cursor-based pagination (search_after) as an alternative to offset-based pagination ({kibana-pull}203712[#203712]). +* Updates Elastic Observability Serverless to use architecture-specific Elser models ({kibana-pull}205851[#205851]). +* Fixes dynamic batching in the timeline for Elastic Security Serverless ({kibana-pull}204034[#204034]). +* Resolves a race condition bug in Elastic Security Serverless related to OpenAI errors ({kibana-pull}205665[#205665]). +* Improves the integration display by ensuring all policies are listed in Elastic Security Serverless ({kibana-pull}205103[#205103]). +* Renames color variables in the user interface for better clarity and consistency ({kibana-pull}204908[#204908]). +* Allows editor suggestions to remain visible when the inline documentation flyout is open in ES|QL ({kibana-pull}206064[#206064]). +* Ensures the same time range is applied to documents and the histogram in ES|QL ({kibana-pull}204694[#204694]). +* Fixes validation for the "required" field in multi-text input fields in Fleet ({kibana-pull}205768[#205768]). +* Fixes timeout issues for bulk actions in Fleet ({kibana-pull}205735[#205735]). +* Handles invalid RRule parameters to prevent infinite loops in alerts ({kibana-pull}205650[#205650]). +* Fixes privileges display for features and sub-features requiring "All Spaces" permissions in Fleet ({kibana-pull}204402[#204402]). +* Prevents password managers from modifying disabled input fields ({kibana-pull}204269[#204269]). +* Updates the listing control in the user interface ({kibana-pull}205914[#205914]). +* Improves consistency in the help dropdown design ({kibana-pull}206280[#206280]). + +[discrete] +[[serverless-changelog-01062025]] +=== January 6, 2025 + +[discrete] +[[deprecations-01062025]] +==== Deprecations +* Disables Elastic Observability Serverless log stream and settings pages ({kibana-pull}203996[#203996]). +* Removes Logs Explorer in Elastic Observability Serverless ({kibana-pull}203685[#203685]). + +[discrete] +[[features-enhancements-01062025]] +==== Features and enhancements +* Introduces case observables in Elastic Security Serverless ({kibana-pull}190237[#190237]). +* Adds a JSON field called "additional fields" to ServiceNow cases when sent using connector, containing the internal names of the ServiceNow table columns ({kibana-pull}201948[#201948]). +* Adds the ability to configure the appearance color mode to sync dark mode with the system value ({kibana-pull}203406[#203406]). +* Makes the "Copy" action visible on cell hover in Discover ({kibana-pull}204744[#204744]). +* Updates the `EnablementModalCallout` name to `AdditionalChargesMessage` in Elastic Security Serverless ({kibana-pull}203061[#203061]). +* Adds more control over which Elastic Security Serverless alerts in Attack Discovery are included as context to the large language model ({kibana-pull}205070[#205070]). +* Adds a consistent layout and other UI enhancements for {ml} pages ({kibana-pull}203813[#203813]). + +[discrete] +[[fixes-01062025]] +==== Fixes +* Fixes an issue that caused dashboards to lag when dragging the time slider ({kibana-pull}201885[#201885]). +* Updates the CloudFormation template to the latest version and adjusts the documentation to reflect the use of a single Firehose stream created by the new template ({kibana-pull}204185[#204185]). +* Fixes Integration and Datastream name validation in Elastic Security Serverless ({kibana-pull}204943[#204943]). +* Fixes an issue in the Automatic Import process where there is now inclusion of the `@timestamp` field in ECS field mappings whenever possible ({kibana-pull}204931[#204931]). +* Allows Automatic Import to safely parse Painless field names that are not valid Painless identifiers in `if` contexts ({kibana-pull}205220[#205220]). +* Aligns the Box Native Connector configuration fields with the source of truth in the connectors codebase, correcting mismatches and removing unused configurations ({kibana-pull}203241[#203241]). +* Fixes the "Show all agent tags" option in Fleet when the agent list is filtered ({kibana-pull}205163[#205163]). +* Updates the Results Explorer flyout footer buttons alignment in Data Frame Analytics ({kibana-pull}204735[#204735]). +* Adds a missing space between lines in the Data Frame Analytics delete job modal ({kibana-pull}204732[#204732]). +* Fixes an issue where the Refresh button in the Anomaly Detection Datafeed counts table was unresponsive ({kibana-pull}204625[#204625]). +* Fixes the inference timeout check in File Upload ({kibana-pull}204722[#204722]). +* Fixes the side bar navigation for the Data Visualizer ({kibana-pull}205170[#205170]). + +[discrete] +[[serverless-changelog-12162024]] +=== December 16, 2024 + +[discrete] +[[deprecations-12162024]] +==== Deprecations +* Deprecates the `discover:searchFieldsFromSource` setting ({kibana-pull}202679[#202679]). +* Disables scripted field creation in the Data Views management page ({kibana-pull}202250[#202250]). +* Removes all logic based on the following settings: `xpack.reporting.roles.enabled`, +`xpack.reporting.roles.allow` ({kibana-pull}200834[#200834]). +* Removes the legacy table from Discover ({kibana-pull}201254[#201254]). +* Deprecates ephemeral tasks from action and alerting plugins ({kibana-pull}197421[#197421]). + +[discrete] +[[features-enhancements-12162024]] +==== Features and enhancements +* Optimizes the Kibana Trained Models API ({kibana-pull}200977[#200977]). +* Adds a *Create Case* action to the *Log rate analysis* page ({kibana-pull}201549[#201549]). +* Improves AI Assistant's response quality by giving it access to Elastic's product documentation ({kibana-pull}199694[#199694]). +* Adds support for suppressing EQL sequence alerts ({kibana-pull}189725[#189725]). +* Adds an *Advanced settings* section to the SLO form ({kibana-pull}200822[#200822]). +* Adds a new sub-feature privilege under **Synthetics and Uptime** `Can manage private locations` ({kibana-pull}201100[#201100]). + + +[discrete] +[[fixes-12162024]] +==== Fixes +* Fixes point visibility regression ({kibana-pull}202358[#202358]). +* Improves help text of creator and view count features on dashboard listing page ({kibana-pull}202488[#202488]). +* Highlights matching field values when performing a KQL search on a keyword field ({kibana-pull}201952[#201952]). +* Supports "Inspect" in saved search embeddables ({kibana-pull}202947[#202947]). +* Fixes your ability to clear the user-specific system prompt ({kibana-pull}202279[#202279]). +* Fixes error when opening rule flyout ({kibana-pull}202386[#202386]). +* Fixes to Ops Genie as a default connector ({kibana-pull}201923[#201923]). +* Fixes actions on charts ({kibana-pull}202443[#202443]). +* Adds flyout to table view in Infrastructure Inventory ({kibana-pull}202646[#202646]). +* Fixes service names with spaces not being URL encoded properly for `context.viewInAppUrl` ({kibana-pull}202890[#202890]). +* Allows access query logic to handle user ID and name conditions ({kibana-pull}202833[#202833]). +* Fixes APM rule error message for invalid KQL filter ({kibana-pull}203096[#203096]). +* Rejects CEF logs from Automatic Import and redirects you to the CEF integration instead ({kibana-pull}201792[#201792]). +* Updates the install rules title and message ({kibana-pull}202226[#202226]). +* Fixes error on second entity engine init API call ({kibana-pull}202903[#202903]). +* Restricts unsupported log formats ({kibana-pull}202994[#202994]). +* Removes errors related to Enterprise Search nodes ({kibana-pull}202437[#202437]). +* Improves web crawler name consistency ({kibana-pull}202738[#202738]). +* Fixes editor cursor jumpiness ({kibana-pull}202389[#202389]). +* Fixes rollover datastreams on subobjects mapper exception ({kibana-pull}202689[#202689]). +* Fixes spaces sync to retrieve 10,000 trained models ({kibana-pull}202712[#202712]). +* Fixes log rate analysis embeddable error on the Alerts page ({kibana-pull}203093[#203093]). +* Fixes Slack API connectors not displayed under Slack connector type when adding new connector to rule ({kibana-pull}202315[#202315]). + + +[discrete] +[[serverless-changelog-12092024]] +=== December 9, 2024 + +[discrete] +[[features-enhancements-12092024]] +==== Features and enhancements +* Elastic Observability Serverless adds a new sub-feature for managing private locations ({kibana-pull}201100[#201100]). +* Elastic Observability Serverless adds the ability to configure SLO advanced settings from the UI ({kibana-pull}200822[#200822]). +* Elastic Security Serverless adds support for suppressing EQL sequence alerts ({kibana-pull}189725[#189725]). +* Elastic Security Serverless adds a `/trained_models_list` endpoint to retrieve complete data for the Trained Model UI ({kibana-pull}200977[#200977]). +* Machine Learning adds an action to include log rate analysis in a case ({kibana-pull}199694[#199694]). +* Machine Learning enhances the Kibana API to optimize trained models ({kibana-pull}201549[#201549]). + +[discrete] +[[fixes-12092020]] +==== Fixes +* Fixes Slack API connectors not being displayed under the Slack connector type when adding a new connector to a rule in Alerting ({kibana-pull}202315[#202315]). +* Fixes point visibility regression in dashboard visualizations ({kibana-pull}202358[#202358]). +* Improves help text for creator and view count features on the Dashboard listing page ({kibana-pull}202488[#202488]). +* Highlights matching field values when performing a KQL search on a keyword field in Discover ({kibana-pull}201952[#201952]). +* Adds support for the *Inspect* option in saved search embeddables in Discover ({kibana-pull}202947[#202947]). +* Enables the ability to clear user-specific system prompts in Elastic Observability Serverless ({kibana-pull}202279[#202279]). +* Fixes an error when opening the rule flyout in Elastic Observability Serverless ({kibana-pull}202386[#202386]). +* Improves handling of Opsgenie as the default connector in Elastic Observability Serverless ({kibana-pull}201923[#201923]). +* Fixes issues with actions on charts in Elastic Observability Serverless ({kibana-pull}202443[#202443]). +* Adds a flyout to the table view in Infrastructure Inventory in Elastic Observability Serverless ({kibana-pull}202646[#202646]). +* Fixes service names with spaces not being URL-encoded properly for {{context.viewInAppUrl}} in Elastic Observability Serverless ({kibana-pull}202890[#202890]). +* Enhances access query logic to handle user ID and name conditions in Elastic Observability Serverless ({kibana-pull}202833[#202833]). +* Fixes an APM rule error message when a KQL filter is invalid in Elastic Observability Serverless ({kibana-pull}203096[#203096]). +* Restricts and rejects CEF logs in automatic import and redirects them to the CEF integration in Elastic Security Serverless ({kibana-pull}201792[#201792]). +* Updates the copy of the install rules title and message in Elastic Security Serverless ({kibana-pull}202226[#202226]). +* Clears errors on the second entity engine initialization API call in Elastic Security Serverless ({kibana-pull}202903[#202903]). +* Restricts unsupported log formats in Elastic Security Serverless ({kibana-pull}202994[#202994]). +* Removes errors related to Enterprise Search nodes in Elasticsearch Serverless ({kibana-pull}202437[#202437]). +* Ensures consistency in web crawler naming in Elasticsearch Serverless ({kibana-pull}202738[#202738]). +* Fixes editor cursor jumpiness in ES|QL ({kibana-pull}202389[#202389]). +* Implements rollover of data streams on subobject mapper exceptions in Fleet ({kibana-pull}202689[#202689]). +* Fixes trained models to retrieve up to 10,000 models when spaces are synced in Machine Learning ({kibana-pull}202712[#202712]). +* Fixes a Log Rate Analysis embeddable error on the Alerts page in AiOps ({kibana-pull}203093[#203093]). + +[discrete] +[[serverless-changelog-12032024]] +=== December 3, 2024 + +[discrete] +[[features-enhancements-12032024]] +==== Features and enhancements +* Adds tabs for Import Entities and Engine Status to the Entity Store ({kibana-pull}201235[#201235]). +* Adds status tracking for agentless integrations to {fleet} ({kibana-pull}199567[#199567]). +* Adds a new {ml} module that can detect anomalous activity in host-based logs ({kibana-pull}195582[#195582]). +* Allows custom Mapbox Vector Tile sources to style map layers and provide custom legends ({kibana-pull}200656[#200656]). +* Excludes stale SLOs from counts of healthy and violated SLOs ({kibana-pull}201027[#201027]). +* Adds a **Continue without adding integrations** button to the {elastic-sec} Dashboards page that takes you to the Entity Analytics dashboard ({kibana-pull}201363[#201363]). +* Displays visualization descriptions under their titles ({kibana-pull}198816[#198816]). + +[discrete] +[[fixes-12032024]] +==== Fixes +* Hides the *Clear* button when no filters are selected ({kibana-pull}200177[#200177]). +* Fixes a mismatch between how wildcards were handled in previews versus actual rule executions ({kibana-pull}201553[#201553]). +* Fixes incorrect Y-axis and hover values in the Service Inventory's Log rate chart ({kibana-pull}201361[#201361]). +* Disables the *Add note* button in the alert details flyout for users who lack privileges ({kibana-pull}201707[#201707]). +* Fixes the descriptions of threshold rules that use cardinality ({kibana-pull}201162[#201162]). +* Disables the *Install All* button on the **Add Elastic Rules** page when rules are installing ({kibana-pull}201731[#201731]). +* Reintroduces a data usage warning on the Entity Analytics Enablement modal ({kibana-pull}201920[#201920]). +* Improves accessibility for the **Create a connector** page ({kibana-pull}201590[#201590]). +* Fixes a bug that could cause {agents} to get stuck updating during scheduled upgrades ({kibana-pull}202126[#202126]). +* Fixes a bug related to starting {ml} deployments with autoscaling and no active nodes ({kibana-pull}201256[#201256]). +* Initializes saved objects when the **Trained Model** page loads ({kibana-pull}201426[#201426]). +* Fixes the display of deployment stats for unallocated deployments of {ml} models ({kibana-pull}202005[#202005]). +* Enables the solution type search for instant deployments ({kibana-pull}201688[#201688]). +* Improves the consistency of alert counts across different views ({kibana-pull}202188[#202188]). \ No newline at end of file From 65b950f73e2d8a0d74a2c8ec7361189d78ad965b Mon Sep 17 00:00:00 2001 From: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com> Date: Tue, 4 Feb 2025 12:59:43 -0500 Subject: [PATCH 03/14] Removes 206313 from the Feb 3, 2025 Serverless changelog (#2947) --- docs/en/install-upgrade/serverless-changelog.asciidoc | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/en/install-upgrade/serverless-changelog.asciidoc b/docs/en/install-upgrade/serverless-changelog.asciidoc index 23c40bb45..6e70e38af 100644 --- a/docs/en/install-upgrade/serverless-changelog.asciidoc +++ b/docs/en/install-upgrade/serverless-changelog.asciidoc @@ -33,7 +33,6 @@ For serverless changes in Cloud Console, refer to https://www.elastic.co/guide/e * Adds in-text citations to security solution AI assistant responses ({kibana-pull}206683[#206683]). * Remove Tech preview badge for GA ({kibana-pull}208523[#208523]). * Adds new View job detail flyouts for Anomaly detection and Data Frame Analytics ({kibana-pull}207141[#207141]). -* Rule gaps ({kibana-pull}206313[#206313]). * Adds a default "All logs" temporary data view in the Observability Solution view ({kibana-pull}205991[#205991]). * Adds Knowledge Base entries API ({kibana-pull}206407[#206407]). * Adds Kibana Support for Security AI Prompts Integration ({kibana-pull}207138[#207138]). From 8f468fdcc63cb5b4a3bb9faa475e3e0910689faf Mon Sep 17 00:00:00 2001 From: Lisa Cawley Date: Fri, 7 Feb 2025 12:30:15 -0800 Subject: [PATCH 04/14] Add 8.18 change base in mergify configuration (#2950) --- .mergify.yml | 56 ++++++++++++++++++++++++++++++++-------------------- 1 file changed, 35 insertions(+), 21 deletions(-) diff --git a/.mergify.yml b/.mergify.yml index f886533dd..12deb49a4 100644 --- a/.mergify.yml +++ b/.mergify.yml @@ -31,7 +31,7 @@ pull_request_rules: - name: backport patches to 8.x branch conditions: - merged - - base=main + - base=9.0 - label=backport-8.x actions: backport: @@ -42,10 +42,24 @@ pull_request_rules: title: "[{{ destination_branch }}] {{ title }} (backport #{{ number }})" labels: - backport + - name: backport patches to 8.18 branch + conditions: + - merged + - base=9.0 + - label=backport-8.18 + actions: + backport: + assignees: + - "{{ author }}" + branches: + - "8.18" + title: "[{{ destination_branch }}] {{ title }} (backport #{{ number }})" + labels: + - backport - name: backport patches to 8.17 branch conditions: - merged - - base=main + - base=9.0 - label=backport-8.17 actions: backport: @@ -59,7 +73,7 @@ pull_request_rules: - name: backport patches to 8.16 branch conditions: - merged - - base=main + - base=9.0 - label=backport-8.16 actions: backport: @@ -73,7 +87,7 @@ pull_request_rules: - name: backport patches to 8.15 branch conditions: - merged - - base=main + - base=9.0 - label=backport-8.15 actions: backport: @@ -87,7 +101,7 @@ pull_request_rules: - name: backport patches to 8.14 branch conditions: - merged - - base=main + - base=9.0 - label=backport-8.14 actions: backport: @@ -101,7 +115,7 @@ pull_request_rules: - name: backport patches to 8.13 branch conditions: - merged - - base=main + - base=9.0 - label=backport-8.13 actions: backport: @@ -115,7 +129,7 @@ pull_request_rules: - name: backport patches to 8.12 branch conditions: - merged - - base=main + - base=9.0 - label=backport-8.12 actions: backport: @@ -129,7 +143,7 @@ pull_request_rules: - name: backport patches to 8.11 branch conditions: - merged - - base=main + - base=9.0 - label=backport-8.11 actions: backport: @@ -143,7 +157,7 @@ pull_request_rules: - name: backport patches to 8.10 branch conditions: - merged - - base=main + - base=9.0 - label=backport-8.10 actions: backport: @@ -157,7 +171,7 @@ pull_request_rules: - name: backport patches to 8.9 branch conditions: - merged - - base=main + - base=9.0 - label=backport-8.9 actions: backport: @@ -171,7 +185,7 @@ pull_request_rules: - name: backport patches to 8.8 branch conditions: - merged - - base=main + - base=9.0 - label=backport-8.8 actions: backport: @@ -185,7 +199,7 @@ pull_request_rules: - name: backport patches to 8.7 branch conditions: - merged - - base=main + - base=9.0 - label=backport-8.7 actions: backport: @@ -199,7 +213,7 @@ pull_request_rules: - name: backport patches to 8.6 branch conditions: - merged - - base=main + - base=9.0 - label=backport-8.6 actions: backport: @@ -213,7 +227,7 @@ pull_request_rules: - name: backport patches to 8.5 branch conditions: - merged - - base=main + - base=9.0 - label=backport-8.5 actions: backport: @@ -227,7 +241,7 @@ pull_request_rules: - name: backport patches to 8.4 branch conditions: - merged - - base=main + - base=9.0 - label=backport-8.4 actions: backport: @@ -241,7 +255,7 @@ pull_request_rules: - name: backport patches to 8.3 branch conditions: - merged - - base=main + - base=9.0 - label=backport-8.3 actions: backport: @@ -255,7 +269,7 @@ pull_request_rules: - name: backport patches to 8.2 branch conditions: - merged - - base=main + - base=9.0 - label=backport-8.2 actions: backport: @@ -269,7 +283,7 @@ pull_request_rules: - name: backport patches to 8.1 branch conditions: - merged - - base=main + - base=9.0 - label=backport-8.1 actions: backport: @@ -283,7 +297,7 @@ pull_request_rules: - name: backport patches to 8.0 branch conditions: - merged - - base=main + - base=9.0 - label=backport-8.0 actions: backport: @@ -297,7 +311,7 @@ pull_request_rules: - name: backport patches to 7.17 branch conditions: - merged - - base=main + - base=9.0 - label=backport-7.17 actions: backport: @@ -311,7 +325,7 @@ pull_request_rules: - name: notify the backport policy conditions: - -label~=^backport - - base=main + - base=9.0 actions: comment: message: | From efb54d2960a6304e926f8b3d400a60f6b66186d9 Mon Sep 17 00:00:00 2001 From: Lisa Cawley Date: Mon, 10 Feb 2025 13:48:34 -0800 Subject: [PATCH 05/14] Add release notes placeholders for 9.0.0-beta1 (#2954) --- docs/en/install-upgrade/index.asciidoc | 10 +++++++++- .../release-notes/release-notes-elasticsearch.asciidoc | 8 ++++++++ .../release-notes/release-notes-kibana.asciidoc | 8 ++++++++ .../release-notes/release-notes-logstash.asciidoc | 8 ++++++++ .../release-notes/release-notes.asciidoc | 7 +++++++ 5 files changed, 40 insertions(+), 1 deletion(-) create mode 100644 docs/en/install-upgrade/release-notes/release-notes-elasticsearch.asciidoc create mode 100644 docs/en/install-upgrade/release-notes/release-notes-kibana.asciidoc create mode 100644 docs/en/install-upgrade/release-notes/release-notes-logstash.asciidoc create mode 100644 docs/en/install-upgrade/release-notes/release-notes.asciidoc diff --git a/docs/en/install-upgrade/index.asciidoc b/docs/en/install-upgrade/index.asciidoc index 298950e73..7840e59b6 100644 --- a/docs/en/install-upgrade/index.asciidoc +++ b/docs/en/install-upgrade/index.asciidoc @@ -32,8 +32,16 @@ include::upgrading-kibana.asciidoc[] // include::upgrading-agent.asciidoc[] +include::serverless-changelog.asciidoc[] + include::breaking.asciidoc[] -include::serverless-changelog.asciidoc[] +include::release-notes/release-notes.asciidoc[leveloffset=+1] + +include::release-notes/release-notes-elasticsearch.asciidoc[leveloffset=+2] + +include::release-notes/release-notes-kibana.asciidoc[leveloffset=+2] + +include::release-notes/release-notes-logstash.asciidoc[leveloffset=+2] include::redirects.asciidoc[] diff --git a/docs/en/install-upgrade/release-notes/release-notes-elasticsearch.asciidoc b/docs/en/install-upgrade/release-notes/release-notes-elasticsearch.asciidoc new file mode 100644 index 000000000..55548e966 --- /dev/null +++ b/docs/en/install-upgrade/release-notes/release-notes-elasticsearch.asciidoc @@ -0,0 +1,8 @@ +[[release-notes-elasticsearch-9.0.0-beta1]] += {es} version 9.0.0-beta1 +++++ +{es} +++++ + +coming::[9.0.0-beta1] + diff --git a/docs/en/install-upgrade/release-notes/release-notes-kibana.asciidoc b/docs/en/install-upgrade/release-notes/release-notes-kibana.asciidoc new file mode 100644 index 000000000..8d3ce2198 --- /dev/null +++ b/docs/en/install-upgrade/release-notes/release-notes-kibana.asciidoc @@ -0,0 +1,8 @@ +[[release-notes-kibana-9.0.0-beta1]] += {kib} version 9.0.0-beta1 +++++ +{kib} +++++ + +coming::[9.0.0-beta1] + diff --git a/docs/en/install-upgrade/release-notes/release-notes-logstash.asciidoc b/docs/en/install-upgrade/release-notes/release-notes-logstash.asciidoc new file mode 100644 index 000000000..4f3b59531 --- /dev/null +++ b/docs/en/install-upgrade/release-notes/release-notes-logstash.asciidoc @@ -0,0 +1,8 @@ +[[release-notes-logstash-9.0.0-beta1]] += {ls} version 9.0.0-beta1 +++++ +{ls} +++++ + +coming::[9.0.0-beta1] + diff --git a/docs/en/install-upgrade/release-notes/release-notes.asciidoc b/docs/en/install-upgrade/release-notes/release-notes.asciidoc new file mode 100644 index 000000000..75a753e2d --- /dev/null +++ b/docs/en/install-upgrade/release-notes/release-notes.asciidoc @@ -0,0 +1,7 @@ +[[elastic-stack-release-notes]] += Release notes + +This section summarizes the changes in the {stack} releases. + +coming::[9.0.0-beta1] + From 7b147d95a4190925fb8f33c10df76c67bb45b44e Mon Sep 17 00:00:00 2001 From: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com> Date: Mon, 10 Feb 2025 17:34:59 -0500 Subject: [PATCH 06/14] Adds release notes placeholders for Security 9.0.0-beta1 (#2955) * First draft * Fixed attribute * Add release note links --------- Co-authored-by: lcawl --- docs/en/install-upgrade/index.asciidoc | 2 ++ .../release-notes/release-notes-security.asciidoc | 7 +++++++ .../install-upgrade/release-notes/release-notes.asciidoc | 5 ++++- 3 files changed, 13 insertions(+), 1 deletion(-) create mode 100644 docs/en/install-upgrade/release-notes/release-notes-security.asciidoc diff --git a/docs/en/install-upgrade/index.asciidoc b/docs/en/install-upgrade/index.asciidoc index 7840e59b6..9ba33ba3d 100644 --- a/docs/en/install-upgrade/index.asciidoc +++ b/docs/en/install-upgrade/index.asciidoc @@ -44,4 +44,6 @@ include::release-notes/release-notes-kibana.asciidoc[leveloffset=+2] include::release-notes/release-notes-logstash.asciidoc[leveloffset=+2] +include::release-notes/release-notes-security.asciidoc[leveloffset=+2] + include::redirects.asciidoc[] diff --git a/docs/en/install-upgrade/release-notes/release-notes-security.asciidoc b/docs/en/install-upgrade/release-notes/release-notes-security.asciidoc new file mode 100644 index 000000000..9df35cc1c --- /dev/null +++ b/docs/en/install-upgrade/release-notes/release-notes-security.asciidoc @@ -0,0 +1,7 @@ +[[release-notes-security-9.0.0-beta1]] += {elastic-sec} version 9.0.0-beta1 +++++ +{elastic-sec} +++++ + +coming::[9.0.0-beta1] \ No newline at end of file diff --git a/docs/en/install-upgrade/release-notes/release-notes.asciidoc b/docs/en/install-upgrade/release-notes/release-notes.asciidoc index 75a753e2d..e015e2b52 100644 --- a/docs/en/install-upgrade/release-notes/release-notes.asciidoc +++ b/docs/en/install-upgrade/release-notes/release-notes.asciidoc @@ -3,5 +3,8 @@ This section summarizes the changes in the {stack} releases. -coming::[9.0.0-beta1] +* <> +* <> +* <> +* <> From 4939c3fa1798cced45e0425dc46e257fee6c5c38 Mon Sep 17 00:00:00 2001 From: Lisa Cawley Date: Tue, 11 Feb 2025 07:58:01 -0800 Subject: [PATCH 07/14] Update serverless changelog (#2953) --- .../serverless-changelog.asciidoc | 42 +++++++++++++++++++ 1 file changed, 42 insertions(+) diff --git a/docs/en/install-upgrade/serverless-changelog.asciidoc b/docs/en/install-upgrade/serverless-changelog.asciidoc index 6e70e38af..43466647f 100644 --- a/docs/en/install-upgrade/serverless-changelog.asciidoc +++ b/docs/en/install-upgrade/serverless-changelog.asciidoc @@ -10,6 +10,48 @@ For serverless API changes, refer to https://www.elastic.co/docs/api/changes[API For serverless changes in Cloud Console, refer to https://www.elastic.co/guide/en/cloud/current/ec-release-notes.html[Elasticsearch Service Documentation: Release notes]. +[discrete] +[[serverless-changelog-02102025]] +=== February 10, 2025 + +[discrete] +[[enhancements-02102025]] +==== Features and enhancements +* Rule connector - handle multiple prompt ({kibana-pull}209221[#209221]). +* Added max_file_size_bytes advanced option to malware for all operating systems ({kibana-pull}209541[#209541]). +* Introduce GroupStreams ({kibana-pull}208126[#208126]). +* Service example added to entity store upload ({kibana-pull}209023[#209023]). +* Update the `bucket_span` for ML jobs in the security_host module ({kibana-pull}209663[#209663]). +* Improved handling for operator-defined role mappings ({kibana-pull}208710[#208710]). +* Added `object_src` directive to `Content-Security-Policy-Report-Only` header ({kibana-pull}209306[#209306]). + +[discrete] +[[fixes-02102025]] +==== Fixes +* Fixes highlight for HJSON ({kibana-pull}208858[#208858]). +* Disable pointer events on drag + resize ({kibana-pull}208647[#208647]). +* Restore show missing dataView error message in case of missing datasource ({kibana-pull}208363[#208363]). +* Fixes issue with `Amsterdam` theme where charts render with the incorrect background color ({kibana-pull}209595[#209595]). +* Fixes an issue in Lens Table where a split-by metric on a terms rendered incorrect colors in table cells ({kibana-pull}208623[#208623]). +* Force return 0 on empty buckets on count if null flag is disabled ({kibana-pull}207308[#207308]). +* Fixes all embeddables rebuilt on refresh ({kibana-pull}209677[#209677]). +* Fixes using data view runtime fields during rule execution for the custom threshold rule ({kibana-pull}209133[#209133]). +* Running processes missing from processes table ({kibana-pull}209076[#209076]). +* Fixes missing exception stack trace ({kibana-pull}208577[#208577]). +* Fixes the preview chart in the Custom Threshold rule creation form when the field name has slashes ({kibana-pull}209263[#209263]). +* Display No Data in Threshold breached component ({kibana-pull}209561[#209561]). +* Fixes an issue where APM charts were rendered without required transaction type or service name, causing excessive alerts to appear ({kibana-pull}209552[#209552]). +* Fixed bug that caused issues with loading SLOs by status, SLI type, or instance id ({kibana-pull}209910[#209910]). +* Update colors in the AI Assistant icon ({kibana-pull}210233[#210233]). +* Update the simulate function calling setting to support "auto" ({kibana-pull}209628[#209628]). +* Fixes structured log template to use single quotes ({kibana-pull}209736[#209736]). +* Fixes ES|QL alert on alert ({kibana-pull}208894[#208894]). +* Fixes issue with multiple ip addresses in strings ({kibana-pull}209475[#209475]). +* Keeps the histogram config on time change ({kibana-pull}208053[#208053]). +* WHERE replacement ranges correctly generated for every case ({kibana-pull}209684[#209684]). +* Updates removed params of the Fleet -> Logstash output configurations ({kibana-pull}210115[#210115]). +* Fixes log rate analysis, change point detection, and pattern analysis embeddables not respecting filters from Dashboard's controls ({kibana-pull}210039[#210039]). + [discrete] [[serverless-changelog-02032025]] === February 3, 2025 From d1df4b49e85405b71235c42bbe9f98900c8df8aa Mon Sep 17 00:00:00 2001 From: Janeen Mikell Roberts <57149392+jmikell821@users.noreply.github.com> Date: Mon, 17 Feb 2025 11:37:07 -0500 Subject: [PATCH 08/14] [DOCS] Upgrade 9.0 beta1 (#2961) * Update upgrading-stack.asciidoc Pushing to save edits. * Update upgrading-stack.asciidoc * Saving to not lose edits. * Saving changes. * Lots of edits; saving. * Fix build errors * Change page nesting * Edits * Update structure --------- Co-authored-by: natasha-moore-elastic --- docs/en/install-upgrade/index.asciidoc | 8 + .../upgrade-deployment-cluster.asciidoc | 23 ++ .../upgrade-ingest-components.asciidoc | 0 .../install-upgrade/upgrade-on-ece.asciidoc | 46 ++++ .../install-upgrade/upgrade-on-eck.asciidoc | 143 +++++++++++++ .../upgrade-orchestrator.asciidoc | 20 ++ .../upgrading-elasticsearch.asciidoc | 4 +- .../install-upgrade/upgrading-kibana.asciidoc | 2 +- .../upgrading-stack-cloud.asciidoc | 70 +++--- .../upgrading-stack-on-prem.asciidoc | 18 +- .../install-upgrade/upgrading-stack.asciidoc | 199 ++++++++++++------ 11 files changed, 425 insertions(+), 108 deletions(-) create mode 100644 docs/en/install-upgrade/upgrade-deployment-cluster.asciidoc create mode 100644 docs/en/install-upgrade/upgrade-ingest-components.asciidoc create mode 100644 docs/en/install-upgrade/upgrade-on-ece.asciidoc create mode 100644 docs/en/install-upgrade/upgrade-on-eck.asciidoc create mode 100644 docs/en/install-upgrade/upgrade-orchestrator.asciidoc diff --git a/docs/en/install-upgrade/index.asciidoc b/docs/en/install-upgrade/index.asciidoc index 9ba33ba3d..2e4c3bdc3 100644 --- a/docs/en/install-upgrade/index.asciidoc +++ b/docs/en/install-upgrade/index.asciidoc @@ -16,8 +16,16 @@ include::air-gapped-install.asciidoc[] include::upgrading-stack.asciidoc[] +include::upgrade-orchestrator.asciidoc[] + +include::upgrade-deployment-cluster.asciidoc[] + include::upgrading-stack-cloud.asciidoc[] +include::upgrade-on-ece.asciidoc[] + +include::upgrade-on-eck.asciidoc[] + include::upgrading-stack-on-prem.asciidoc[] include::upgrading-elasticsearch.asciidoc[] diff --git a/docs/en/install-upgrade/upgrade-deployment-cluster.asciidoc b/docs/en/install-upgrade/upgrade-deployment-cluster.asciidoc new file mode 100644 index 000000000..1298104b2 --- /dev/null +++ b/docs/en/install-upgrade/upgrade-deployment-cluster.asciidoc @@ -0,0 +1,23 @@ +[[upgrade-deployment-cluster]] +== Upgrade your deployment or cluster + +Before you upgrade your deployment or cluster to {version}, ensure you're <>. + +The procedures you follow to upgrade depend on whether you've installed Elastic components using Elastic-managed infrastructure or self-managed infrastructure. + +If you're running Elastic-managed infrastructure, your options are: + +* <> +* Upgrading on {serverless-full} (updates are automatic and require no user management) + +If you're running your own self-managed infrastructure—either on-prem or on public cloud—your options are: + +* <> (upgrade each component individually) +* <> (ECE) +* <> (ECK) + +NOTE: Before you begin upgrading on ECE or ECK, ensure your orchestrator is compatible with {version}. + + + + diff --git a/docs/en/install-upgrade/upgrade-ingest-components.asciidoc b/docs/en/install-upgrade/upgrade-ingest-components.asciidoc new file mode 100644 index 000000000..e69de29bb diff --git a/docs/en/install-upgrade/upgrade-on-ece.asciidoc b/docs/en/install-upgrade/upgrade-on-ece.asciidoc new file mode 100644 index 000000000..14b719846 --- /dev/null +++ b/docs/en/install-upgrade/upgrade-on-ece.asciidoc @@ -0,0 +1,46 @@ +[[upgrade-on-ece]] +=== Upgrade on {ece} (ECE) + +Similar to {ecloud} Hosted, a single click in the {ecloud} console can upgrade a deployment running on ECE to a newer version. During the upgrade process, {es}, {kib}, and all of your deployment components are upgraded simultaneously. + +Once you're <>, do the following: + +. Ensure your current ECE and Docker versions are https://www.elastic.co/support/matrix/#matrix_os[compatible] with {version} (the minimum required version for 9.x is ECE 3.0). If you don’t have a compatible version installed, <>. +. Download the most recent {ece-ref}/ece-manage-elastic-stack.html#ece_most_recent_elastic_stack_packs[stack pack] for the version you're upgrading to, then {ece-ref}/ece-manage-elastic-stack.html#ece-manage-elastic-stack-add[add the stack pack] to your installation via the Cloud UI. +. Back up your data to a snapshot. First, {ece-ref}/ece-manage-repositories.html[configure a snapshot repository] to enable snapshots. + +[discrete] +[[perform-upgrade-ece]] +==== Perform the upgrade + +. Log in to the {ece-ref}/ece-login.html[Cloud UI]. +. On the Deployments page, select your deployment. ++ +Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters. + +To upgrade a deployment: + +. In the *Deployment version* section, click *Upgrade*. +. Select version {version}. +. Click *Upgrade*, then *Confirm upgrade*. The new configuration takes a few minutes to create. ++ +NOTE: If any incompatibilities are detected when you attempt to upgrade to {version}, the UI provides a link to the Upgrade Assistant, which checks for deprecated settings in your cluster and indices and helps you resolve them. After resolving the issues, return to the deployments page and restart the upgrade. + +Security realm settings:: +During the upgrade process, you are prompted to update the security realm settings if your user settings include a `xpack.security.authc.realms` value. ++ +If the security realms are configured in `user_settings`, you'll be prompted to modify the settings: ++ +.. On the *Update security realm settings* window, edit the settings. ++ +.. Click *Update settings*. ++ +If the security realm settings are located in `user_settings_override`, contact Support to help you upgrade. + +After you're done upgrading, upgrade your ingest components in the following order: + +. {ls}: {logstash-ref}/upgrading-logstash.html[upgrade instructions] +. {beats}: {beats-ref}/upgrading.html[upgrade instructions] +. {agent}: {fleet-guide}/upgrade-elastic-agent.html[upgrade instructions] +. {apm-agent}s: {observability-guide}/apm-upgrade.html[upgrade instructions] + diff --git a/docs/en/install-upgrade/upgrade-on-eck.asciidoc b/docs/en/install-upgrade/upgrade-on-eck.asciidoc new file mode 100644 index 000000000..310d3e196 --- /dev/null +++ b/docs/en/install-upgrade/upgrade-on-eck.asciidoc @@ -0,0 +1,143 @@ +[[upgrade-on-eck]] +=== Upgrade on {eck} (ECK) + +The ECK orchestrator can safely perform upgrades to newer versions of the various {stack} resources. + +To upgrade on ECK, first do the following: + +. Ensure you're <>. +. Ensure the ECK version is {eck-ref}/k8s-supported.html[compatible] with the {stack} version you’re targeting. If necessary, <>. + +[discrete] +[[perform-upgrade-eck]] +==== Perform the upgrade + +When you are ready, modify the `version` field in the resource spec to the desired stack version and the orchestrator will start the upgrade process automatically. Do this for each resource, including {es} and {kib}. In the following example, we’re modifying the version to `9.0.0`. + +[source,yaml,subs="attributes,+macros"] +---- +apiVersion: elasticsearch.k8s.elastic.co/v1 +kind: Elasticsearch +metadata: + name: elasticsearch-sample + namespace: production +spec: + version: 9.0.0 + monitoring: + metrics: + elasticsearchRefs: + - name: monitoring-cluster + namespace: observability + logs: + elasticsearchRefs: + - name: monitoring-cluster + namespace: observability + http: + service: + spec: + type: LoadBalancer + nodeSets: + - name: master + count: 3 + config: + node.roles: ["master"] + xpack.ml.enabled: true + node.store.allow_mmap: false + volumeClaimTemplates: + - metadata: + name: elasticsearch-data + spec: + accessModes: + - ReadWriteOnce + resources: + requests: + storage: 20Gi + storageClassName: standard + podTemplate: + metadata: + labels: + key: sample + spec: + initContainers: + - name: sysctl + securityContext: + privileged: true + command: ['sh', '-c', 'sysctl -w vm.max_map_count=262144'] + containers: + - name: elasticsearch + resources: + requests: + memory: 2Gi + cpu: 0.5 + limits: + memory: 2Gi + cpu: 1 + - name: data + count: 3 + config: + node.roles: ["data", "ingest", "ml", "transform"] + node.store.allow_mmap: false + volumeClaimTemplates: + - metadata: + name: elasticsearch-data + spec: + accessModes: + - ReadWriteOnce + resources: + requests: + storage: 20Gi + storageClassName: standard + podTemplate: + metadata: + labels: + key: sample + spec: + initContainers: + - name: sysctl + securityContext: + privileged: true + command: ['sh', '-c', 'sysctl -w vm.max_map_count=262144'] + containers: + - name: elasticsearch + resources: + requests: + memory: 2Gi + cpu: 0.5 + limits: + memory: 2Gi + cpu: 1 +--- +apiVersion: kibana.k8s.elastic.co/v1 +kind: Kibana +metadata: + name: kibana-sample + namespace: production +spec: + version: 9.0.0 + monitoring: + metrics: + elasticsearchRefs: + - name: monitoring-cluster + namespace: observability + logs: + elasticsearchRefs: + - name: monitoring-cluster + namespace: observability + http: + service: + spec: + type: LoadBalancer + count: 1 + elasticsearchRef: + name: elasticsearch-sample + +---- + +ECK will ensure that {stack} resources are upgraded in the correct order. For more information on how the orchestrator performs upgrades and how to tune its behavior, check out {eck-ref}/k8s-orchestration.html[Nodes orchestration]. + +Next, upgrade your ingest components in the following order: + +. {ls}: {logstash-ref}/upgrading-logstash.html[upgrade instructions] +. {beats}: {beats-ref}/upgrading.html[upgrade instructions] +. {agent}: {fleet-guide}/upgrade-elastic-agent.html[upgrade instructions] +. {apm-agent}s: {observability-guide}/apm-upgrade.html[upgrade instructions] \ No newline at end of file diff --git a/docs/en/install-upgrade/upgrade-orchestrator.asciidoc b/docs/en/install-upgrade/upgrade-orchestrator.asciidoc new file mode 100644 index 000000000..1685ae995 --- /dev/null +++ b/docs/en/install-upgrade/upgrade-orchestrator.asciidoc @@ -0,0 +1,20 @@ +[[upgrade-orchestrator]] +== Upgrade your orchestrator + +NOTE: This topic applies only to customers running the {stack} on {ece} (ECE) or {eck} (ECK). + +Elastic provides customers with two major self-managed orchestrators to manage the {stack}. Before you can upgrade the products in the stack, you need to ensure your orchestrator is running a compatible version. If it's incompatible, you'll need to upgrade the orchestrator first before you can upgrade the stack. + +[discrete] +=== Upgrade ECE + +{ece} (ECE) provides an easy way to provision, manage, and scale a fleet of {es} deployments from a central place. It can be installed on a public cloud platform, such as AWS, GCP or Microsoft Azure, on your own private cloud, or on bare metal. + +If you’re planning to upgrade to {version}, the minimum required version is ECE 3.0.0. If you're running an earlier version, refer to {ece-ref}/ece-upgrade.html[Upgrade your installation] for instructions on how to upgrade. + +[discrete] +=== Upgrade ECK + +{eck} (ECK) is built on the Kubernetes operator pattern and extends the basic Kubernetes orchestration capabilities to support the setup and management of Elastic products and solutions on Kubernetes. + +If you're planning to upgrade to {version}, refer to the list of {eck-ref}/k8s-supported.html[supported versions] to ensure your current ECK version is compatible. If it isn't, refer to {eck-ref}/k8s-upgrading-eck.html[Upgrade ECK] for instructions on how to upgrade. diff --git a/docs/en/install-upgrade/upgrading-elasticsearch.asciidoc b/docs/en/install-upgrade/upgrading-elasticsearch.asciidoc index 4fa2b7e24..f6bd73740 100644 --- a/docs/en/install-upgrade/upgrading-elasticsearch.asciidoc +++ b/docs/en/install-upgrade/upgrading-elasticsearch.asciidoc @@ -1,5 +1,5 @@ [[upgrading-elasticsearch]] -== Upgrade {es} +=== Upgrade {es} An {es} cluster can be upgraded one node at a time so upgrading does not interrupt service. Running multiple versions of @@ -332,7 +332,7 @@ upgraded master. [discrete] [[archived-settings]] -=== Archived settings +==== Archived settings If you upgrade an {es} cluster that uses deprecated cluster or index settings that are not used in the target version, they are archived. We diff --git a/docs/en/install-upgrade/upgrading-kibana.asciidoc b/docs/en/install-upgrade/upgrading-kibana.asciidoc index c8e9c36fb..a0b012408 100644 --- a/docs/en/install-upgrade/upgrading-kibana.asciidoc +++ b/docs/en/install-upgrade/upgrading-kibana.asciidoc @@ -1,5 +1,5 @@ [[upgrading-kibana]] -== Upgrade {kib} +=== Upgrade {kib} [WARNING] ==== diff --git a/docs/en/install-upgrade/upgrading-stack-cloud.asciidoc b/docs/en/install-upgrade/upgrading-stack-cloud.asciidoc index de0785de9..448a34e92 100644 --- a/docs/en/install-upgrade/upgrading-stack-cloud.asciidoc +++ b/docs/en/install-upgrade/upgrading-stack-cloud.asciidoc @@ -1,22 +1,19 @@ [[upgrade-elastic-stack-for-elastic-cloud]] -=== Upgrade on Elastic Cloud +=== Upgrade on {ecloud} Hosted -Once you are <>, -a single click in the Elastic Cloud console can upgrade a deployment to a newer -version, add more processing capacity, change plugins, and enable or disable -high availability, all at the same time. During the upgrade process, -{es}, {kib}, and all of your deployment components are upgraded simultaneously. +Once you are <>, +a single click in the {ecloud} console can upgrade a deployment to a newer version, add more processing capacity, change plugins, and enable or disable high availability, all at the same time. During the upgrade process, {es}, {kib}, and all of your deployment components are upgraded simultaneously. -Minor version upgrades, upgrades from {prev-major-last} to {version}, +Minor version upgrades, upgrades from 8.18 to {version}, and cluster configuration changes can be performed with no downtime. -Elastic Cloud only supports upgrades to released versions. +{ecloud} only supports upgrades to released versions. Preview releases and master snapshots are not supported. -{ess} and {ece} do not support the ability to upgrade to or from release candidate builds, such as 8.0.0-rc1. +{ecloud} Hosted and {ece} do not support the ability to upgrade to or from release candidate builds, such as 9.0.0-rc1. -If you use a separate {cloud}/ec-enable-logging-and-monitoring.html[monitoring deployment], you should upgrade the monitoring deployment before the production deployment. In general, the monitoring deployment and the deployments being monitored should be running the same version of the Elastic Stack. A monitoring deployment cannot monitor production deployments running newer versions of the stack. If necessary, the monitoring deployment can monitor production deployments running the latest release of the previous major version. +If you use a separate {cloud}/ec-enable-logging-and-monitoring.html[monitoring deployment], you should upgrade the monitoring deployment before the production deployment. In general, the monitoring deployment and the deployments being monitored should be running the same version of the {stack}. A monitoring deployment cannot monitor production deployments running newer versions of the stack. If necessary, the monitoring deployment can monitor production deployments running the latest release of the previous major version. -IMPORTANT: Although it's simple to upgrade an Elastic Cloud deployment, +IMPORTANT: Although it's simple to upgrade an {ecloud} deployment, the new version might include breaking changes that affect your application. Make sure you review the deprecation logs, make any necessary changes, and test against the new version before upgrading your production deployment. @@ -24,7 +21,7 @@ and test against the new version before upgrading your production deployment. //To learn more about the upgrade process on Elastic Cloud, see {cloud}/ec-upgrade-deployment.html[Upgrade versions]. Upgrade Assistant:: -Prior to upgrading, Elastic Cloud checks the deprecation API to retrieve information about the cluster, node, and index-level settings that need to be removed or changed. If there are any issues that would prevent a successful upgrade, the upgrade is blocked. Use the {kibana-ref-all}/{prev-major-last}/upgrade-assistant.html[Upgrade Assistant] in {prev-major-last} to identify and resolve issues and reindex any indices created before 7.0. +Prior to upgrading, {ecloud} checks the deprecation API to retrieve information about the cluster, node, and index-level settings that need to be removed or changed. If there are any issues that would prevent a successful upgrade, the upgrade is blocked. Use the {kibana-ref}/upgrade-assistant.html[Upgrade Assistant] in 8.18 to identify and resolve issues and reindex any indices created before 8.0. Snapshots:: To keep your data safe during the upgrade process, a snapshot is taken automatically @@ -56,45 +53,37 @@ If the security realms are configured in `user_settings`, you'll be prompted to . On the *Update security realm settings* window, edit the settings. + . Click *Update settings*. -If the security realm settings are located in `user_settings_override`, contact support to help you upgrade. +If the security realm settings are located in `user_settings_override`, contact Support to help you upgrade. [discrete] [[perform-cloud-upgrade]] -=== Perform the upgrade +==== Perform the upgrade -Log in to your Elastic Cloud environment: +Log in to your {ecloud} environment: + +. Log in to the {ecloud} Hosted https://cloud.elastic.co/login[console]. +. Select your deployment on the home page in the {ecloud} Hosted card or go to the Deployments page. ++ +Narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. //include::tab-widgets/code.asciidoc[] //include::tab-widgets/cloud-login-widget.asciidoc[] -include::{docs-root}/shared/cloud/tab-widgets/code.asciidoc[] -include::{docs-root}/shared/cloud/tab-widgets/cloud-login-widget.asciidoc[] +//include::{docs-root}/shared/cloud/tab-widgets/code.asciidoc[] +//include::{docs-root}/shared/cloud/tab-widgets/cloud-login-widget.asciidoc[] To upgrade a deployment: . In the *Deployment version* section, click *Upgrade*. . Select version {version}. -. Click *Upgrade* and then *Confirm upgrade*. The new configuration takes a few minutes to create. +. Click *Upgrade*, then *Confirm upgrade*. The new configuration takes a few minutes to create. + NOTE: If any incompatibilities are detected when you attempt to upgrade to {version}, the UI provides a link to the Upgrade Assistant, which checks for deprecated settings in your cluster and indices and helps you resolve them. After resolving the issues, return to the deployments page and restart the upgrade. -[discrete] -[[upgrading-clients-ingest]] -=== Upgrading {es} clients and ingest components - -Once you have upgraded from {prev-major-last}, you need to update your {es} clients and ingest components -in the following order: - -. Java API Client: {java-api-client}/installation.html#maven[dependency configuration] -. Logstash: {logstash-ref}/upgrading-logstash.html[upgrade instructions] -. Beats: {beats-ref}/upgrading.html[upgrade instructions] -. {agent}: {fleet-guide}/upgrade-elastic-agent.html[upgrade instructions] - [discrete] [[upgrading-reindex]] -=== Reindex to upgrade +==== Reindex to upgrade -If you are running a pre-{prev-major-version} version, you might need to perform multiple upgrades -or a full-cluster restart to get to {prev-major-last} to prepare to upgrade to {version}. +If you are running a pre-{prev-major-version} version, you might need to perform multiple upgrades or a full-cluster restart to get to 8.18 to then prepare to upgrade to {version}. Alternatively, you can create a new {version} deployment and reindex from remote: @@ -107,6 +96,19 @@ and temporarily send new index requests to both clusters. permanently swap in the new cluster. . Delete the old deployment. -On Elastic Cloud, you are billed only for the time that the new deployment +On {ecloud}, you are billed only for the time that the new deployment runs in parallel with your old deployment. Usage is billed on an hourly basis. + + +[discrete] +[[upgrading-clients-ingest]] +==== Upgrading {es} clients and ingest components + +Once you have upgraded from 8.18, you need to update your ingest components in the following order: + +//. Java API Client: {java-api-client}/installation.html#maven[dependency configuration] +. {ls}: {logstash-ref}/upgrading-logstash.html[upgrade instructions] +. {beats}: {beats-ref}/upgrading.html[upgrade instructions] +. {agent}: {fleet-guide}/upgrade-elastic-agent.html[upgrade instructions] +. {apm-agent}s: {observability-guide}/apm-upgrade.html[upgrade instructions] \ No newline at end of file diff --git a/docs/en/install-upgrade/upgrading-stack-on-prem.asciidoc b/docs/en/install-upgrade/upgrading-stack-on-prem.asciidoc index 158952e4b..e2bc23631 100644 --- a/docs/en/install-upgrade/upgrading-stack-on-prem.asciidoc +++ b/docs/en/install-upgrade/upgrading-stack-on-prem.asciidoc @@ -1,5 +1,5 @@ [[upgrading-elastic-stack-on-prem]] -=== Upgrade Elastic on-prem +== Upgrade Elastic on self-managed infrastructure Once you are <>, you will need to upgrade each of your Elastic components individually. @@ -8,12 +8,14 @@ you will need to upgrade each of your Elastic components individually. jobs can continue to run during a rolling upgrade, it increases the overhead on the cluster during the upgrade process. -. Upgrade the components of your Elastic Stack in the following order: +. Upgrade the components of your {stack} in the following order: ++ -.. {es} Hadoop: {hadoop-ref}/install.html[install instructions] +//.. {es} Hadoop: {hadoop-ref}/install.html[install instructions] .. {es}: <> -.. Kibana: <> -.. Java API Client: {java-api-client}/installation.html#maven[dependency configuration] -.. Logstash: {logstash-ref}/upgrading-logstash.html[upgrade instructions] -.. Beats: {beats-ref}/upgrading.html[upgrade instructions] -.. {agent}: {fleet-guide}/upgrade-elastic-agent.html[upgrade instructions] \ No newline at end of file +.. {kib}: <> +//.. Java API Client: {java-api-client}/installation.html#maven[dependency configuration] +.. {ls}: {logstash-ref}/upgrading-logstash.html[upgrade instructions] +.. {beats}: {beats-ref}/upgrading.html[upgrade instructions] +.. {agent}: {fleet-guide}/upgrade-elastic-agent.html[upgrade instructions] +.. {apm-agent}s {observability-guide}/apm-upgrade.html[upgrade instructions] \ No newline at end of file diff --git a/docs/en/install-upgrade/upgrading-stack.asciidoc b/docs/en/install-upgrade/upgrading-stack.asciidoc index 4219c92ac..7c6803b02 100644 --- a/docs/en/install-upgrade/upgrading-stack.asciidoc +++ b/docs/en/install-upgrade/upgrading-stack.asciidoc @@ -1,69 +1,93 @@ [[upgrading-elastic-stack]] -== Upgrade to Elastic {version} += Upgrade to Elastic {version} -Before you upgrade to {version}, it's important to take some preparation steps. -ifeval::["{version}"!="8.0.0"] -These steps vary based on your current version: +Upgrading to the latest version provides you access to Elastic latest features, enhancements, performance improvements, and bug fixes, many of which enable you to save your organization money, respond faster to potential threats, and improve the tools you use to investigate and analyze your data. As new versions are released, older versions reach their end of life at a regular cadence, so it’s important to ensure that your deployment is fully maintained and supported. For more information, refer to Elastic’s https://www.elastic.co/support/eol[Product End of Life Dates]. -* <> -* <> -endif::[] +[discrete] +[[plan-upgrade]] +== Plan your upgrade -IMPORTANT: Upgrading from a release candidate build, such as 8.0.0-rc1 or -8.0.0-rc2, is not supported. Pre-releases should only be used for testing in a -temporary environment. +Before you upgrade, there are a number of things that you need to plan for before performing the actual upgrade, so create a test plan. Consider the following recommendations: + +* Plan for an appropriate amount of time to complete the upgrade. Depending on your configuration and the size of your cluster, the process can take up a few weeks or or more to complete. + +* Consider opening a https://support.elastic.co/case[support case] with Elastic to alert our Elastic Support team of your system change. If you need additional assistance, https://www.elastic.co/consulting[Elastic Consulting Services] provides the technical expertise and step-by-step approach for upgrading your Elastic deployment. + +* Schedule a system maintenance window within your organization. + +**Check system requirements** + +Ensure the version you’re upgrading to for Elasticsearch, Kibana, and any ingest components supports your current operating system. Refer to the Product and Operating System https://www.elastic.co/support/matrix#matrix_os[support matrix]. + +**JVM and FIPS compliance** + +By default, {es} includes a bundled Java Virtual Machine (JVM) supported by Elastic. While we strongly recommend using the bundled JVM in all installations of Elasticsearch, if you choose to use your own JVM, ensure it’s compatible by reviewing the Product and JVM https://www.elastic.co/support/matrix#matrix_jvm[support matrix]. {es} 9.0+ requires Java 21 or later. + +If you’re running {es} in FIPS 140-2 mode, {es} 9.0+ has been tested with https://www.bouncycastle.org/java.html[Bouncy Castle]'s FIPS implementation and is the recommended Java security provider when running Elasticsearch. + +*Conduct a component inventory* + +It is very important to map all the components that are being used on the {stack}. When you upgrade your deployment, you may also need to upgrade all the other components. You should record if each component is used, and if it is, you should record its current version. While this is not a comprehensive list, here are some components you should check: + +* {es} +* {es} Hadoop +* {es} Plugins +* {es} clients +* {kib} +* {ls} +* {ls} plugins +* {beats} +* {beats} modules +* {apm-agent}s +* APM server +* {agent} +* {fleet} +* Enterprise Search server +* Security +* Browsers +* External services (Kafka, etc.) + +TIP: When you do your inventory, you can {ref}/enable-audit-logging.html[enable audit logging] to evaluate resources that are accessing your deployment. -ifeval::["{version}"!="8.0.0"] [discrete] -[[prepare-to-upgrade-8x]] -=== Prepare to upgrade from an earlier 8.x version +[[choose-upgrade-path]] +== Choose your upgrade path -. Review the breaking changes for each product you use and make the necessary -changes so your code is compatible with {version}: -+ --- -include::breaking.asciidoc[tag=breaking-changes-links] +The procedures you follow to upgrade depend on your infrastructure and deployment method. You’ve installed Elastic components using either Elastic-managed infrastructure or self-managed infrastructure. -include::breaking.asciidoc[tag=breaking-changes-admon] --- +Elastic-managed infrastructure includes {ecloud} – the umbrella term for {ecloud} Hosted (ECH) and {serverless-full}. {serverless-full} (“Serverless”) is the fully managed cloud offering and has three products: {es-serverless}, {obs-serverless}, and {sec-serverless}. All serverless products are built on top of the Search AI Lake. Customers receive the latest features automatically when updates are published. -include::upgrading-stack.asciidoc[tag=generic-upgrade-steps] -endif::[] +{ecloud} Hosted is Elastic’s cloud offering for managing {stack} deployments, built on top of {es}. A single click in the {ecloud} console can upgrade a deployment to a newer version. -//// -// List of upgrade steps used in both 8.x and 7.x -// tag::generic-upgrade-steps[] -. If you use any {es} plugins, make sure there is a version of each plugin that is -compatible with {es} version {version}. +Self-managed infrastructure — either on-prem or on public cloud, includes: -. Test the upgrade in an isolated environment before upgrading your production -cluster. +* {stack} +* {ece} (ECE) +* {eck} (ECK) -. Make sure you have a current snapshot before you start the upgrade. -+ -IMPORTANT: You cannot downgrade {es} nodes after upgrading. -If you cannot complete the upgrade process, -you will need to restore from the snapshot. +For ECE and ECK, you need to ensure the orchestrator is running a compatible version with the {stack} version you’re upgrading to. If not, you need to <> your orchestrator before you can upgrade your cluster. -. If you use a separate {ref}/monitoring-production.html[monitoring cluster], you should upgrade the monitoring cluster before the production cluster. In general, the monitoring cluster and the clusters being monitored should be running the same version of the stack. A monitoring cluster cannot monitor production clusters running newer versions of the stack. If necessary, the monitoring cluster can monitor production clusters running the latest release of the previous major version. -// end::generic-upgrade-steps[] -//// +If you’re running the {stack} on your own self-managed infrastructure, you’ll need to upgrade each component individually. [discrete] -[[prepare-to-upgrade]] -=== Prepare to upgrade from 7.x +[[prepare-upgrade-9.0]] +== Prepare to upgrade -To upgrade to {version} from 7.16 or earlier, **you must first upgrade to {prev-major-last}**. -This enables you to use the **Upgrade Assistant** to identify and resolve issues, -reindex indices created before 7.0, and then perform a rolling upgrade. +Before you upgrade to {version}, it's important to take some preparation steps. Unless noted, these following recommendations are best practices regardless of deployment method. + +IMPORTANT: Upgrading from a release candidate build, such as 9.0.0-rc1 or 9.0.0-rc2, is not supported. Pre-releases should only be used for testing in a temporary environment. + +To upgrade to {version} from 8.17 or earlier, **you must first upgrade to the latest patch version of 8.18**. This enables you to use the **Upgrade Assistant** to identify and resolve issues, +reindex indices created before 8.0, and then perform a rolling upgrade. + +*Upgrading to 8.18 before upgrading to {version} is required +even if you opt to do a full-cluster restart of your {es} cluster.* -**Upgrading to {prev-major-last} before upgrading to {version} is required -even if you opt to do a full-cluster restart of your {es} cluster.** Alternatively, you can create a new {version} deployment and reindex from remote. -For more information, see <>. +For more information, refer to <>. -{beats} and {ls} {prev-major-last} are compatible with {es} {version} +{beats} and {ls} 8.17 are compatible with {es} {version} to give you flexibility in scheduling the upgrade. .Remote cluster compatibility @@ -78,26 +102,20 @@ For more information, see {ref}/xpack-ccr.html[Cross cluster replication] for ve You can view your remote clusters from **Stack Management > Remote Clusters**. ==== -. Use the {kibana-ref-all}/{prev-major-last}/upgrade-assistant.html[Upgrade Assistant] -to prepare for your upgrade from {prev-major-last} to {version}. -The **Upgrade Assistant** identifies deprecated settings and guides -you through resolving issues and reindexing indices created before 7.0. -Make sure you have a current snapshot before making configuration changes -or reindexing. -+ -**You must resolve all critical issues before proceeding with the upgrade.** +. Once you've upgraded to 8.18, use the {kibana-ref}/upgrade-assistant.html[*Upgrade Assistant*] to prepare for your upgrade from 8.18 to {version}. The Upgrade Assistant identifies deprecated settings and guides you through resolving issues and reindexing indices created before 8.0. {es} fully supports indices created in the current or previous major version. Older indices are partly supported as read-only archives with limited capabilities. +//For example, {es} {version} fully supports indices, data streams, and searchable snapshots created in {es}8.x, but those created in {es} 7.x would be read-only and indices Elasticsearch 6.x or older would not be compatible with Elasticsearch 9.x.// -. Review the deprecation logs from the **Upgrade Assistant** to -determine if your applications are using features that are not supported -or behave differently in 8.x. -See the <> for more information -about changes in {version} that could affect your application. +. Ensure you have a current {ref}/snapshots-take-snapshot.html[snapshot] before making configuration changes or reindexing. +*You must resolve all critical issues before proceeding with the upgrade.* If you make any additional changes, take a new snapshot to back up your data. + -IMPORTANT: Make sure you check the breaking changes for each minor 8.x release -up to {version}. +NOTE: If you’re upgrading on {ecloud} Hosted, to keep your data safe during the upgrade process, a snapshot is taken automatically before any changes are made to your cluster. If you’re upgrading on {ece}, you need to {ece-ref}/ece-manage-repositories.html[configure a snapshot repository] to enable snapshots. + +. Ensure you carefully review the deprecation logs from the Upgrade Assistant to determine if your applications are using features that are not supported or behave differently in {version}. -. Make the recommended changes to ensure that your applications -continue to operate as expected after the upgrade. +. Major version upgrades can include breaking changes that require you to take additional steps to ensure that your applications behave as expected after the upgrade. Review all {version} <> for each product you use to view more information about changes that could affect your application. Ensure you test against the new version before upgrading existing deployments. ++ +IMPORTANT: Ensure you check the breaking changes for each minor 8.x release up to {version}. +. Make the recommended changes to ensure that your clients continue to operate as expected after the upgrade. + NOTE: As a temporary solution, you can submit requests to {major-version} using the {prev-major-version} syntax with the REST API compatibility mode. @@ -106,5 +124,60 @@ it does not guarantee the same behavior. REST API compatibility should be a bridge to smooth out the upgrade process, not a long term strategy. For more information, see {ref}/rest-api-compatibility.html[REST API compatibility]. +. If you use any {es} plugins, ensure there is a version of each plugin that is compatible with {version}. +. We recommend creating a 9.0 test deployment and testing the upgrade in an isolated environment before upgrading your production deployment. Ensure that both your test and production environments have the same settings. ++ +IMPORTANT: You cannot downgrade {es} nodes after upgrading. If you cannot complete the upgrade process, you will need to {ref}/snapshots-restore-snapshot.html[restore from the snapshot]. ++ +. If you use a separate {ref}/monitoring-production.html[monitoring cluster], you should upgrade the monitoring cluster before the production cluster. In general, the monitoring cluster and the clusters being monitored should be running the same version of the stack. A monitoring cluster cannot monitor production clusters running newer versions of the stack. If necessary, the monitoring cluster can monitor production clusters running the latest release of the previous major version. + + + + + +//// +Before you upgrade to {version}, it's important to take some preparation steps. +ifeval::["{version}"!="8.0.0"] +These steps vary based on your current version: + +* <> +* <> +endif::[] + +IMPORTANT: Upgrading from a release candidate build, such as 8.0.0-rc1 or +8.0.0-rc2, is not supported. Pre-releases should only be used for testing in a +temporary environment. + +ifeval::["{version}"!="8.0.0"] +[discrete] +[[prepare-to-upgrade-8x]] +=== Prepare to upgrade from an earlier 8.x version + +. Review the breaking changes for each product you use and make the necessary +changes so your code is compatible with {version}: ++ +-- +include::breaking.asciidoc[tag=breaking-changes-links] + +include::breaking.asciidoc[tag=breaking-changes-admon] +-- include::upgrading-stack.asciidoc[tag=generic-upgrade-steps] +endif::[] + +//// +// List of upgrade steps used in both 8.x and 7.x +// tag::generic-upgrade-steps[] +//. If you use any {es} plugins, make sure there is a version of each plugin that is compatible with {es} version {version}. + +//. Test the upgrade in an isolated environment before upgrading your production cluster. + +//. Make sure you have a current snapshot before you start the upgrade. +//+ +//IMPORTANT: You cannot downgrade {es} nodes after upgrading. +//If you cannot complete the upgrade process, you will need to restore from the snapshot. + +//. If you use a separate {ref}/monitoring-production.html[monitoring cluster], you should upgrade the monitoring cluster before the production cluster. In general, the monitoring cluster and the clusters being monitored should be running the same version of the stack. A monitoring cluster cannot monitor production clusters running newer versions of the stack. If necessary, the monitoring cluster can monitor production clusters running the latest release of the previous major version. +// +// end::generic-upgrade-steps[] + From 2c37db4e320c7598ae1dfb5faf0e2f57bf1c7246 Mon Sep 17 00:00:00 2001 From: florent-leborgne Date: Tue, 18 Feb 2025 16:08:50 +0100 Subject: [PATCH 09/14] Add serverless changelog for Feb 17 (#2963) --- .../serverless-changelog.asciidoc | 59 +++++++++++++++++++ 1 file changed, 59 insertions(+) diff --git a/docs/en/install-upgrade/serverless-changelog.asciidoc b/docs/en/install-upgrade/serverless-changelog.asciidoc index 43466647f..2f4802003 100644 --- a/docs/en/install-upgrade/serverless-changelog.asciidoc +++ b/docs/en/install-upgrade/serverless-changelog.asciidoc @@ -10,6 +10,65 @@ For serverless API changes, refer to https://www.elastic.co/docs/api/changes[API For serverless changes in Cloud Console, refer to https://www.elastic.co/guide/en/cloud/current/ec-release-notes.html[Elasticsearch Service Documentation: Release notes]. +[discrete] +[[serverless-changelog-02172025]] +=== February 17, 2025 + +[discrete] +[[features-02172025]] +==== Features and enhancements +* Adds alert status management to the AI Assistant connector ({kibana-pull}203729[#203729]). +* Enables the new Borealis theme ({kibana-pull}210468[#210468]). +* Applies compact Display options Popover layout ({kibana-pull}210180[#210180]). +* Increases search timeout toast lifetime to 1 week ({kibana-pull}210576[#210576]). +* Improves performance in `dependencies` endpoints to prevent high CPU usage ({kibana-pull}209999[#209999]). +* Adds "Logs" tab to mobile services ({kibana-pull}209944[#209944]). +* Adds "All logs" data view to the Classic navigation ({kibana-pull}209042[#209042]). +* Changes default to "native" function calling if the connector configuration is not exposed ({kibana-pull}210455[#210455]). +* Updates entity insight badge to open entity flyouts ({kibana-pull}208287[#208287]). +* Standardizes actions in Alerts KPI visualizations ({kibana-pull}206340[#206340]). +* Allows the creation of dynamic aggregations controls for ES|QL charts ({kibana-pull}210170[#210170]). +* Fixes the values control FT ({kibana-pull}211159[#211159]). +* Trained models: Replaces the download button by extending the deploy action ({kibana-pull}205699[#205699]). +* Adds the `useCustomDragHandle` property ({kibana-pull}210463[#210463]). + +[discrete] +[[fixes-02172025]] +==== Fixes +* Fixes an issue where clicking on the name badge for a synthetics monitor on an SLO details page would lead to a page that failed to load monitor details ({kibana-pull}210695[#210695]). +* Fixes an issue where the popover in the rules page may get stuck when being clicked more than once ({kibana-pull}208996[#208996]). +* Fixes an error in the cases list when the case assignee is an empty string ({kibana-pull}209973[#209973]). +* Fixes an issue with assigning color mappings when multiple layers are defined ({kibana-pull}208571[#208571]). +* Fixes an issue where behind text colors were not correctly assigned, such as in `Pie`, `Treemap` and `Mosaic` charts. ({kibana-pull}209632[#209632]). +* Fixes an issue where dynamic coloring has been disabled from Last value aggregation types ({kibana-pull}209110[#209110]). +* Fixes panel styles ({kibana-pull}210113[#210113]). +* Fixes incorrectly serialized `searchSessionId` attribute ({kibana-pull}210765[#210765]). +* Fixes the "Save to library" action that could break the chart panel ({kibana-pull}210125[#210125]). +* Fixes link settings not persisting ({kibana-pull}211041[#211041]). +* Fixes "Untitled" export title when exporting CSV from a dashboard ({kibana-pull}210143[#210143]). +* Missing items in the trace waterfall shouldn't break it entirely ({kibana-pull}210210[#210210]). +* Removes unused `error.id` in `getErrorGroupMainStatistics` queries ({kibana-pull}210613[#210613]). +* Fixes connector test in MKI ({kibana-pull}211235[#211235]). +* Clicking a link in the host/user flyout does not refresh details panel ({kibana-pull}209863[#209863]). +* Makes 7.x signals/alerts compatible with 8.18 alerts UI ({kibana-pull}209936[#209936]). +* Handle empty categorization results from LLM ({kibana-pull}210420[#210420]). +* Remember page index in Rule Updates table ({kibana-pull}209537[#209537]). +* Adds concurrency limits and request throttling to prebuilt rule routes ({kibana-pull}209551[#209551]). +* Fixes package name validation on the Datastream page ({kibana-pull}210770[#210770]). +* Makes entity store description more generic ({kibana-pull}209130[#209130]). +* Deletes 'critical services' count from the Entity Analytics Dashboard header ({kibana-pull}210827[#210827]). +* Disables sorting IP ranges in value list modal ({kibana-pull}210922[#210922]). +* Updates entity store copies ({kibana-pull}210991[#210991]). +* Fixes generated name for integration title ({kibana-pull}210916[#210916]). +* Fixes formatting and sorting for custom ES|QL vars ({kibana-pull}209360[#209360]). +* Fixes WHERE autocomplete with MATCH before LIMIT ({kibana-pull}210607[#210607]). +* Updates install snippets to include all platforms ({kibana-pull}210249[#210249]). +* Updates component templates with deprecated setting ({kibana-pull}210200[#210200]). +* Hides saved query controls in AIOps ({kibana-pull}210556[#210556]). +* Fixes unattended Transforms in integration packages not automatically restarting after reauthorizing ({kibana-pull}210217[#210217]). +* Reinstates switch to support generating public URLs for embed when supported ({kibana-pull}207383[#207383]). +* Provides a fallback view to recover from Stack Alerts page filters bar errors ({kibana-pull}209559[#209559]). + [discrete] [[serverless-changelog-02102025]] === February 10, 2025 From 8aaa163091c2cccb83013f9075ba3c6bc2b38974 Mon Sep 17 00:00:00 2001 From: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com> Date: Tue, 18 Feb 2025 10:17:29 -0500 Subject: [PATCH 10/14] 9.0.0 beta Security release notes (#2960) * First draft * Removed extra coming tag --- .../release-notes-security.asciidoc | 68 ++++++++++++++++++- 1 file changed, 67 insertions(+), 1 deletion(-) diff --git a/docs/en/install-upgrade/release-notes/release-notes-security.asciidoc b/docs/en/install-upgrade/release-notes/release-notes-security.asciidoc index 9df35cc1c..1fec89084 100644 --- a/docs/en/install-upgrade/release-notes/release-notes-security.asciidoc +++ b/docs/en/install-upgrade/release-notes/release-notes-security.asciidoc @@ -4,4 +4,70 @@ {elastic-sec} ++++ -coming::[9.0.0-beta1] \ No newline at end of file +coming::[9.0.0-beta1] + +[[release-notes-header-9.0.0]] +== 9.0 + +[discrete] +[[release-notes-9.0.0-beta]] +=== 9.0.0-beta + +[discrete] +[[breaking-changes-9.0.0-beta]] +==== Breaking changes +* Refactors the Timeline HTTP API endpoints ({kibana-pull}200633[#200633]). +* Removes deprecated API endpoints for {elastic-defend} ({kibana-pull}199598[#199598]). +* Removes deprecated API endpoints for bulk CRUD actions on detection rules ({kibana-pull}197422[#197422], {kibana-pull}207906[#207906]). + +[discrete] +[[deprecations-9.0.0-beta]] +==== Deprecations +* Renames the `integration-assistant` plugin to `automatic-import` to match the associated feature ({kibana-pull}207325[#207325]). +* Removes all legacy risk engine code and features ({kibana-pull}201810[#201810]). +* Removes deprecated API endpoints for {elastic-defend} ({kibana-pull}199598[#199598]). +* Deprecates the SIEM signals migration APIs ({kibana-pull}202662[#202662]). + +[discrete] +[[known-issue-9.0.0-beta]] +==== Known issues + +// tag::known-issue[] +[discrete] +.Duplicate alerts can be produced from manually running threshold rules +[%collapsible] +==== +*Details* + +On November 12, 2024, it was discovered that manually running threshold rules could produce duplicate alerts if the date range was already covered by a scheduled rule execution. +==== +// end::known-issue[] + +// tag::known-issue[] +[discrete] +.Manually running custom query rules with suppression could suppress more alerts than expected +[%collapsible] +==== +*Details* + +On November 12, 2024, it was discovered that manually running a custom query rule with suppression could incorrectly inflate the number of suppressed alerts. +==== +// end::known-issue[] + +[discrete] +[[features-9.0.0-beta]] +==== New features +* Enables Automatic Import to accept CEL log samples ({kibana-pull}206491[#206491]). +* Applies the latest Elastic UI framework (EUI) to {elastic-sec} features ({kibana-pull}204007[#204007], {kibana-pull}204908[#204908]). +* Adds the option to view {es} queries that run during rule execution for threshold, custom query, and {ml} rules ({kibana-pull}203320[#203320]). + +[discrete] +[[enhancements-9.0.0-beta]] +==== Enhancements +* Enhances Automatic Import by including setup and troubleshooting documentation for each input type that's selected in the readme ({kibana-pull}206477[#206477]). +* Allows users to include `closed` alerts in risk score calculations ({kibana-pull}201909[#201909]). +* Adds the ability to continue to the Entity Analytics dashboard when there is no data ({kibana-pull}201363[#201363]). +* Modifies the privilege-checking behavior during rule execution. Now, only read privileges of extant indices are checked during rule execution ({kibana-pull}177658[#177658]). + +[discrete] +[[bug-fixes-9.0.0-beta]] +==== Bug fixes +* Ensures that table actions use standard colors ({kibana-pull}207743[#207743]). \ No newline at end of file From ef051c7cca95d45c5cbc6ab837f396627d245c8a Mon Sep 17 00:00:00 2001 From: florent-leborgne Date: Tue, 18 Feb 2025 16:49:51 +0100 Subject: [PATCH 11/14] Kibana release notes for 9.0.0-beta1 (#2959) Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> --- .../release-notes-kibana.asciidoc | 413 ++++++++++++++++++ 1 file changed, 413 insertions(+) diff --git a/docs/en/install-upgrade/release-notes/release-notes-kibana.asciidoc b/docs/en/install-upgrade/release-notes/release-notes-kibana.asciidoc index 8d3ce2198..e02816d5b 100644 --- a/docs/en/install-upgrade/release-notes/release-notes-kibana.asciidoc +++ b/docs/en/install-upgrade/release-notes/release-notes-kibana.asciidoc @@ -6,3 +6,416 @@ coming::[9.0.0-beta1] +For information about the {kib} 9.0.0 release, review the following information. + +[float] +[[highlights-9.0.0]] +== Highlights + +[[highlight-borealis]] +*New UI theme*. {Kib} 9.0 introduces a more modern and refined look and feel. This new theme brings improvements at multiple levels of the interface that will make navigating Kibana and visualizing dashboards easier than ever before. + + +[float] +[[breaking-changes-9.0.0]] +== Breaking changes + +Breaking changes can prevent your application from optimal operation and performance. +Before you upgrade to 9.0.0, review the breaking changes, then mitigate the impact to your application. + +//Needs to be added to upgrade notes and detailed +[discrete] +[[breaking-193792]] +.Usage restrictions on Kibana's internal APIs. +[%collapsible] +==== +*Details* + +Starting with this release, requests to internal Kibana APIs are globally restricted by default. This change is designed to provide more flexibility in making breaking changes to internal APIs while protecting external consumers from unexpected disruptions. + +Key Changes: + +* Internal API Access: External consumers no longer have access to Kibana’s internal APIs, which are now strictly reserved for internal development and subject to frequent changes. This helps ensure that external integrations only interact with stable, public APIs. +* Error Handling: When a request is made to an internal API without the proper internal identifier (header or query parameter), Kibana will respond with a 400 Bad Request error, indicating that the route exists but is not allowed under the current Kibana configuration. + +For more information, refer to ({kibana-pull}193792[#193792]). +==== + +**Alerts and cases** + +//Needs to be added to upgrade notes and detailed +[discrete] +[[breaking-198435]] +.Removed 7.x deprecated kibana.yml settings. +[%collapsible] +==== +*Details* + +The following deprecated configuration settings were removed: + +- `xpack.actions.customHostSettings.ssl.rejectUnauthorized` +- `xpack.actions.whitelistedHosts` +- `xpack.actions.rejectUnauthorized` +- `xpack.actions.proxyRejectUnauthorizedCertificates` +- `xpack.alerts.healthCheck` +- `xpack.alerts.invalidateApiKeysTask.interval` +- `xpack.alerts.invalidateApiKeysTask.removalDelay` +- `xpack.alerting.defaultRuleTaskTimeout` + +For more information, refer to ({kibana-pull}198435[#198435]). +==== + +//Needs to be added to upgrade notes and detailed +[discrete] +[[deprecation-208208]] +.Removed deprecated Cases APIs. +[%collapsible] +==== +*Details* + +The following Cases APIs were removed: + +- Get case status +- Get user actions +- Get all comments + +For more information, refer to ({kibana-pull}208208[#208208]), ({kibana-pull}208086[#208086]), and ({kibana-pull}207926[#207926]). +==== + +//Needs to be added to upgrade notes and detailed +[discrete] +[[deprecation-203148]] +.Deleted deprecated alerts routes. +[%collapsible] +==== +*Details* + +The deprecated legacy alerts routes `api/alerts/alert` were removed. For more information, refer to ({kibana-pull}203148[#203148]). +==== + +**Discover and dashboards** + +//Needs to be added to upgrade notes and detailed +[discrete] +[[breaking-203927]] +.Disabled search sessions by default. +[%collapsible] +==== +*Details* + +Search sessions are now disabled by default. For more information, refer to ({kibana-pull}203927[#203927]). +==== + +//Already added to upgrade notes +[discrete] +[[breaking-202863]] +.Saved query privileges have been reworked. +[%collapsible] +==== +*Details* + +Saved query privileges have been reworked to rely solely on a single global `savedQueryManagement` privilege, and eliminate app-specific overrides (e.g. implicit access with `all` privilege for Discover, Dashboard, Maps, and Visualize apps). This change simplifies the security model and ensures consistency in the saved query management UI across Kibana, but results in different handling of saved query privileges for new user roles, and minor breaking changes to the existing management UX. +For more information, refer to {kibana-pull}202863[#202863]. + +*Impact* + +The `savedQueryManagement` feature privilege now globally controls access to saved query management for all new user roles. Regardless of privileges for Discover, Dashboard, Maps, or Visualize, new user roles follow this behaviour: + +* If `savedQueryManagement` is `none`, the user cannot see or access the saved query management UI or APIs. +* If `savedQueryManagement` is `read`, the user can load queries from the UI and access read APIs, but cannot save queries from the UI or make changes to queries through APIs. +* If `savedQueryManagement` is `all`, the user can both load and save queries from the UI and through APIs. + +*Action* + +Existing user roles that were previously implicitly granted access to saved queries through the dashboard, discover, visualize, or maps feature privileges will retain that access to prevent breaking changes. While no action is required for existing roles, it’s still advisable to audit relevant roles and re-save them to migrate to the latest privileges model. For new roles, ensure that the savedQueryManagement privilege is set as needed. +==== + +//Needs to be added to upgrade notes and detailed +[discrete] +[[breaking-202679]] +.Removed `discover:searchFieldsFromSource` setting. +[%collapsible] +==== +*Details* + +For more information, refer to ({kibana-pull}202679[#202679]). +==== + +//Needs to be added to upgrade notes and detailed +[discrete] +[[breaking-201254]] +.Removed the legacy table in Discover. +[%collapsible] +==== +*Details* + +It's no longer possible to use the legacy documents table in Discover. To that effect, the `doc_table:legacy` and `truncate:maxHeight` deprecated advanced settings have been removed. For more information, refer to ({kibana-pull}201254[#201254]). +==== + +//Already added to upgrade notes +[discrete] +[[breaking-202250]] +.Scripted field creation has been disabled in the Data Views management page. +[%collapsible] +==== +*Details* + +The ability to create new scripted fields has been removed from the *Data Views* management page in 9.0. Existing scripted fields can still be edited or deleted, and the creation UI can be accessed by navigating directly to `/app/management/kibana/dataViews/dataView/{dataViewId}/create-field`, but we recommend migrating to runtime fields or ES|QL queries instead to prepare for removal. +For more information, refer to {kibana-pull}202250[#202250]. + +*Impact* + +It will no longer be possible to create new scripted fields directly from the *Data Views* management page. + +*Action* + +Migrate to runtime fields or ES|QL instead of creating new scripted fields. Existing scripted fields can still be edited or deleted. +==== + + + +**Elastic Observability solution** + +//Needs to be added to upgrade notes and detailed +[discrete] +[[breaking-202278]] +.Profiling now defaults to 19Hz sampling frequency. +[%collapsible] +==== +*Details* + +For more information, refer to ({kibana-pull}202278[#202278]). +==== + +//Needs to be added to upgrade notes and detailed +[discrete] +[[deprecation-203996]] +.Disabled log stream and settings pages. +[%collapsible] +==== +*Details* + +Logs Stream and the logs settings page in Observability are removed. Use the Discover application, which now offers a contextual experience for logs, to explore your logs. The logs stream panel in dashboards is removed, use Discover sessions instead. + +For more information, refer to ({kibana-pull}203996[#203996]). +==== + +//Needs to be added to upgrade notes and detailed +[discrete] +[[deprecation-203685]] +.Removed Logs Explorer. +[%collapsible] +==== +*Details* + +Logs Explorer has been removed. Instead, you can use Discover, that was improved to provide an optimal logs exploration experience. For more information, refer to ({kibana-pull}203685[#203685]). +==== + +**Elastic Security solution** + +For the Elastic Security 9.0.0 release information, refer to <>. + +**Data ingestion and Fleet** + +//Needs to be added to upgrade notes and detailed +[discrete] +[[breaking-198799]] +.Removed deprecated settings API endpoints in Fleet. +[%collapsible] +==== +*Details* + + +* `GET/DELETE/POST enrollment-api-keys`: removed in favor of `GET/DELETE/POST enrollment_api_keys` +* Removed `list` property from `GET enrollment_api_keys` response in favor of `items` +* `GET/POST /settings`: `fleet_server_hosts` was removed from the response and body + +For more information, refer to ({kibana-pull}198799[#198799]). +==== + +//Needs to be added to upgrade notes and detailed +[discrete] +[[breaking-198313]] +.Removed deprecated Fleet APIs for agents endpoints. +[%collapsible] +==== +*Details* + + +Removed API endpoints: + +* `POST /service-tokens` in favor of `POST /service_tokens` +* `GET /agent-status` in favor `GET /agent_status` +* `PUT /agents/:agentid/reassign` in favor of `POST /agents/:agentid/reassign` + +Removed deprecated parameters or responses: + +* Removed `total` from `GET /agent_status` response +* Removed `list` from `GET /agents` response + +For more information, refer to ({kibana-pull}198313[#198313]). +==== + +//Needs to be added to upgrade notes and detailed +[discrete] +[[breaking-198434]] +.Removed deprecated `epm` Fleet APIs. +[%collapsible] +==== +*Details* + + +* Removed `GET/POST/DELETE /epm/packages/:pkgkey` APIs in favor of `GET/POST/DELETE /epm/packages/:pkgName/:pkgVersion` +* Removed `experimental` query parameter in `GET /epm/packages` and `GET /epm/categories` +* Removed `response` in response in `* /epm/packages*` and `GET /epm/categories` +* Removed `savedObject` in `/epm/packages` response in favor of `installationInfo` + +For more information, refer to ({kibana-pull}198434[#198434]). +==== + +//Needs to be added to upgrade notes and detailed +[discrete] +[[breaking-199226]] +.Removed deprecated `topics` property for kafka output in favor of the `topic` property. +[%collapsible] +==== +*Details* + +Removed deprecated property `topics` from output APIs in response and requests (`(GET|POST|PUT) /api/fleet/outputs`) in favor of the `topic` property. For more information, refer to ({kibana-pull}199226[#199226]). +==== + +//Needs to be added to upgrade notes and detailed +[discrete] +[[breaking-196887]] +.Limit pagination size to 100 when retrieving full policy or `withAgentCount` in Fleet. +[%collapsible] +==== +*Details* + +In addition to the new pagination limit size of 100, retrieving agent policies without agent count is now the new default behavior, and a new query parameter `withAgentCount` was added to retrieve the agent count. + +For more information, refer to ({kibana-pull}196887[#196887]). +==== + +**Reporting** + +//Needs to be added to upgrade notes and detailed +[discrete] +[[breaking-200834]] +.Now using Kibana feature privileges only to control access to reporting features. +[%collapsible] +==== +*Details* + +The default system of granting users the privilege to generate reports has changed. Rather than assigning users the `reporting_user` role, administrators should create a custom role that grants report-creation privileges using Kibana application privileges. For more information, refer to ({kibana-pull}200834[#200834]). +==== + + +//Needs to be added to upgrade notes and detailed +[discrete] +[[breaking-199033]] +.Removed the "Download CSV" export type functionality. +[%collapsible] +==== +*Details* + +The functionality that allowed to download a CSV export from a dashboard's saved search panel without creating a report has been removed. To export CSV data from a dashboard panel, you may use the action menu of a saved search panel in a dashboard to generate a CSV report, and download the report from a toast popup when the report has finished generating. For more information, refer to ({kibana-pull}199033[#199033]). +==== + + +**Kibana security** + +//Needs to be added to upgrade notes and detailed +[discrete] +[[deprecation-203856]] +.Removed `TLSv1.1` from the default set of supported protocols. +[%collapsible] +==== +*Details* + +For more information, refer to ({kibana-pull}203856[#203856]). +==== + +//Needs to be added to upgrade notes and detailed +[discrete] +[[deprecation-207325]] +.Renamed `integration-assistant` plugin to `automatic-import`. +[%collapsible] +==== +*Details* + +For more information, refer to ({kibana-pull}207325[#207325]). +==== + + + +[float] +[[deprecations-9.0.0]] +== Deprecations + +The following functionality is deprecated in 9.0.0, and will be removed in 10.0.0. +Deprecated functionality does not have an immediate impact on your application, but we strongly recommend +you make the necessary updates after you upgrade to 9.0.0. + + +[discrete] +[[deprecation-201313]] +.Removed ephemeral tasks from task manager, action, and alerting plugins. +[%collapsible] +==== +*Details* + + +Deprecates the following configuration settings: + +* `xpack.task_manager.ephemeral_tasks.enabled` +* `xpack.task_manager.ephemeral_tasks.request_capacity` +* `xpack.alerting.maxEphemeralActionsPerAlert` + +No action is required on the user's end. These settings will no longer have any effect as ephemeral tasks are now removed. + +For more information, refer to ({kibana-pull}201313[#201313]). +==== + + +[discrete] +[[deprecation-197802]] +.Removed `visualization:colorMapping` advanced setting. +[%collapsible] +==== +*Details* + +The `visualization:colorMapping` advanced setting for TSVB and Visualize charts has been removed. You can switch to Lens charts, which offer a more advanced, per-chart color mapping feature with enhanced configuration options. For more details, refer to link:https://github.com/elastic/kibana/pull/162389[#162389]. +==== + + +[float] +[[features-9.0.0]] +== Features +{kib} 9.0.0 adds the following new and notable features. + +Data ingestion and Fleet:: +* New setting allowing automatic deletion of unenrolled agents in Fleet settings ({kibana-pull}195544[#195544]). +Elastic Security solution:: +For the Elastic Security 9.0.0 release information, refer to <>. +Kibana security:: +* New interface for Automatic Import CEL generation flow ({kibana-pull}206491[#206491]). + +//For more information about the features introduced in 9.0.0, refer to <>. + +[[enhancements-and-bug-fixes-v9.0.0]] +== Enhancements and bug fixes + +//For detailed information about the 9.0.0 release, review the enhancements and bug fixes. + +[float] +[[enhancement-v9.0.0]] +=== Enhancements +//Dashboards & Visualizations:: +Data ingestion and Fleet:: +* Improves filtering and visibility of `Uninstalled` and `Orphaned` agents in Fleet, by differentiating them from `Offline` agents ({kibana-pull}205815[#205815]). +* Introduces air-gapped configuration for bundled packages ({kibana-pull}202435[#202435]). +* Updates removed parameters of the Fleet -> Logstash output configurations ({kibana-pull}210115[#210115]). +* Updates max supported package version ({kibana-pull}196675[#196675]). +//* Remove old bundled.yaml from oas, fixed tags ({kibana-pull}194788[#194788]). +Elastic Security solution:: +For the Elastic Security 9.0.0 release information, refer to <>. +Kibana security:: +* Updates `js-yaml` to `4.1.0` ({kibana-pull}190678[#190678]). +Machine Learning:: +* Removes use of `ignore_throttled` ({kibana-pull}199107[#199107]). +Platform:: +* Adds warning header to deprecated API endpoints ({kibana-pull}205926[#205926]). +* Sets HTTP2 as default if SSL is enabled and adds deprecation log if SSL is not enabled or protocol is set to HTTP1 ({kibana-pull}204384[#204384]). + +[float] +[[fixes-v9.0.0]] +=== Bug fixes +Dashboards & Visualizations:: +* Fixes an issue in Lens where colors behind text were not correctly assigned, such as in `Pie`, `Treemap` and `Mosaic` charts. +//* Fixes an issue with `Amsterdam` theme where charts render with the incorrect background color ({kibana-pull}209595[#209595]). +* Fixes an issue where changing the *Ignore timeout results* control setting wasn't taken into account ({kibana-pull}208611[#208611]). +* Force returns 0 on empty buckets on count if `null` flag is disabled ({kibana-pull}207308[#207308]). +* Fixes infinite loading time for some charts due to search context reload ({kibana-pull}203150[#203150]). +Data ingestion and Fleet:: +* Fixes a validation error happening on multi-text input fields ({kibana-pull}205768[#205768]). +Elastic Observability solution:: +* Fixes chat on the Alerts page ({kibana-pull}197126[#197126]). +* Fixes an error that could prevent the Observability Infrastructure Inventory view from loading after an upgrade due to missing versioning on inventory_view_saved_object ({kibana-pull}207007[#207007]). +Elastic Security solution:: +For the Elastic Security 9.0.0 release information, refer to <>. +Platform:: +* Fixes several interface inconsistencies on the Space creation and settings pages ({kibana-pull}197303[#197303]). \ No newline at end of file From 5a56dfb23480a5d22187e3d444408b153251566f Mon Sep 17 00:00:00 2001 From: Lisa Cawley Date: Tue, 18 Feb 2025 08:35:06 -0800 Subject: [PATCH 12/14] Add Logstash release notes (#2964) --- docs/en/install-upgrade/index.asciidoc | 28 ++--- .../release-notes-logstash.asciidoc | 109 +++++++++++++++++- 2 files changed, 122 insertions(+), 15 deletions(-) diff --git a/docs/en/install-upgrade/index.asciidoc b/docs/en/install-upgrade/index.asciidoc index 2e4c3bdc3..fa7bd3628 100644 --- a/docs/en/install-upgrade/index.asciidoc +++ b/docs/en/install-upgrade/index.asciidoc @@ -14,6 +14,20 @@ include::installing-stack-demo-secure.asciidoc[] include::air-gapped-install.asciidoc[] +include::serverless-changelog.asciidoc[] + +include::breaking.asciidoc[] + +include::release-notes/release-notes.asciidoc[leveloffset=+1] + +include::release-notes/release-notes-elasticsearch.asciidoc[leveloffset=+2] + +include::release-notes/release-notes-kibana.asciidoc[leveloffset=+2] + +include::release-notes/release-notes-logstash.asciidoc[leveloffset=+2] + +include::release-notes/release-notes-security.asciidoc[leveloffset=+2] + include::upgrading-stack.asciidoc[] include::upgrade-orchestrator.asciidoc[] @@ -40,18 +54,4 @@ include::upgrading-kibana.asciidoc[] // include::upgrading-agent.asciidoc[] -include::serverless-changelog.asciidoc[] - -include::breaking.asciidoc[] - -include::release-notes/release-notes.asciidoc[leveloffset=+1] - -include::release-notes/release-notes-elasticsearch.asciidoc[leveloffset=+2] - -include::release-notes/release-notes-kibana.asciidoc[leveloffset=+2] - -include::release-notes/release-notes-logstash.asciidoc[leveloffset=+2] - -include::release-notes/release-notes-security.asciidoc[leveloffset=+2] - include::redirects.asciidoc[] diff --git a/docs/en/install-upgrade/release-notes/release-notes-logstash.asciidoc b/docs/en/install-upgrade/release-notes/release-notes-logstash.asciidoc index 4f3b59531..7e99bf088 100644 --- a/docs/en/install-upgrade/release-notes/release-notes-logstash.asciidoc +++ b/docs/en/install-upgrade/release-notes/release-notes-logstash.asciidoc @@ -4,5 +4,112 @@ {ls} ++++ -coming::[9.0.0-beta1] +== Breaking changes +[[pipeline-buffer-type]] +=== Pipeline buffer type changed to 'heap' + +Set `pipeline.buffer.type` to `direct` to continue using direct memory with {agent}, {beats}, TCP, and HTTP input plugins https://github.com/elastic/logstash/pull/16500[#16500] + +[[removed-params]] +=== Removed deprecated params + +`http.*` params replaced by `api.*` are removed https://github.com/elastic/logstash/pull/16552[#16552] + +`event_api.tags.illegal` no longer exists. +Instead, {ls} generates `_tagsparsefailure` in the event `tags` and the illegal value is written to the `_tags` field https://github.com/elastic/logstash/pull/16461[#16461] + +[[removed-modules]] +=== Removed {ls} modules + +Removed netflow, fb_apache and azure https://github.com/elastic/logstash/pull/16514[#16514] + +Removed Arcsight module and the modules framework https://github.com/elastic/logstash/pull/16794[#16794] + +Removed ingest-converter https://github.com/elastic/logstash/pull/16453[#16453] + + +[[jdk-11-support-drop]] +=== JDK 11 support drop + +Starting with {ls} 9.0, we no longer support Java 11 https://github.com/elastic/logstash/pull/16443[#16443] + +[[docker-base-image-change]] +=== Docker base image change + +{ls} on Docker, Ubuntu base image changed to UBI https://github.com/elastic/logstash/pull/16599[#16599] + +[[allow-superuser]] +=== {ls} does not run with superuser by default + +Starting with 9.0, set `allow_superuser` to `true` if you prefer running {ls} as a superuser https://github.com/elastic/logstash/pull/16558[#16558] + +[[allow-legacy-monitoring]] +=== {ls} introduces new setting to allow legacy internal monitoring + +Starting from 9.0, set `xpack.monitoring.allow_legacy_collection` to `true` to explicitly permit legacy monitoring https://github.com/elastic/logstash/pull/16586[#16586] + +[[avoid-collision-on-json-fileds]] +=== {ls} avoids JSON log lines collision + +`log.format.json.fix_duplicate_message_fields` config is enabled by default to avoid collision on `message` field in log lines when `log.format` is JSON https://github.com/elastic/logstash/pull/16578[#16578] + +== Plugin releases + +*elastic_integration Filter - 9.0.0* + +* 9.0 prerelease compatible plugin version https://github.com/elastic/logstash-filter-elastic_integration/pull/265[#265] + +*Elasticsearch Filter - 4.1.0* + +* Remove deprecated SSL settings https://github.com/logstash-plugins/logstash-filter-elasticsearch/pull/183[#183] + +*Http Filter - 2.0.0* + +* Remove deprecated SSL settings https://github.com/logstash-plugins/logstash-filter-http/pull/54[#54] + +*Beats Input - 7.0.1* + +* Remove deprecated SSL settings https://github.com/logstash-plugins/logstash-input-beats/pull/508[#508] + +*Elastic_serverless_forwarder Input - 2.0.0* + +* Remove deprecated SSL settings https://github.com/logstash-plugins/logstash-input-elastic_serverless_forwarder/pull/11[#11] + +* Promote from technical preview to GA https://github.com/logstash-plugins/logstash-input-elastic_serverless_forwarder/pull/10[#10] + +*Elasticsearch Input - 5.0.0* + +* Remove deprecated SSL settings https://github.com/logstash-plugins/logstash-input-elasticsearch/pull/213[#213] + +*Http Input - 4.1.0* + +* Remove deprecated SSL settings https://github.com/logstash-plugins/logstash-input-http/pull/182[#182] + +*Http_poller Input - 6.0.0* + +* Remove deprecated SSL settings https://github.com/logstash-plugins/logstash-input-http_poller/pull/149[#149] + +*Tcp Input - 7.0.0* + +* Remove deprecated SSL settings https://github.com/logstash-plugins/logstash-input-tcp/pull/228[#228] + +*Kafka Integration - 11.6.0* + +* Support additional `oauth` and `sasl` configuration options for configuring kafka client https://github.com/logstash-plugins/logstash-integration-kafka/pull/189[#189] + +*Snmp Integration - 4.0.6* + +* [DOC] Fix typo in snmptrap migration section https://github.com/logstash-plugins/logstash-integration-snmp/pull/74[#74] + +*Elasticsearch Output - 12.0.2* + +* Remove deprecated SSL settings https://github.com/logstash-plugins/logstash-output-elasticsearch/pull/1197[#1197] + +*Http Output - 6.0.0* + +* Remove deprecated SSL settings https://github.com/logstash-plugins/logstash-output-http/pull/147[#147] + +*Tcp Output - 7.0.0* + +* Remove deprecated SSL settings https://github.com/logstash-plugins/logstash-output-tcp/pull/58[#58] From 6b154336ac00c52032f3a9914e67e93e1a9df48d Mon Sep 17 00:00:00 2001 From: Lisa Cawley Date: Tue, 18 Feb 2025 10:05:30 -0800 Subject: [PATCH 13/14] Remove coming tags, fix security release note levels (#2967) --- .../release-notes-kibana.asciidoc | 2 -- .../release-notes-security.asciidoc | 21 ++++++------------- 2 files changed, 6 insertions(+), 17 deletions(-) diff --git a/docs/en/install-upgrade/release-notes/release-notes-kibana.asciidoc b/docs/en/install-upgrade/release-notes/release-notes-kibana.asciidoc index e02816d5b..837f5e746 100644 --- a/docs/en/install-upgrade/release-notes/release-notes-kibana.asciidoc +++ b/docs/en/install-upgrade/release-notes/release-notes-kibana.asciidoc @@ -4,8 +4,6 @@ {kib} ++++ -coming::[9.0.0-beta1] - For information about the {kib} 9.0.0 release, review the following information. [float] diff --git a/docs/en/install-upgrade/release-notes/release-notes-security.asciidoc b/docs/en/install-upgrade/release-notes/release-notes-security.asciidoc index 1fec89084..cc42b8be6 100644 --- a/docs/en/install-upgrade/release-notes/release-notes-security.asciidoc +++ b/docs/en/install-upgrade/release-notes/release-notes-security.asciidoc @@ -4,25 +4,16 @@ {elastic-sec} ++++ -coming::[9.0.0-beta1] - -[[release-notes-header-9.0.0]] -== 9.0 - -[discrete] -[[release-notes-9.0.0-beta]] -=== 9.0.0-beta - [discrete] [[breaking-changes-9.0.0-beta]] -==== Breaking changes +== Breaking changes * Refactors the Timeline HTTP API endpoints ({kibana-pull}200633[#200633]). * Removes deprecated API endpoints for {elastic-defend} ({kibana-pull}199598[#199598]). * Removes deprecated API endpoints for bulk CRUD actions on detection rules ({kibana-pull}197422[#197422], {kibana-pull}207906[#207906]). [discrete] [[deprecations-9.0.0-beta]] -==== Deprecations +== Deprecations * Renames the `integration-assistant` plugin to `automatic-import` to match the associated feature ({kibana-pull}207325[#207325]). * Removes all legacy risk engine code and features ({kibana-pull}201810[#201810]). * Removes deprecated API endpoints for {elastic-defend} ({kibana-pull}199598[#199598]). @@ -30,7 +21,7 @@ coming::[9.0.0-beta1] [discrete] [[known-issue-9.0.0-beta]] -==== Known issues +== Known issues // tag::known-issue[] [discrete] @@ -54,14 +45,14 @@ On November 12, 2024, it was discovered that manually running a custom query rul [discrete] [[features-9.0.0-beta]] -==== New features +== New features * Enables Automatic Import to accept CEL log samples ({kibana-pull}206491[#206491]). * Applies the latest Elastic UI framework (EUI) to {elastic-sec} features ({kibana-pull}204007[#204007], {kibana-pull}204908[#204908]). * Adds the option to view {es} queries that run during rule execution for threshold, custom query, and {ml} rules ({kibana-pull}203320[#203320]). [discrete] [[enhancements-9.0.0-beta]] -==== Enhancements +== Enhancements * Enhances Automatic Import by including setup and troubleshooting documentation for each input type that's selected in the readme ({kibana-pull}206477[#206477]). * Allows users to include `closed` alerts in risk score calculations ({kibana-pull}201909[#201909]). * Adds the ability to continue to the Entity Analytics dashboard when there is no data ({kibana-pull}201363[#201363]). @@ -69,5 +60,5 @@ On November 12, 2024, it was discovered that manually running a custom query rul [discrete] [[bug-fixes-9.0.0-beta]] -==== Bug fixes +== Bug fixes * Ensures that table actions use standard colors ({kibana-pull}207743[#207743]). \ No newline at end of file From 47e45d918963940cfd5f91444e45cae1e3a003bd Mon Sep 17 00:00:00 2001 From: David Kilfoyle Date: Tue, 18 Feb 2025 14:04:25 -0500 Subject: [PATCH 14/14] Add Fleet & Agent 9.0.0-beta1 Release Notes --- docs/en/install-upgrade/index.asciidoc | 2 + .../release-notes-fleet-agent.asciidoc | 147 ++++++++++++++++++ .../release-notes/release-notes.asciidoc | 1 + 3 files changed, 150 insertions(+) create mode 100644 docs/en/install-upgrade/release-notes/release-notes-fleet-agent.asciidoc diff --git a/docs/en/install-upgrade/index.asciidoc b/docs/en/install-upgrade/index.asciidoc index fa7bd3628..5b8bc49c7 100644 --- a/docs/en/install-upgrade/index.asciidoc +++ b/docs/en/install-upgrade/index.asciidoc @@ -22,6 +22,8 @@ include::release-notes/release-notes.asciidoc[leveloffset=+1] include::release-notes/release-notes-elasticsearch.asciidoc[leveloffset=+2] +include::release-notes/release-notes-fleet-agent.asciidoc[leveloffset=+2] + include::release-notes/release-notes-kibana.asciidoc[leveloffset=+2] include::release-notes/release-notes-logstash.asciidoc[leveloffset=+2] diff --git a/docs/en/install-upgrade/release-notes/release-notes-fleet-agent.asciidoc b/docs/en/install-upgrade/release-notes/release-notes-fleet-agent.asciidoc new file mode 100644 index 000000000..3fb7aff19 --- /dev/null +++ b/docs/en/install-upgrade/release-notes/release-notes-fleet-agent.asciidoc @@ -0,0 +1,147 @@ +// 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-fleet-agent-9.0.0-beta1]] += {fleet} and {agent} Release notes +++++ +{fleet} and {agent} +++++ + +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] + +// begin 9.0.0-beta1 relnotes + +[[release-notes-9.0.0-beta1]] +== {fleet} and {agent} 9.0.0-beta1 + +Review important information about the {fleet} and {agent} 9.0.0-beta1 release. + +[discrete] +[[security-updates-9.0.0-beta1]] +=== Security updates + +{agent}:: +* Update Go version to 1.22.10. {agent-pull}6236[#6236] + +[discrete] +[[breaking-changes-9.0.0-beta1]] +=== 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. + +{fleet}:: + +[discrete] +[[breaking-198434-fleet]] +.Removed deprecated `epm` Fleet APIs. +[%collapsible] +==== +*Details* + +Removed `GET/POST/DELETE /epm/packages/:pkgkey` APIs in favor of the `GET/POST/DELETE /epm/packages/:pkgName/:pkgVersion`: + +** Removed `experimental` query parameter in `GET /epm/packages` and `GET /epm/categories` +** Removed `response` in response in `* /epm/packages*` and `GET /epm/categories` +** Removed `savedObject` in `/epm/packages` response in favor of `installationInfo` + +For more information, refer to ({kibana-pull}198434[#198434]). +==== + +[discrete] +[[breaking-198313-fleet]] +.Removed deprecated Fleet APIs for agents endpoints. +[%collapsible] +==== +*Details* + +Removed the following API endpoints: + +* `POST /service-tokens` in favor of `POST /service_tokens` +* `GET /agent-status` in favor `GET /agent_status` +* `PUT /agents/:agentid/reassign` in favor of `POST /agents/:agentid/reassign` + +Removed deprecated parameters or responses: + +* Removed `total` from `GET /agent_status` response +* Removed `list` from `GET /agents` response + +For more information, refer to ({kibana-pull}198313[#198313]). +==== + +{agent}:: +* Support for `cloud-defend` (Defend for Containers) has been removed in this release. The package has been removed from the {agent} packaging scripts and template Kubernetes files. {agent-pull}5481[#5481] +* The default values for `username` and `password` have been removed for when {agent} is running in container mode. The {es} `api_key` can now be set in that mode using the `ELASTICSEARCH_API_KEY` environment variable. {agent-pull}5536[#5536] +* The default Ubuntu-based Docker images used for {agent} have been changed to UBI-minimal-based images, to reduce the overall footprint of the agent Docker images and to improve compliance with enterprise standards. {agent-pull}6427[#6427] +* The deprecated `--path.install` flag declaration has been removed from the {agent} `paths` command and its use removed from the `container` and `enroll` commands. {agent-pull}6461[#6461] {agent-issue}2489[#2489] +* The default {agent} installation and ugprade have been changed to include only the `agentbeat`, `endpoint-security` and `pf-host-agent` components. Additional components can be included using flags. {agent-pull}6542[#6542] + +[discrete] +[[new-features-9.0.0-beta1]] +=== New features + +The 9.0.0-beta1 release Added the following new and notable features. + +{fleet}:: +* Add new setting allowing automatic deletion of unenrolled agents in {fleet} settings. ({kibana-pull}195544[#195544]) + +{agent}:: +* Add the Azure Asset Inventory definition to Cloudbeat. {agent-pull}5323[#5323] +* Add a new Kubernetes deployment of the Elastic Distribution of OTel Collector named "gateway" to the Helm kube-stack deployment. {agent-pull}6444[#6444] +* Add the filesource providert to composable inputs. The provider watches for changes of the files and updates the values of the variables when the content of the file changes. {agent-pull}6587[#6587] {agent-issue}6362[#6362] +* Add the jmxreceiver to the Elastic Distribution of OTel Collector. {agent-pull}6601[#6601] +* Add support for context variables in outputs as well as a default provider prefix. {agent-pull}6602[#6602] {agent-issue}6376[#6376] +* Add the Nginx receiver and Redis receiver OTel components. {agent-pull}6627[#6627] +* Add new `--id` (`ELASTIC_AGENT_ID` environment variable for container) and `--replace-token` (`FLEET_REPLACE_TOKEN` environment variable for container) enrollment options. {agent-pull}6498[#6498] + +[discrete] +[[enhancements-9.0.0-beta1]] +=== Enhancements + +{fleet}:: +* Improve filtering and visibility of `Uninstalled` and `Orphaned` agents in {fleet}, by differentiating them from `Offline` agents. ({kibana-pull}205815[#205815]) +* Introduce air-gapped configuration for bundled packages. ({kibana-pull}202435[#202435]) +* Update removed parameters of the {fleet} -> {ls} output configurations. ({kibana-pull}210115[#210115]) +* Update the maximum supported package version. ({kibana-pull}196675[#196675]) + +{fleet-server}:: +* Replace the use of `context.TODO` and `context.Background` in logger function calls for most use cases. {fleet-server-pull}4168[#4168] {fleet-server-issue}3087[#3087] +* Refactor the API constructor to use functional opts instead of a long list of pointers. {fleet-server-pull}4169[#4169] {fleet-server-issue}3823[#3823] +* Remove the deprecated `policy_throttle` configuration setting in favour of the newer `policy-limit`. {fleet-server-pull}4288[#4288] +* Add the ability for {agent} to enroll using a specific ID. {fleet-server-pull}4290[#4290] {fleet-server-issue}4226[#4226] + +{agent}:: +* Add the Filebeat receiver into {agent}. {agent-pull}5833[#5833] +* Update OTel components to v0.119.0. {agent-pull}6713[#6713] + +[discrete] +[[bug-fixes-9.0.0-beta1]] +=== Bug fixes + +{fleet}:: +* Fix a validation error that occurs on multi-text input fields. ({kibana-pull}205768[#205768]) + +{fleet-server}:: +* Adding a context timeout to the bulker flush so it times out if it takes more time than the deadline. {fleet-server-pull}3986[#3986] +* Remove a race condition that may occur when remote {es} outputs are used. {fleet-server-pull}4171[#4171] +* Use the `chi/middleware.Throttle` package to track in-flight requests and return a 429 response when the limit is reached. {fleet-server-pull}4402[#4402] {fleet-server-issue}4400[#4400] + +{agent}:: +* Fix logical race conditions in the `kubernetes_secrets` provider. {agent-pull}6623[#6623] +* Resolve the proxy to inject into agent component configurations using the Go `http` package. {agent-pull}6675[#6675] {agent-issue}6209[#6209] + +// end 9.0.0-beta1 relnotes \ No newline at end of file diff --git a/docs/en/install-upgrade/release-notes/release-notes.asciidoc b/docs/en/install-upgrade/release-notes/release-notes.asciidoc index e015e2b52..17dd467c2 100644 --- a/docs/en/install-upgrade/release-notes/release-notes.asciidoc +++ b/docs/en/install-upgrade/release-notes/release-notes.asciidoc @@ -5,6 +5,7 @@ This section summarizes the changes in the {stack} releases. * <> * <> +* <> * <> * <>