Skip to content
Merged
Show file tree
Hide file tree
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added docs/images/management_basic_license.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/images/management_index_bulk.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/images/management_watcher_assistant.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
135 changes: 133 additions & 2 deletions docs/release-notes/highlights-6.3.0.asciidoc
Original file line number Diff line number Diff line change
@@ -1,9 +1,140 @@
[[release-highlights-6.3.0]]
== 6.3.0 release highlights
== 6.3.0 Release Highlights
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought we used sentence case for titles?

++++
<titleabbrev>6.3.0</titleabbrev>
++++

coming[6.3.0]

See also <<breaking-changes>> and <<release-notes-6.3.0>>.
Each release of {kib} brings new features and product improvements.
Here are the highlights of the features that were added in 6.3 and
how the user experience improved.

Refer to the <<release-notes-6.3.0,6.3.0 Release Notes>> for a list bug
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: I'm not sure if the title is necessary here. I think if you just list <<release-notes-6.3.0>>, it'll automatically pull the title from the corresponding doc so they are guaranteed to be consistent.

This is true of pretty much all the <<>> links in this file.

fixes and other changes.

[float]
=== License management and {xpack} code

Starting with version 6.3, all of the free {xpack} features, such
as monitoring, tile maps, Grok Debugger, and Search Profiler,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit : we should either capitalize Monitoring , Tile maps just like Grok Debugger and Search Profiler - or make everything start with small letters?

ship with the default distribution of {kib}. When you install {kib},
it generates a Basic license with no expiration date.

You can view the status of your license, install a new license,
or start a 30-day trial of https://www.elastic.co/subscriptions[Platinum features]
in *Management > License Management*.
The trial enables you to try out features such as
security, machine learning, alerting,
graph capabilities,
and more.

At the end of the trial period, your license reverts to a Basic license.
To continue using the Platinum features, you can purchase a
https://www.elastic.co/subscriptions[subscription] and update
you license.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo: you -> your


[role="screenshot"]
image::images/management_basic_license.png[]

[float]
=== Autocomplete and simple syntax

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know if we need to explicitly call out simple syntax, I think something like Query Autocomplete would suffice. Alona has been focusing on this, @AlonaNadler what do you think?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, I think if we're going to show a screenshot of anything in these release highlights, it should be this. This is probably the largest feature in the release.


{kib}'s experimental autocomplete and simple syntax features
can help you create queries. To turn on these features,
click *Options* on the right of the query bar
and opt in.

Once enabled, just start typing in the query bar,
and you'll get suggestions for fields,
values for keyword fields, and query operators.
For information on the simplified, easier-to-use syntax, see
<<kuery-query, {kib} Query Language Enhancements>>.



[float]
=== Return to recently viewed content

{kib} now keeps track of your recently viewed
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: It looks like new lines are created arbitrarily throughout this doc, and I'm not sure why that is. I think we usually hard wrap at 80 characters.

items so that you can easily get back to them. Here's how:

* Your last five recently viewed items are listed
at the top of the Home page. A dropdown menu
provides access to views further back in
history.

* Your recently selected time ranges are listed
in the Recent tab in the time picker.


[float]
=== Smaller grid dimensions for dashboards

{kib} 6.3 gives you more control over panel sizes when
creating a dashboard. This gives you better control over
the layout. Here are the changes:

* The grid height of the dashboard was decreased from 100 pixels to 20
pixels.

* The number of columns in the grid was increased from 12 pixels to
48 pixels.


[float]
=== Chained Input Controls

The <<controls,Controls>> visualization now enables you to chain dropdown menus.
When chained, the value selected in the first menu
filters the terms in the second menu. A chained menu
is only enabled when its ancestor controls have values.

[float]
=== Index Management UI

The new <<managing-indices,Index management>> UI enables you to view index settings, mappings,
and statistics and perform management operations. These include refreshing,
flushing, clearing the cache, merging segments, and closing or deleting indices.
The UI provides a convenient way to perform bulk operations on multiple indices.

[role="screenshot"]
image::images/management_index_bulk.png[Index Management UI]

[float]
=== Interactive map support in Vega

You can now use the <<vega-graph, Vega visualization plugin>> to overlay
a geographic data visualization on a map. To start a Vega visualization,
open the Visualization application and click the *+* button. Scroll to the
*Others* section and select *Vega*.

[float]
=== Easily enable monitoring from the UI

In 6.3, the first time you open {kib} monitoring, data collection is disabled,
and you'll be prompted to turn it on. If you have permission to turn
on data collection, and there is data in the cluster, {kib} displays the
monitoring dashboards. If {kib} can't activate monitoring, you'll get a message
with suggestions to try.

[float]
=== Enhancements to the console

The autocomplete function in the Dev tools console
is now expanded to use {kib} and Basic {xpack} APIs.
This ensures that autocomplete covers the same use cases as the query bar
and other areas of {kib}.

[float]
=== APM Watcher Assistant

The new *Watcher assistant* UI enables
you to easily generate watches that alert you to errors in
your APM data. You can specify an error group occurrence threshold
and a trigger schedule. At a fixed interval (minutes/hours/daily),
you will get an email or slack notification if
an error group has more than the specified number of occurrences.

[role="screenshot"]
image::images/management_watcher_assistant.png[Index Management UI]