mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 01:38:56 -04:00
[Docs] Reset release files for 9.0 (#199519)
This PR resets the release notes, upgrade notes, and what's new for 9.0. It also cleans up a few references/files that were focusing on migration to 8.0 Some more PRs will happen to prepare the rest of the docs for v9 Closes: https://github.com/elastic/platform-docs-team/issues/564
This commit is contained in:
florent-leborgne
GitHub
parent
b1eae2deed
commit
e42569dc04
9 changed files with 71 additions and 11238 deletions
File diff suppressed because it is too large
Load diff
|
|
@ -19,7 +19,7 @@ We would recommend waiting until later in `7.x` to upgrade your plugins if possi
|
|||
If you would like to keep up with progress on the visualizations plugin in the meantime,
|
||||
here are a few resources:
|
||||
|
||||
* The <<breaking-changes-8.0.0,breaking changes>> documentation, where we try to capture any changes to the APIs as they occur across minors.
|
||||
* The <<breaking-changes-9.0.0,breaking changes>> documentation, where we try to capture any changes to the APIs as they occur across minors.
|
||||
* link:https://github.com/elastic/kibana/issues/44121[Meta issue] which is tracking the move of the plugin to the new {kib} platform
|
||||
* Our link:https://www.elastic.co/blog/join-our-elastic-stack-workspace-on-slack[Elastic Stack workspace on Slack].
|
||||
* The {kib-repo}blob/{branch}/src/plugins/visualizations[source code], which will continue to be
|
||||
|
|
|
|||
|
|
@ -6,9 +6,9 @@
|
|||
This section discusses the changes that you need to be aware of when migrating
|
||||
your application from one version of Kibana to another.
|
||||
|
||||
* <<breaking-changes-8.0>>
|
||||
* <<breaking-changes-9.0>>
|
||||
|
||||
See also <<whats-new>> and <<release-notes>>.
|
||||
--
|
||||
|
||||
include::migration/migrate_8_0.asciidoc[]
|
||||
include::migration/migrate_9_0.asciidoc[]
|
||||
|
|
@ -1,402 +0,0 @@
|
|||
[[breaking-changes-8.0]]
|
||||
== Breaking changes in 8.0
|
||||
++++
|
||||
<titleabbrev>8.0</titleabbrev>
|
||||
++++
|
||||
|
||||
This section discusses the changes that you need to be aware of when migrating
|
||||
your application to Kibana 8.0.
|
||||
|
||||
See also <<whats-new>> and <<release-notes>>.
|
||||
|
||||
* <<breaking_80_index_pattern_changes>>
|
||||
* <<breaking_80_setting_changes>>
|
||||
|
||||
[float]
|
||||
[[breaking_80_index_pattern_changes]]
|
||||
=== Index pattern changes
|
||||
|
||||
[float]
|
||||
==== Removed support for time-based internal index patterns
|
||||
*Details:* Time-based interval index patterns were deprecated in 5.x. In 6.x,
|
||||
you could no longer create time-based interval index patterns, but they continued
|
||||
to function as expected. Support for these index patterns has been removed in 8.0.
|
||||
|
||||
*Impact:* You must migrate your time_based index patterns to a wildcard pattern,
|
||||
for example, `logstash-*`.
|
||||
|
||||
[float]
|
||||
[[breaking_80_setting_changes]]
|
||||
=== Settings changes
|
||||
|
||||
[float]
|
||||
==== Multitenancy by changing `kibana.index` is no longer supported
|
||||
*Details:* `kibana.index`, `xpack.reporting.index` and `xpack.task_manager.index` can no longer be specified.
|
||||
|
||||
*Impact:* Users who relied on changing these settings to achieve multitenancy should use *Spaces*, cross-cluster replication, or cross-cluster search instead. To migrate to *Spaces*, users are encouraged to use saved object management to export their saved objects from a tenant into the default tenant in a space. Improvements are planned to improve on this workflow. See https://github.com/elastic/kibana/issues/82020 for more details.
|
||||
|
||||
[float]
|
||||
==== Disabling most plugins with the `{plugin_name}.enabled` setting is no longer supported
|
||||
*Details:* The ability for most plugins to be disabled using the `{plugin_name}.enabled` config option has been removed.
|
||||
|
||||
*Impact:* Some plugins, such as `telemetry`, `newsfeed`, `reporting`, and the various `vis_type` plugins will continue to support this setting, however the rest of the plugins that ship with Kibana will not. By default, any newly created plugins will not support this configuration unless it is explicitly added to the plugin's `configSchema`.
|
||||
|
||||
If you are currently using one of these settings in your Kibana config, please remove it before upgrading to 8.0. If you were using these settings to control user access to certain Kibana applications, we recommend leveraging Feature Controls instead.
|
||||
|
||||
[float]
|
||||
==== Legacy browsers are now rejected by default
|
||||
*Details:* `csp.strict` is now enabled by default, so Kibana will fail to load for older, legacy browsers that do not enforce basic Content Security Policy protections - notably Internet Explorer 11.
|
||||
|
||||
*Impact:* To allow Kibana to function for these legacy browsers, set `csp.strict: false`. Since this is about enforcing a security protocol, we *strongly discourage* disabling `csp.strict` unless it is critical that you support Internet Explorer 11.
|
||||
|
||||
[float]
|
||||
==== Configuring content security policy rules is no longer supported
|
||||
*Details:* Configuring `csp.rules` is removed in favor of per-directive specific configuration. Configuring the default `csp.script_src`, `csp.workers_src` and `csp.style_src` values is not required.
|
||||
|
||||
*Impact:* Configure per-directive sources instead. See https://github.com/elastic/kibana/pull/102059 for more details.
|
||||
|
||||
[float]
|
||||
==== Default logging timezone is now the system's timezone
|
||||
*Details:* In prior releases the timezone used in logs defaulted to UTC. We now use the host machine's timezone by default.
|
||||
|
||||
*Impact:* To restore the previous behavior, in kibana.yml use the pattern layout, with a {kibana-ref}/logging-configuration.html#date-format[date modifier]:
|
||||
[source,yaml]
|
||||
-------------------
|
||||
logging:
|
||||
appenders:
|
||||
custom:
|
||||
type: console
|
||||
layout:
|
||||
type: pattern
|
||||
pattern: "%date{ISO8601_TZ}{UTC}"
|
||||
-------------------
|
||||
See https://github.com/elastic/kibana/pull/90368 for more details.
|
||||
|
||||
[float]
|
||||
==== Responses are never logged by default
|
||||
*Details:* Previously responses would be logged if either `logging.json` was true, `logging.dest` was specified, or a `TTY` was detected. With the new logging configuration, these are provided by a dedicated logger.
|
||||
|
||||
*Impact:* To restore the previous behavior, in `kibana.yml` enable `debug` for the `http.server.response` logger:
|
||||
[source,yaml]
|
||||
-------------------
|
||||
logging:
|
||||
appenders:
|
||||
custom:
|
||||
type: console
|
||||
layout:
|
||||
type: pattern
|
||||
loggers:
|
||||
- name: http.server.response
|
||||
appenders: [custom]
|
||||
level: debug
|
||||
-------------------
|
||||
See https://github.com/elastic/kibana/pull/87939 for more details.
|
||||
|
||||
[float]
|
||||
==== Logging destination is specified by the appender
|
||||
*Details:* Previously log destination would be `stdout` and could be changed to `file` using `logging.dest`. With the new logging configuration, you can specify the destination using {kibana-ref}/logging-configuration.html#logging-appenders[appenders].
|
||||
|
||||
*Impact:* To restore the previous behavior and log records to *stdout*, in `kibana.yml` use an appender with `type: console`.
|
||||
[source,yaml]
|
||||
-------------------
|
||||
logging:
|
||||
appenders:
|
||||
custom:
|
||||
type: console
|
||||
layout:
|
||||
type: pattern
|
||||
root:
|
||||
appenders: [default, custom]
|
||||
-------------------
|
||||
|
||||
To send logs to `file` with a given file path, you should define a custom appender with `type:file`:
|
||||
[source,yaml]
|
||||
-------------------
|
||||
logging:
|
||||
appenders:
|
||||
file:
|
||||
type: file
|
||||
fileName: /var/log/kibana.log
|
||||
layout:
|
||||
type: pattern
|
||||
root:
|
||||
appenders: [default, file]
|
||||
-------------------
|
||||
|
||||
[float]
|
||||
==== Set log verbosity with root
|
||||
*Details:* Previously logging output would be specified by `logging.silent` (none), `logging.quiet` (error messages only) and `logging.verbose` (all). With the new logging configuration, set the minimum required {kibana-ref}/logging-configuration.html#log-level[log level].
|
||||
|
||||
*Impact:* To restore the previous behavior, in `kibana.yml` specify `logging.root.level`:
|
||||
[source,yaml]
|
||||
-------------------
|
||||
# suppress all logs
|
||||
logging:
|
||||
root:
|
||||
level: off
|
||||
-------------------
|
||||
|
||||
[source,yaml]
|
||||
-------------------
|
||||
# only log error messages
|
||||
logging:
|
||||
root:
|
||||
level: error
|
||||
-------------------
|
||||
|
||||
[source,yaml]
|
||||
-------------------
|
||||
# log all events
|
||||
logging:
|
||||
root:
|
||||
level: all
|
||||
-------------------
|
||||
|
||||
[float]
|
||||
==== Declare log message format
|
||||
*Details:* Previously all events would be logged in `json` format when `logging.json` was true. With the new logging configuration you can specify the output format with layouts. You can choose between `json` and pattern format depending on your needs.
|
||||
|
||||
*Impact:* To restore the previous behavior, in `kibana.yml` configure the logging format for each custom appender with the `appender.layout` property. There is no default for custom appenders and each one must be configured expilictly.
|
||||
|
||||
[source,yaml]
|
||||
-------------------
|
||||
logging:
|
||||
appenders:
|
||||
custom_console:
|
||||
type: console
|
||||
layout:
|
||||
type: pattern
|
||||
custom_json:
|
||||
type: console
|
||||
layout:
|
||||
type: json
|
||||
loggers:
|
||||
- name: plugins.myPlugin
|
||||
appenders: [custom_console]
|
||||
root:
|
||||
appenders: [default, custom_json]
|
||||
level: warn
|
||||
-------------------
|
||||
|
||||
[float]
|
||||
==== Configure log rotation with the rolling-file appender
|
||||
*Details:* Previously log rotation would be enabled when `logging.rotate.enabled` was true.
|
||||
|
||||
*Impact:* To restore the previous behavior, in `kibana.yml` use the {kibana-ref}/logging-configuration.html#rolling-file-appender[`rolling-file`] appender.
|
||||
|
||||
[source,yaml]
|
||||
-------------------
|
||||
logging:
|
||||
appenders:
|
||||
rolling-file:
|
||||
type: rolling-file
|
||||
fileName: /var/logs/kibana.log
|
||||
policy:
|
||||
type: size-limit
|
||||
size: 50mb
|
||||
strategy:
|
||||
type: numeric
|
||||
pattern: '-%i'
|
||||
max: 2
|
||||
layout:
|
||||
type: pattern
|
||||
loggers:
|
||||
- name: plugins.myPlugin
|
||||
appenders: [rolling-file]
|
||||
-------------------
|
||||
|
||||
[float]
|
||||
==== `xpack.security.authProviders` is no longer valid
|
||||
*Details:* The deprecated `xpack.security.authProviders` setting in the `kibana.yml` file has been removed.
|
||||
|
||||
*Impact:* Use `xpack.security.authc.providers` instead.
|
||||
|
||||
[float]
|
||||
==== `xpack.security.authc.providers` has changed value format
|
||||
*Details:* `xpack.security.authc.providers` setting in the `kibana.yml` has changed value format.
|
||||
|
||||
*Impact:* Array of provider types as a value is no longer supported, use extended object format instead.
|
||||
|
||||
[float]
|
||||
==== `xpack.security.authc.saml` is no longer valid
|
||||
*Details:* The deprecated `xpack.security.authc.saml` setting in the `kibana.yml` file has been removed.
|
||||
|
||||
*Impact:* Configure SAML authentication providers using `xpack.security.authc.providers.saml.{provider unique name}.*` settings instead.
|
||||
|
||||
[float]
|
||||
==== `xpack.security.authc.oidc` is no longer valid
|
||||
*Details:* The deprecated `xpack.security.authc.oidc` setting in the `kibana.yml` file has been removed.
|
||||
|
||||
*Impact:* Configure OpenID Connect authentication providers using `xpack.security.authc.providers.oidc.{provider unique name}.*` settings instead.
|
||||
|
||||
[float]
|
||||
==== `xpack.security.public` is no longer valid
|
||||
*Details:* Previously Kibana was choosing the appropriate Elasticsearch SAML realm automatically using the `Assertion Consumer Service`
|
||||
URL that it derived from the actual server address and `xpack.security.public` setting. Starting in 8.0.0, the deprecated `xpack.security.public` setting in the `kibana.yml` file has been removed and the Elasticsearch SAML realm name that Kibana will use should be specified explicitly.
|
||||
|
||||
*Impact:* Define `xpack.security.authc.providers.saml.{provider unique name}.realm` when using the SAML authentication providers instead.
|
||||
|
||||
[float]
|
||||
==== `/api/security/v1/saml` endpoint is no longer supported
|
||||
*Details:* The deprecated `/api/security/v1/saml` endpoint is no longer supported.
|
||||
|
||||
*Impact:* Rely on `/api/security/saml/callback` endpoint when using SAML instead. This change should be reflected in Elasticsearch and Identity Provider SAML settings.
|
||||
|
||||
[float]
|
||||
==== `/api/security/v1/oidc` endpoint is no longer supported
|
||||
*Details:* The deprecated `/api/security/v1/oidc` endpoint is no longer supported.
|
||||
|
||||
*Impact:* Rely on `/api/security/oidc/callback` endpoint when using OpenID Connect instead. This change should be reflected in Elasticsearch and OpenID Connect Provider settings.
|
||||
|
||||
[float]
|
||||
==== `/api/security/v1/oidc` endpoint is no longer supported for Third Party initiated login
|
||||
*Details:* The deprecated `/api/security/v1/oidc` endpoint is no longer supported for Third Party initiated login.
|
||||
|
||||
*Impact:* Rely on `/api/security/oidc/initiate_login` endpoint when using Third Party initiated OpenID Connect login instead. This change should be reflected in Elasticsearch and OpenID Connect Provider settings.
|
||||
|
||||
[float]
|
||||
==== `/api/security/v1/oidc/implicit` endpoint is no longer supported
|
||||
*Details:* The deprecated `/api/security/v1/oidc/implicit` endpoint is no longer supported.
|
||||
|
||||
*Impact:* Rely on `/api/security/oidc/implicit` endpoint when using OpenID Connect Implicit Flow instead. This change should be reflected in OpenID Connect Provider settings.
|
||||
|
||||
[float]
|
||||
=== `optimize` directory is now in the `data` folder
|
||||
*Details:* Generated bundles have moved to the configured `path.data` folder.
|
||||
|
||||
*Impact:* Any workflow that involved manually clearing generated bundles will have to be updated with the new path.
|
||||
|
||||
[float]
|
||||
=== Legacy `optimize.*` settings are no longer supported
|
||||
*Details:* The legacy optimizer has been removed and any `optimize.*` settings have been deprecated since 7.10. These settings have been removed as they are no longer in use.
|
||||
|
||||
*Impact:* Any of the legacy `optimize.*` settings will prevent Kibana from starting up. Going forward, to run the `@kbn/optimizer` separately in development, pass `--no-optimizer` to `yarn start`. See https://github.com/elastic/kibana/pull/73154 for more details.
|
||||
|
||||
[float]
|
||||
=== kibana.keystore has moved from the `data` folder to the `config` folder
|
||||
*Details:* By default, kibana.keystore has moved from the configured `path.data` folder to `<root>/config` for archive distributions
|
||||
and `/etc/kibana` for package distributions. If a pre-existing keystore exists in the data directory that path will continue to be used.
|
||||
|
||||
[float]
|
||||
[[breaking_80_user_role_changes]]
|
||||
=== User role changes
|
||||
|
||||
[float]
|
||||
=== `kibana_user` role has been removed and `kibana_admin` has been added.
|
||||
|
||||
*Details:* The `kibana_user` role has been removed and `kibana_admin` has been added to better
|
||||
reflect its intended use. This role continues to grant all access to every
|
||||
{kib} feature. If you wish to restrict access to specific features, create
|
||||
custom roles with {kibana-ref}/kibana-privileges.html[{kib} privileges].
|
||||
|
||||
*Impact:* Any users currently assigned the `kibana_user` role will need to
|
||||
instead be assigned the `kibana_admin` role to maintain their current
|
||||
access level.
|
||||
|
||||
[float]
|
||||
=== `kibana_dashboard_only_user` role has been removed.
|
||||
|
||||
*Details:* The `kibana_dashboard_only_user` role has been removed.
|
||||
If you wish to restrict access to just the Dashboard feature, create
|
||||
custom roles with {kibana-ref}/kibana-privileges.html[{kib} privileges].
|
||||
|
||||
*Impact:* Any users currently assigned the `kibana_dashboard_only_user` role will need to be assigned a custom role which only grants access to the Dashboard feature.
|
||||
|
||||
Granting additional cluster or index privileges may enable certain
|
||||
**Stack Monitoring** features.
|
||||
|
||||
[float]
|
||||
[[breaking_80_reporting_changes]]
|
||||
=== Reporting changes
|
||||
|
||||
[float]
|
||||
==== Legacy job parameters are no longer supported
|
||||
*Details:* POST URL snippets that were copied in Kibana 6.2 or earlier are no longer supported. These logs have
|
||||
been deprecated with warnings that have been logged throughout 7.x. Please use Kibana UI to re-generate the
|
||||
POST URL snippets if you depend on these for automated PDF reports.
|
||||
|
||||
[float]
|
||||
=== Configurations starting with `xpack.telemetry` are no longer valid
|
||||
|
||||
*Details:*
|
||||
The `xpack.` prefix has been removed for all telemetry configurations.
|
||||
|
||||
*Impact:*
|
||||
For any configurations beginning with `xpack.telemetry`, remove the `xpack` prefix. Use {kibana-ref}/telemetry-settings-kbn.html#telemetry-general-settings[`telemetry.enabled`] instead.
|
||||
|
||||
[float]
|
||||
=== SysV init support has been removed
|
||||
|
||||
*Details:*
|
||||
All supported operating systems support using systemd service files. Any system that doesn't already have service aliased to use kibana.service should use `systemctl start kibana.service` instead of the `service start kibana`.
|
||||
|
||||
*Impact:*
|
||||
Any installations using `.deb` or `.rpm` packages using SysV will need to migrate to systemd.
|
||||
|
||||
[float]
|
||||
=== TLS v1.0 and v1.1 are disabled by default
|
||||
|
||||
*Details:*
|
||||
Support can be re-enabled by setting `--tls-min-1.0` in the `node.options` config file that can be found inside `kibana/config` folder or any other configured with the environment variable `KBN_PATH_CONF` (for example in Debian based system would be `/etc/kibana`).
|
||||
|
||||
*Impact:*
|
||||
Browser and proxy clients communicating over TLS v1.0 and v1.1.
|
||||
|
||||
[float]
|
||||
=== Platform removed from root folder name for `.tar.gz` and `.zip` archives
|
||||
|
||||
*Details:*
|
||||
The output directory after extracting an archive no longer includes the target platform. For example, `kibana-8.0.0-linux-aarch64.tar.gz` will produce a folder named `kibana-8.0.0`.
|
||||
|
||||
*Impact:*
|
||||
Configuration management tools and automation will need to be updated to use the new directory.
|
||||
|
||||
[float]
|
||||
=== `elasticsearch.preserveHost` is no longer valid
|
||||
*Details:* The deprecated `elasticsearch.preserveHost` setting in the `kibana.yml` file has been removed.
|
||||
|
||||
*Impact:* Configure {kibana-ref}/settings.html#elasticsearch-requestHeadersWhitelist[`elasticsearch.requestHeadersWhitelist`] to whitelist client-side headers.
|
||||
|
||||
[float]
|
||||
=== `elasticsearch.startupTimeout` is no longer valid
|
||||
*Details:* The deprecated `elasticsearch.startupTimeout` setting in the `kibana.yml` file has been removed.
|
||||
|
||||
*Impact:* Kibana will keep on trying to connect to Elasticsearch until it manages to connect.
|
||||
|
||||
[float]
|
||||
=== `savedObjects.indexCheckTimeout` is no longer valid
|
||||
*Details:* The deprecated `savedObjects.indexCheckTimeout` setting in the `kibana.yml` file has been removed.
|
||||
|
||||
[float]
|
||||
=== `server.xsrf.token` is no longer valid
|
||||
*Details:* The deprecated `server.xsrf.token` setting in the `kibana.yml` file has been removed.
|
||||
|
||||
[float]
|
||||
=== `newsfeed.defaultLanguage` is no longer valid
|
||||
*Details:* Specifying a default language to retrieve newsfeed items is no longer supported.
|
||||
|
||||
*Impact:* Newsfeed items will be retrieved based on the browser locale and fallback to 'en' if an item does not have a translation for the locale. Configure {kibana-ref}/i18n-settings-kb.html#general-i18n-settings-kb[`i18n.locale`] to override the default behavior.
|
||||
|
||||
[float]
|
||||
=== `xpack.banners.placement` has changed value
|
||||
*Details:* `xpack.banners.placement: 'header'` setting in `kibana.yml` has changed value.
|
||||
|
||||
*Impact:* Use {kibana-ref}/banners-settings-kb.html#banners-settings-kb[`xpack.banners.placement: 'top'`] instead.
|
||||
|
||||
[float]
|
||||
=== `cpu.cgroup.path.override` is no longer valid
|
||||
*Details:* The deprecated `cpu.cgroup.path.override` setting is no longer supported.
|
||||
|
||||
*Impact:* Configure {kibana-ref}/settings.html#ops-cGroupOverrides-cpuPath[`ops.cGroupOverrides.cpuPath`] instead.
|
||||
|
||||
[float]
|
||||
=== `cpuacct.cgroup.path.override` is no longer valid
|
||||
*Details:* The deprecated `cpuacct.cgroup.path.override` setting is no longer supported.
|
||||
|
||||
*Impact:* Configure {kibana-ref}/settings.html#ops-cGroupOverrides-cpuAcctPath[`ops.cGroupOverrides.cpuAcctPath`] instead.
|
||||
|
||||
[float]
|
||||
=== `server.xsrf.whitelist` is no longer valid
|
||||
*Details:* The deprecated `server.xsrf.whitelist` setting is no longer supported.
|
||||
|
||||
*Impact:* Use {kibana-ref}/settings.html#settings-xsrf-allowlist[`server.xsrf.allowlist`] instead.
|
||||
18
docs/migration/migrate_9_0.asciidoc
Normal file
18
docs/migration/migrate_9_0.asciidoc
Normal file
|
|
@ -0,0 +1,18 @@
|
|||
[[breaking-changes-9.0]]
|
||||
== Breaking changes in 9.0
|
||||
++++
|
||||
<titleabbrev>9.0</titleabbrev>
|
||||
++++
|
||||
|
||||
This section discusses the changes that you need to be aware of when migrating
|
||||
your application to Kibana 9.0.
|
||||
|
||||
See also <<whats-new>> and <<release-notes>>.
|
||||
|
||||
* <<breaking_90_setting_changes>>
|
||||
|
||||
|
||||
[float]
|
||||
[[breaking_90_setting_changes]]
|
||||
=== Settings changes
|
||||
|
||||
|
|
@ -418,10 +418,6 @@ This page has been deleted. Refer to <<machine-learning-api-sync>>.
|
|||
|
||||
This page has been deleted. Refer to <<alerting-getting-started>>.
|
||||
|
||||
[role="exclude",id="enhancements-and-bug-fixes-v8.10.0"]
|
||||
== Enhancements and bug fixes for 8.10.0
|
||||
|
||||
This content has moved. Refer to <<enhancements-and-bug-fixes-v8.10.0-revised>> for 8.10.0.
|
||||
|
||||
[role="exclude",id="gen-ai-action-type"]
|
||||
== Generative AI connector and action
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ Different versions of {kib} running against the same {es} index, such as during
|
|||
+
|
||||
|
||||
Make sure you remove or update any configurations
|
||||
that are indicated in the <<breaking-changes-8.0.0,breaking changes>> documentation
|
||||
that are indicated in the <<breaking-changes-9.0.0,breaking changes>> documentation
|
||||
otherwise {kib} will fail to start.
|
||||
--
|
||||
. Upgrade any plugins by removing the existing plugin and reinstalling the
|
||||
|
|
@ -51,7 +51,7 @@ and becomes a new instance in the monitoring data.
|
|||
--
|
||||
. Copy the files from the `config` directory from your old installation to your
|
||||
new installation. Make sure you remove or update any configurations that are
|
||||
indicated in the <<breaking-changes-8.0.0,breaking changes>> documentation
|
||||
indicated in the <<breaking-changes-9.0.0,breaking changes>> documentation
|
||||
otherwise {kib} will fail to start.
|
||||
. Copy the files from the `data` directory from your old installation to your
|
||||
new installation.
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load diff
|
|
@ -1,144 +1,10 @@
|
|||
[[whats-new]]
|
||||
== What's new in 8.16
|
||||
== What's new in 9.0
|
||||
|
||||
Here are the highlights of what's new and improved in 8.16.
|
||||
Here are the highlights of what's new and improved in 9.0.
|
||||
For detailed information about this release,
|
||||
check the <<release-notes, release notes>>.
|
||||
|
||||
Previous versions: {kibana-ref-all}/8.15/whats-new.html[8.15] | {kibana-ref-all}/8.14/whats-new.html[8.14] | {kibana-ref-all}/8.13/whats-new.html[8.13] | {kibana-ref-all}/8.12/whats-new.html[8.12] | {kibana-ref-all}/8.11/whats-new.html[8.11] | {kibana-ref-all}/8.10/whats-new.html[8.10] | {kibana-ref-all}/8.9/whats-new.html[8.9] | {kibana-ref-all}/8.8/whats-new.html[8.8] | {kibana-ref-all}/8.7/whats-new.html[8.7] | {kibana-ref-all}/8.6/whats-new.html[8.6] | {kibana-ref-all}/8.5/whats-new.html[8.5] | {kibana-ref-all}/8.4/whats-new.html[8.4] | {kibana-ref-all}/8.3/whats-new.html[8.3] | {kibana-ref-all}/8.2/whats-new.html[8.2] | {kibana-ref-all}/8.1/whats-new.html[8.1] | {kibana-ref-all}/8.0/whats-new.html[8.0]
|
||||
|
||||
[discrete]
|
||||
=== Solution-oriented navigation
|
||||
On Elastic Cloud Hosted deployments running on version 8.16, you can now navigate Kibana using a lighter, solution-oriented left navigation menu, called **Solution view**.
|
||||
|
||||
There are four selectable solution views: Search, Observability, Security, and Classic. Search, Observability, and Security are the new navigation menus. Each of those brings simplicity by focusing the left navigation menu on a relevant subset of features, scoped to its associated use cases, and offers a dedicated home page. Classic has the same navigation menu as 8.15 and before.
|
||||
|
||||
Each space has its own solution view setting which determines the navigation experience for all users of that space.
|
||||
|
||||
When creating a new deployment, you will now be asked to choose between one of the 3 new solution views for your default space. If you prefer to stick with the classic, multi-layered navigation, you can do so once the deployment is created by navigating to your space settings.
|
||||
|
||||
Deployments upgrading from a previous version to 8.16 keep the classic navigation. Admins can enable one of the new solution views from the space settings.
|
||||
|
||||
image::images/solution-view-obs.png[Example of observability solution view]
|
||||
_The Observability solution view and its Home page._
|
||||
|
||||
[discrete]
|
||||
=== Discover and ES|QL
|
||||
|
||||
[discrete]
|
||||
==== Contextual Data presentation
|
||||
|
||||
In this release, Discover introduces enhanced contextual data presentation. Previously, you needed to manually select relevant fields and set up your workspace before diving into data exploration. Now, Discover automatically tailors the user experience based on the data being explored, powered by a scalable contextual architecture. For example, when analyzing logs, you'll see a *log.level* field rendered directly in the table, a custom Logs overview in the document viewer, and log.level indicators on individual rows.
|
||||
|
||||
image::images/discover-log-level.png[Log level badge displaying in the Discover grid]
|
||||
|
||||
[discrete]
|
||||
==== Recommended ES|QL queries
|
||||
|
||||
Writing ES|QL queries just got easier. Many users face challenges when authoring queries, and even more so when unfamiliar with the syntax or data structure. This can lead to inefficiencies in data analysis and visualization. We want to reduce the time it takes to create queries and to lower the learning curve for both new and existing users by suggesting recommended queries within the ES|QL Help menu and from the auto-complete.
|
||||
|
||||
image::images/esql-suggestions.png[A list of suggestions to get started with an ES|QL query, width=30%]
|
||||
_Recommended ES|QL queries from the ES|QL help menu_
|
||||
|
||||
image::images/esql-autocomplete-suggestions.png[A list of suggestions in the autocomplete menu of an ES|QL query, width=50%]
|
||||
_Recommended ES|QL queries from auto-complete suggestions_
|
||||
|
||||
|
||||
|
||||
[discrete]
|
||||
=== Dashboards
|
||||
|
||||
[discrete]
|
||||
==== Manage dashboards more easily and efficiently
|
||||
As part of a series of improvements to help you find and manage your dashboards https://www.elastic.co/guide/en/kibana/8.15/whats-new.html#_view_dashboard_creator_and_last_editor[started in version 8.15], the new default way to sort your dashboards is by recently viewed, and we are adding an option to star your favorite dashboards, as well as some statistics to monitor the usage of your dashboards.
|
||||
|
||||
You can find your favorite dashboards in the new **Starred** tab.
|
||||
|
||||
image::images/dashboard-star.png[Viewing starred dashboards]
|
||||
|
||||
By opening a dashboard's details using the “info” icon from the dashboard list view, you can now get a sense of the popularity of that dashboard with a histogram showing how many times the dashboard was viewed in the last 90 days.
|
||||
|
||||
image::images/dashboard-usage.png[Dashboard usage chart]
|
||||
|
||||
[discrete]
|
||||
==== Log Pattern Analysis dashboard panels
|
||||
Log Pattern Analysis panels are now available for you to add to your dashboards, making AIOps even more embedded in your workflows and where you need it. When filtering patterns, the dashboard’s data adjusts accordingly. You can also choose the filtering to transition you into Discover for further exploration.
|
||||
|
||||
image:https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt8288e01386b5830c/67222fb0d2da223e27bc1e67/log_analysis_panel.gif[Log pattern analysis panel in dashboards]
|
||||
|
||||
|
||||
[discrete]
|
||||
==== Color text values in tables
|
||||
Previously, you could only decide to color numeric values in tables. We're adding the ability to also color your string values. You can decide whether you want to color the whole cell, or only the text.
|
||||
|
||||
image::images/table-coloring.png[Coloring table cells with string values]
|
||||
|
||||
|
||||
[discrete]
|
||||
==== Formatting options for your metrics
|
||||
We've received a lot of feedback asking for more flexibility to customize the appearance of your metrics. In this version, we are adding the ability to customize the title and value alignment, as well as the font size. Selecting the *Fit* option will adjust the font size and make the metric value occupy the entire panel.
|
||||
|
||||
image::images/metric-customization.png[Customization options for a metric panel]
|
||||
|
||||
|
||||
|
||||
//[discrete]
|
||||
//=== Alerting, cases, and connectors
|
||||
|
||||
|
||||
[discrete]
|
||||
=== Managing {kib} and data
|
||||
|
||||
[discrete]
|
||||
==== Edit space access from the space settings
|
||||
As an admin, you can now assign roles to and edit role permissions on a given space directly from the settings of that space.
|
||||
|
||||
Prior to 8.16, you could only do this from the role settings, which was counterintuitive.
|
||||
|
||||
image::space-settings.png[Editing space settings with new options]
|
||||
|
||||
[discrete]
|
||||
==== New IP Location processor
|
||||
Enhancing location information based on IP addresses just got easier with the new IP Location processor. In addition to the existing free GeoLite offerings from MaxMind, we have integrated with MaxMind’s premium GeoIP databases for users who have licensed MaxMind’s products. If you're an Enterprise Elastic customer, you now have an additional third-party product, IP Info, available for use as well. These additional data sources provide improved options for enriching data with location information associated with IP addresses to improve telemetry and insights. To utilize these features beyond the free MaxMind GeoIP database, you will need to have licensed premium MaxMind products and/or the IP Info database.
|
||||
|
||||
image::images/ip-location-processor.png[The IP Location processor]
|
||||
|
||||
[discrete]
|
||||
==== File uploader PDF support
|
||||
The file uploader provides a quick way to upload data and start using Elastic. In 8.16, we are improving it to allow you to upload data from PDF files.
|
||||
|
||||
image:https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blte8f0b295330b7e68/67222fb0ca492a5044b51bd8/file_uploader_pdf.gif[File uploader with PDF support]
|
||||
|
||||
[discrete]
|
||||
=== Developer Tools Console redesign
|
||||
We're excited to introduce a number of improvements to the overall user experience on one of our most popular features: **Console**. If you're new to Console, you will be welcomed by an onboarding tour that will help you get started quickly with your first requests. And if you're already a regular Console user, you will notice a variety of new features, including the ability to copy outputs to the clipboard, import and export request files, enjoy improved responsiveness, and other quality of life improvements.
|
||||
|
||||
image::images/monaco-console.png[Console's redesign featuring the Monaco editor]
|
||||
|
||||
[discrete]
|
||||
=== Machine Learning
|
||||
|
||||
[discrete]
|
||||
==== The Inference API is now Generally Available
|
||||
|
||||
Starting in 8.16, the {ref}/inference-apis.html[Inference API] is now GA, offering production-level stability, robustness and performance. Elastic’s Inference API integrates the state-of-the-art in AI inference, including ELSER, your Elastic hosted models and {ref}/put-inference-api.html#put-inference-api-desc[an increasing array of external models and tasks] in a unified, lean syntax. Used with {ref}/semantic-text.html[semantic_text] or the vector fields supported by the Elastic vector database, you can perform AI search, reranking, and completion with simplicity. In 8.16, we're also adding streamed completions for improved flows and real time interactions and GenAI experiences.
|
||||
|
||||
[discrete]
|
||||
==== ELSER and trained models adaptive resources and chunking strategies
|
||||
|
||||
From 8.16, ELSER and the other AI search and NLP models you use in Elastic automatically adapt resource consumption according to the inference load, providing the performance you need during peak times and reducing the cost during slow periods, all the way down to zero cost during idle times.
|
||||
|
||||
We're also improving the UX through which you deploy your models. You can provision search-optimized and ingest-optimized model deployments with a one-click selection. An optimized configuration is created without the need to specify parameters such as threads and allocations. Combined with the flexibility of ML auto-scaling on Elastic Cloud and the incredible elasticity of Elastic Cloud Serverless, you are in full control of both performance and cost.
|
||||
|
||||
image::https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt429790e1de1b4f93/67222fb048ec8c73255ef4eb/trained_models.gif[Trained models and ELSER]
|
||||
|
||||
In addition, from 8.16 you can choose between a word or sequence-based chunking strategy to use with your trained models, and you can also customize the maximum size and overlap parameters. A suitable chunking strategy can result in gains depending on the model you use, the length and nature of the texts and the length and complexity of the search queries.
|
||||
|
||||
|
||||
[discrete]
|
||||
==== Support for Daylight Saving Time changes in Anomaly Detection
|
||||
|
||||
In 8.16, we are introducing support for DST changes in Anomaly Detection. Set up a DST calendar by selecting the right timezone and apply it to your anomaly detection jobs individually or in groups. This feature eliminates any false positives that you may have experienced previously due to Daylight Saving Time changes, and works without the need for your intervention for many years ahead.
|
||||
|
||||
image::https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt5fb82f18cde26710/67222fb086339971144a31e5/daylight_savings.gif[DST support in Anomaly Detection]
|
||||
//Uncomment and edit from 9.1:
|
||||
//Previous versions: {kibana-ref-all}/9.0/whats-new.html[9.0] | {kibana-ref-all}/8.18/whats-new.html[8.18]
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue