The following changes are included in this release.

Featuresedit

Enable self-monitoring on deployment creation. Extension to the Create Deployment API call: The observability destination for logging and metrics can now also be set to self. This way it is possible to create a deployment with log and metrics delivery already enabled to itself.

Add name to account trust. Added a name property to the AccountTrustRelationship setting used for configuring Trust management. This enables trust to be configured based on an organization name.

Enhancementsedit

Rename upstream to backend. Renamed upstream_proto in the Proxy logs to backend_proto to maintain consistency with other Proxy log fields relating to the connection between the Proxy and the stack components. upstream_dialer has also been renamed to backend_dialer for the same reason.

Change frozen nodes and cache storage wording. Changed the UI wording on frozen instances to clarify how much of the blob storage is full, based on the disk storage.

Add description, size, and last modified to the table for extensions. Added three new fields to the table showing your deployment extensions. You can now see the description field, the size of the extension, and when it was last modified.

Allow list Kibana setting "migrations.discardCorruptObjects: text". When upgrading the stack, Kibana runs a migration process to ensure system indices are up-to-date with the newer version. Sometimes, migrations might fail due to data inconsistencies. For instance if corrupt objects exist or transform errors occur during a migration, this will cause the migration to fail.

This version adds support for the new migrations.discardCorruptObjects flag. This flag tells Kibana to discard corrupt saved objects that can be found during a migration, as well as transform errors, logging a warning message and carrying on with the migration process.

Note that this flag must be set to the target version, that is, the version to which the stack is being upgraded. For instance, if you are upgrading to 8.4.0, you must set migrations.discardCorruptObjects: "8.4.0" in order for the flag to be taken into account. This is a safeguard that prevents Kibana to systematically ignore / discard unknown objects in future migrations, in case users forget to disable the flag after a migration.

Allow list Kibana setting "migrations.discardUnknownObjects: text". When upgrading the stack, Kibana runs a migration process to ensure system indices are up-to-date with the newer version. Sometimes, migrations might fail due to data inconsistencies. For instance if saved objects exist which have unknown types, this will cause the migration to fail.

This version adds support for the new migrations.discardUnknownObjects flag. This flag tells Kibana to discard unknown saved objects that can be found during a migration, logging a warning message and carrying on with the migration process.

Note that this flag must be set to the target version, that is, the version to which the stack is being upgraded. For instance, if you are upgrading to 8.4.0, you must set migrations.discardUnknownObjects: "8.4.0" in order for the flag to be taken into account. This is a safeguard that prevents Kibana to systematically ignore / discard unknown objects in future migrations, in case users forget to disable the flag after a migration.

Bug fixesedit

TermQuery.value is not an object type. Updated the Swagger type of TermQuery.value to string.

Don’t send payload on console API if it’s empty strings. Fixed a bug in the API console where content-type was being sent when no body existed in the API request.

Fix trust UI issue for multiple trusted deployments. Fixed an issue where trusting more than one specific deployment would lead to those deployments being listed as (deleted) in the deployment trust UI.