mirror of
https://github.com/elastic/kibana.git
synced 2025-04-22 08:49:27 -04:00
7bf3f64e90
# Backport This will backport the following commits from `main` to `8.13`: - [Adding the whats new in 8.13 page (#179097)](https://github.com/elastic/kibana/pull/179097) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"amyjtechwriter","email":"61687663+amyjtechwriter@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-03-25T19:19:54Z","message":"Adding the whats new in 8.13 page (#179097)\n\nThis PR adds details about whats new to the 8.13 release on the [whats\r\nnew page](https://www.elastic.co/guide/en/kibana/8.10/whats-new.html).\r\n\r\nCloses: [#179049](https://github.com/elastic/kibana/issues/179049)\r\n\r\n---------\r\n\r\nCo-authored-by: lcawl <lcawley@elastic.co>","sha":"0a949de7c81c0ed519e292a956d32f8777ef9bbf","branchLabelMapping":{"^v8.14.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","v8.13.0","v8.14.0"],"title":"Adding the whats new in 8.13 page","number":179097,"url":"https://github.com/elastic/kibana/pull/179097","mergeCommit":{"message":"Adding the whats new in 8.13 page (#179097)\n\nThis PR adds details about whats new to the 8.13 release on the [whats\r\nnew page](https://www.elastic.co/guide/en/kibana/8.10/whats-new.html).\r\n\r\nCloses: [#179049](https://github.com/elastic/kibana/issues/179049)\r\n\r\n---------\r\n\r\nCo-authored-by: lcawl <lcawley@elastic.co>","sha":"0a949de7c81c0ed519e292a956d32f8777ef9bbf"}},"sourceBranch":"main","suggestedTargetBranches":["8.13"],"targetPullRequestStates":[{"branch":"8.13","label":"v8.13.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.14.0","branchLabelMappingKey":"^v8.14.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/179097","number":179097,"mergeCommit":{"message":"Adding the whats new in 8.13 page (#179097)\n\nThis PR adds details about whats new to the 8.13 release on the [whats\r\nnew page](https://www.elastic.co/guide/en/kibana/8.10/whats-new.html).\r\n\r\nCloses: [#179049](https://github.com/elastic/kibana/issues/179049)\r\n\r\n---------\r\n\r\nCo-authored-by: lcawl <lcawley@elastic.co>","sha":"0a949de7c81c0ed519e292a956d32f8777ef9bbf"}}]}] BACKPORT--> Co-authored-by: amyjtechwriter <61687663+amyjtechwriter@users.noreply.github.com>
253 lines
15 KiB
Text
253 lines
15 KiB
Text
[[whats-new]]
|
||
== What's new in 8.13
|
||
|
||
Here are the highlights of what's new and improved in 8.13.
|
||
For detailed information about this release,
|
||
check the <<release-notes, release notes>>.
|
||
|
||
Previous versions: {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]
|
||
=== Discover
|
||
|
||
[discrete]
|
||
==== Empty fields improvements in Discover, Lens & ES|QL
|
||
|
||
Navigating through extensive data can often lead users to encounter numerous *Empty fields* within their field lists, making it challenging to identify and access valuable data efficiently. To address this issue, we’ve focused our efforts on enhancing the *Empty fields* category. Our solution simplifies the process of finding and accessing fields that contain meaningful data, ensuring a more streamlined and productive data exploration experience for our users.
|
||
|
||
In some cases this can have a huge impact on field lists that target indices with many fields, such as in the below example where the field list was reduced from 5,492 fields down to only 238.
|
||
|
||
[role="screenshot"]
|
||
image::images/empty-fields.png[An image of the available fields before the improvements.]
|
||
|
||
[role="screenshot"]
|
||
image::images/empty-fields-results.png[An image of the improvements to the available fields.]
|
||
|
||
[discrete]
|
||
==== Discover enhancements
|
||
|
||
Improving the experience in Discover when users are exploring their data helps them find insights quickly. In 8.13 we added the *Auto Interval* to the Histogram, which allows users to quickly select a *Time Interval*. We also enhanced the UI by moving the count of documents to the table and new panel toggle buttons for toggling fields sidebar and histogram.
|
||
|
||
[role="screenshot"]
|
||
image::images/auto-interval.png[An image of the new auto interval option, width=60%]
|
||
|
||
[role="screenshot"]
|
||
image::images/auto-interval-1.png[An image of the auto option.]
|
||
|
||
[discrete]
|
||
==== Cancellation of the {esql} long-running query
|
||
|
||
You can now cancel a long-running {esql} query from the UI.
|
||
|
||
[role="screenshot"]
|
||
image::images/cancel-button.png[]
|
||
|
||
|
||
[discrete]
|
||
==== Better validation and autocomplete when writing ES|QL queries
|
||
|
||
Autocomplete and validation are important tools to ensure the user’s ES|QL is correct and can be executed without errors. With these improvements, we are speeding up their workflow and increasing the quality of the improvements.
|
||
|
||
[role="screenshot"]
|
||
image::images/esql-validation.png[An image of {esql} validation in action.]
|
||
|
||
[discrete]
|
||
==== Color all terms in new color mapping
|
||
|
||
In our latest update, based on early feedback, we've enhanced the user experience with our new color mapping feature introducing a more intuitive default option. Now users can either assign a single color or enable color looping for unassigned terms, providing greater flexibility and a cleaner interface for term assignments. Additionally we've eliminated the maximum limit on assignments, allowing for more comprehensive customization. It's important to note that looping colors or using more than 10 colors can be effective in certain scenarios. However, we recommend limiting the number of colors used to prevent potential misinterpretation of your charts. This update aims to make color mapping more user-friendly and adaptable to your needs.
|
||
|
||
[role="screenshot"]
|
||
image::images/color-mapping-enhanced.png[An image of the color mapping feature applied to a vertical bar chart.]
|
||
|
||
[role="screenshot"]
|
||
image::images/color-mapping-1.png[An image of the color palette options, width=60%]
|
||
|
||
[discrete]
|
||
==== Visualizing an {esql} query in Observability AI assistant
|
||
|
||
The {observability} AI assistant in 8.13 comes with great improvements in query generation and performance. Users can now visualize the generated {esql} queries, edit them using the inline editing flyout, and embed them in a dashboard.
|
||
|
||
[role="screenshot"]
|
||
image::https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/bltd6737b8e5633e948/viz-esql.gif[A gif of an {esql} query in the AI assistant.]
|
||
|
||
[discrete]
|
||
==== Cross-cluster search support in {esql} and in {kib}
|
||
|
||
Cross-cluster searches are now supported in {esql} and in {kib} the feature has been introduced for both validation and autocomplete. The autocomplete feature will show some documentation about the specific settings when navigating the suggestions.
|
||
|
||
[role="screenshot"]
|
||
image::https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt4b3db027b6c7951a/ccs-esql-queries.gif[A gif of an {esql} cross cluster query.]
|
||
|
||
[discrete]
|
||
==== Quick fix to help users write {esql}
|
||
|
||
Quick fix helps users when they have misspelled a field, index, or policy name (maybe pasting a query from somewhere else) in {esql} mode.
|
||
|
||
[role="screenshot"]
|
||
image::https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt463edc257418dd71/esql-quickfix[A gif showing the quick fix feature in action.]
|
||
|
||
[discrete]
|
||
==== Create {esql} charts directly from a dashboard
|
||
|
||
Now you can create {esql} charts directly from a dashboard, without the need to go through Discover. Previously, to add a chart to your dashboard, you had to first create it in Discover using {esql} and then save it to the dashboard. This update streamlines the process, allowing you to instantly add {esql} charts right from your dashboard!
|
||
|
||
[role="screenshot"]
|
||
image::images/esql-charts-1.png[]
|
||
|
||
[role="screenshot"]
|
||
image::https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt517f402fdeddd49f/ESQLcharts.gif[A gif of editing an {esql} query in the dashboard.]
|
||
|
||
[discrete]
|
||
==== {esql} in Maps
|
||
|
||
You can now create a new documents layer in map using our recently launched https://www.elastic.co/blog/esql-elasticsearch-piped-query-language[ElasticSearch Query Language (ES|QL)]. You can query your data directly from Elasticsearch and leverage the benefits that {esql} brings such as speed and flexible data transformations to your maps.
|
||
|
||
[role="screenshot"]
|
||
image::images/esql-maps.png[An image of the {esql} option for maps.]
|
||
|
||
[role="screenshot"]
|
||
image::images/esql-maps-example.png[An image of {esql} applied to a map.]
|
||
|
||
[discrete]
|
||
==== Controls configuration
|
||
|
||
We added some improvements to controls for you to easily filter and interact with your dashboards.
|
||
|
||
* You will be able to decide whether you want the global filters and time range to be applied to your controls narrowing down the available options or whether you prefer to display all possible values without considering them. You will find these options in the Controls settings.
|
||
|
||
[role="screenshot"]
|
||
image::images/controls-config.png[An image of the filtering control settings.]
|
||
|
||
* If you have numeric fields displayed as range slider controls in your dashboard, you will now be able to decide what is the step that you want to be displayed between your values.
|
||
|
||
[role="screenshot"]
|
||
image::images/controls-edit.png[An image of the range slider settings.]
|
||
|
||
[discrete]
|
||
=== ResponseOps
|
||
|
||
[discrete]
|
||
==== Alert delay
|
||
|
||
In order to reduce noise for alerting rules with low sensitivity and ensure created alerts will be actionable and reasonable, we want to allow users to define how many rule runs should match before creating the alert. For example, "Generate the alert after 3 threshold matches in a row".
|
||
|
||
[role="screenshot"]
|
||
image::images/alert-delay.png[]
|
||
|
||
[discrete]
|
||
==== Slack action message templating using Slack Block Kit
|
||
|
||
By supporting the link:https://api.slack.com/reference/surfaces/formatting#rich-layouts[Slack Block Kit] with our {kibana-ref}/slack-action-type.html[Slack connector (Web API)], we unlock new message templates to allow users to enrich and format the messages that are sent to Slack channels. Read more about link:https://app.slack.com/block-kit-builder/T0CUZ52US#%7B%22blocks%22:%5B%7B%22type%22:%22section%22,%22text%22:%7B%22type%22:%22mrkdwn%22,%22text%22:%22You%20have%20a%20new%20request:%5Cn*%3Cgoogle.com%7CFred%20Enriquez%20-%20Time%20Off%20request%3E*%22%7D%7D,%7B%22type%22:%22section%22,%22text%22:%7B%22type%22:%22mrkdwn%22,%22text%22:%22*Type:*%5CnPaid%20time%20off%5Cn*When:*%5CnAug%2010-Aug%2013%5Cn*Hours:*%2016.0%20(2%20days)%5Cn*Remaining%20balance:*%2032.0%20hours%20(4%20days)%5Cn*Comments:*%20%5C%22Family%20in%20town,%20going%20camping!%5C%22%22%7D,%22accessory%22:%7B%22type%22:%22image%22,%22image_url%22:%22https://api.slack.com/img/blocks/bkb_template_images/approvalsNewDevice.png%22,%22alt_text%22:%22computer%20thumbnail%22%7D%7D,%7B%22type%22:%22actions%22,%22elements%22:%5B%7B%22type%22:%22button%22,%22text%22:%7B%22type%22:%22plain_text%22,%22emoji%22:true,%22text%22:%22Approve%22%7D,%22style%22:%22primary%22,%22value%22:%22click_me_123%22%7D,%7B%22type%22:%22button%22,%22text%22:%7B%22type%22:%22plain_text%22,%22emoji%22:true,%22text%22:%22Deny%22%7D,%22style%22:%22danger%22,%22value%22:%22click_me_123%22%7D%5D%7D%5D%7D[templates options with Slack Block Kit].
|
||
|
||
[role="screenshot"]
|
||
image::images/slack-api.png[An image of the Slack web api connector, width =60%]
|
||
|
||
[role="screenshot"]
|
||
image::images/slack-block.png[An image of the block kit builder.]
|
||
|
||
[discrete]
|
||
=== Machine Learning
|
||
|
||
[discrete]
|
||
==== Unified inference API now integrates Cohere embeddings
|
||
|
||
We continue enhancing Elastic's unified inference API which supports both internal and external models for seamless easy integration with the LLM ecosystem.
|
||
|
||
In 8.13 we add support for Cohere embeddings. This enhances our offering which supports OpenAI and HuggingFace embeddings since 8.12.
|
||
|
||
The power of the inference API lies in its simple, unified syntax that abstracts away the underlying complexity of using different internal and external models.
|
||
|
||
So, in 8.13 we also added support for inference against the E5 multilingual embeddings that were offered through the Trained Models UI since 8.12.
|
||
|
||
As a reminder, performing inference on the newly supported models and services is as simple as a call with the simple syntax introduced in 8.11:
|
||
|
||
[source,bash]
|
||
----
|
||
PUT /_inference/<task_type>/<model_id>
|
||
----
|
||
|
||
To start using Cohere embeddings with your Elastic deployment using the new inference API, https://www.elastic.co/guide/en/elasticsearch/reference/current/semantic-search-inference.html[please see this tutorial]. This functionality is in Technical Preview in 8.13.
|
||
|
||
[discrete]
|
||
==== {esql} support in the Data Visualizer
|
||
|
||
preview:[] The Data Visualizer now supports {esql}, Elastic’s new piped query language that simplifies data investigation. Run your {esql} queries in the Data Visualizer to easily explore your datasets. Choose to explore and apply your query to the entire dataset or a subset of it for speed. In 8.13 this functionality is in Technical Preview and supports keyword, text, numeric, boolean, date, and ip fields.
|
||
|
||
[role="screenshot"]
|
||
image::images/data-visualizer.png[An image of the new Data Visualizer for {esql}.]
|
||
|
||
[discrete]
|
||
==== Embed Anomaly Detection Single Metric Viewer in Dashboards
|
||
|
||
You can now easily add single metric anomaly detection charts to dashboards. Under the *Add panel* option in Dashboard’s edit mode, select Machine Learning and then the *Single metric viewer* option from the menu.
|
||
|
||
[role="screenshot"]
|
||
image::images/embed-detection.png[An image of the single metric viewer.]
|
||
|
||
[discrete]
|
||
==== AIOps: Usability enhancements
|
||
|
||
We have enhanced Pattern Analysis in AIOps so that you can expand a row and see the tokens, the regex and a few examples that give you a better sense of the pattern. In addition the syntax highlighting (font color) reflects the detected pattern. When you choose to filter a pattern in Discover’s main view, the highlighting is now consistent between the Pattern Analysis feature and Discover.
|
||
|
||
[role="screenshot"]
|
||
image::images/usability.png[An image of expanded rows.]
|
||
|
||
You can now run Log Rate Analysis from the Anomaly Explorer and the Single Metric Viewer. Click on the *Actions* cog and select *Run log rate analysis* from the menu. You will be directed to the Log Rate analysis UI in Machine Learning.
|
||
|
||
[role="screenshot"]
|
||
image::images/usability-1.png[An image of the actions menu with an arrow to run log rate analysis.]
|
||
|
||
From 8.13, you can achieve the same from the anomaly markers in the Single Metric Viewer. Click on them and the actions menu will appear.
|
||
|
||
[role="screenshot"]
|
||
image::images/single-metric-viewer.png[An image of the single metric viewer.]
|
||
|
||
[discrete]
|
||
==== Grok highlighting in the File Data Visualizer
|
||
|
||
Uploading a file through the File Data Visualizer will display the first 5 lines with inline highlighting. Hovering the mouse over displays a tooltip with the field name and type.
|
||
|
||
[role="screenshot"]
|
||
image::images/grok-highlighting.png[An image of grok highlighting.]
|
||
|
||
[discrete]
|
||
=== Security
|
||
|
||
[discrete]
|
||
==== UI improvements for managing API keys
|
||
|
||
We’ve made some improvements to the API keys management page. Going forward, you can now easily sort columns in the API keys table, making it easier for you to navigate through API keys, especially when volume is high.
|
||
|
||
We’ve also made the API key name a required field. This reduces previous bugs on this page that resulted in errors or inconsistent API key names being displayed.
|
||
|
||
[discrete]
|
||
=== Global Experience
|
||
|
||
[discrete]
|
||
==== Discover using {esql} without data views
|
||
|
||
You can now utilize {esql} without creating a data view. To expand, if you have ingested data but have not created a data view, when you navigate to *Discover* you will see a screen prompting you to create a data view, as before. Now an option is available on that screen to *Try ES|QL*.
|
||
|
||
[discrete]
|
||
==== Improved UX for Setup Guides
|
||
|
||
The setup guides you see in Kibana are now organized by solution, making it much easier to find the guide you’re looking for. Additionally, a new card was added to *Connect to the Elasticsearch API* so users with API use cases don’t have to dig through the navigation and documentation to find the connection info.
|
||
|
||
[role="screenshot"]
|
||
image::images/set-up-improvements.png[A screenshot of the home page cards.]
|
||
|
||
[discrete]
|
||
==== Live chat available from the Elastic Cloud console
|
||
|
||
You will now find live chat functionality available in the top right corner in the Elastic Cloud console, completing seamlessly availability from all locations within both Elastic Cloud and Kibana experiences.
|
||
|
||
[discrete]
|
||
==== Faster deployment creation times
|
||
|
||
In particular regions, deployment of a new cluster is nearly instantaneous, saving you about 3-5 minutes of waiting time to get started. The number of regions that provide this performance boost has increased by 5x as we strive to make this the standard experience.
|
||
|
||
|
||
|
||
|
||
|