[7.x] [DOCS] 7.10 Core UI changes (#80407) (#81491)

* [DOCS] 7.10 screenCore UI changes * Kibana access options * Removed Kibana from Set up Kibana * Removed rogue symbols * Update docs/spaces/index.asciidoc Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com> * Update docs/management/managing-beats.asciidoc Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com> * Review comments * Update docs/user/introduction.asciidoc Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com> * Review comments * Changed menu to main menu Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com>
elastic · Oct 26, 2020 · 49928b3 · 49928b3
1 parent 34a140e
commit 49928b3
Show file tree

Hide file tree

Showing 79 changed files with 186 additions and 138 deletions.
diff --git a/docs/apm/images/advanced-discover.png b/docs/apm/images/advanced-discover.png
diff --git a/docs/apm/troubleshooting.asciidoc b/docs/apm/troubleshooting.asciidoc
@@ -157,7 +157,7 @@ the values in `http.request.cookies` are not indexed and thus not searchable.
 
 *Ensure an index pattern exists*
 As a first step, you should ensure the correct index pattern exists.
-In Kibana, navigate to *Management > Kibana > Index Patterns*.
+Open the main menu, then click *Stack Management > Index Patterns*.
 In the pattern list, you should see an apm index pattern; The default is `apm-*`.
 If you don't, the index pattern doesn't exist. See <<no-apm-data-found>> for information on how to fix this problem.
 

diff --git a/docs/canvas/canvas-tutorial.asciidoc b/docs/canvas/canvas-tutorial.asciidoc
@@ -14,7 +14,7 @@ For this tutorial, you'll need to add the <<add-sample-data, Sample eCommerce or
 
 Your first step to working with Canvas is to create a workpad.
 
-. Open the menu, then go to *Canvas*.
+. Open the main menu, then click *Canvas*.
 
 . On the *Canvas workpads* page, click *Create workpad*.
 

diff --git a/docs/dev-tools/console/console.asciidoc b/docs/dev-tools/console/console.asciidoc
@@ -7,7 +7,7 @@ Console enables you to interact with the REST API of {es}. You can:
 * View API documentation
 * Get your request history
 
-To get started, open the menu, go to *Dev Tools*, then click *Console*.
+To get started, open the main menu, click *Dev Tools*, then click *Console*.
 
 [role="screenshot"]
 image::dev-tools/console/images/console.png["Console"]

diff --git a/docs/dev-tools/grokdebugger/index.asciidoc b/docs/dev-tools/grokdebugger/index.asciidoc
@@ -35,7 +35,7 @@ is automatically enabled in {kib}.
 NOTE: If you're using {stack-security-features}, you must have the `manage_pipeline`
 permission to use the Grok Debugger.
 
-. Open the menu, go to *Dev Tools*, then click *Grok Debugger*.
+. Open the main menu, click *Dev Tools*, then click *Grok Debugger*.
 . In *Sample Data*, enter a message that is representative of the data that you
 want to parse. For example:
 +

diff --git a/docs/dev-tools/painlesslab/index.asciidoc b/docs/dev-tools/painlesslab/index.asciidoc
@@ -12,6 +12,6 @@ process {ref}/docs-reindex.html[reindexed data], define complex
 <<watcher-create-advanced-watch, Watcher conditions>>,
 and work with data in other contexts.
 
-To get started, open the menu, go to *Dev Tools*, then click *Painless Lab*.
+To get started, open the main menu, click *Dev Tools*, then click *Painless Lab*.
 
 image::dev-tools/painlesslab/images/painless-lab.png[Painless Lab]
diff --git a/docs/dev-tools/searchprofiler/getting-started.asciidoc b/docs/dev-tools/searchprofiler/getting-started.asciidoc
@@ -2,7 +2,7 @@
 [[profiler-getting-started]]
 === Getting Started
 
-The {searchprofiler} is automatically enabled in {kib}. From the menu, go to *Dev Tools*, then click *Search Profiler*
+The {searchprofiler} is automatically enabled in {kib}. Open the main menu, click *Dev Tools*, then click *Search Profiler*
 to get started.
 
 {searchprofiler} displays the names of the indices searched, the shards in each index,

diff --git a/docs/discover/images/time-filter.png b/docs/discover/images/time-filter.png
diff --git a/docs/discover/search.asciidoc b/docs/discover/search.asciidoc
@@ -104,9 +104,7 @@ To save the current search:
 . Click *Save* in the Kibana toolbar.
 . Enter a name for the search and click *Save*.
 
-To import, export and delete saved searches:
-. Open the menu, then click *Stack Management.
-. From the {kib} menu, click *Saved Ojbects*.
+To import, export, and delete saved searches, open the main menu, then click *Stack Management > Saved Ojbects*.
 
 ==== Open a saved search
 To load a saved search into Discover:

diff --git a/docs/discover/set-time-filter.asciidoc b/docs/discover/set-time-filter.asciidoc
@@ -30,7 +30,7 @@ to the last 15 minutes.
 * *Refresh every* to specify an automatic refresh rate.
 +
 [role="screenshot"]
-image::images/Timepicker-View.png[Time filter menu]
+image::images/time-filter.png[Time filter menu]
 
 . To set the start and end times, click the bar next to the time filter.
 In the popup, select *Absolute*, *Relative* or *Now*, then specify the required

diff --git a/docs/fleet/images/fleet-start.png b/docs/fleet/images/fleet-start.png
diff --git a/docs/getting-started/images/add-sample-data.png b/docs/getting-started/images/add-sample-data.png
diff --git a/docs/getting-started/images/tutorial-sample-dashboard.png b/docs/getting-started/images/tutorial-sample-dashboard.png
diff --git a/docs/getting-started/images/tutorial-sample-filter.png b/docs/getting-started/images/tutorial-sample-filter.png
diff --git a/docs/getting-started/quick-start-guide.asciidoc b/docs/getting-started/quick-start-guide.asciidoc
@@ -10,8 +10,9 @@ When you've finished, you'll know how to:
 * <<view-and-analyze-the-data,Gain insight into the data with *Dashboard*.>>
 
 [float]
-=== Before you begin 
-When security is enabled, you must have `read`, `write`, and `manage` privileges on the `kibana_sample_data_*` indices. For more information, refer to {ref}/security-privileges.html[Security privileges].
+=== Required privileges
+When security is enabled, you must have `read`, `write`, and `manage` privileges on the `kibana_sample_data_*` indices. 
+For more information, refer to {ref}/security-privileges.html[Security privileges].
 
 [float]
 [[set-up-on-cloud]]
@@ -30,15 +31,15 @@ Sample data sets come with sample visualizations, dashboards, and more to help y
 . On the *Sample eCommerce orders* card, click *Add data*.
 +
 [role="screenshot"]
-image::getting-started/images/add-sample-data.png[]
+image::getting-started/images/add-sample-data.png[Add data UI]
 
 [float]
 [[explore-the-data]]
 == Explore the data
 
 *Discover* displays an interactive histogram that shows the distribution of of data, or documents, over time, and a table that lists the fields for each document that matches the index. By default, all fields are shown for each matching document.
 
-. Open the menu, then click *Discover*.
+. Open the main menu, then click *Discover*.
 
 . Change the <<set-time-filter, time filter>> to *Last 7 days*.
 +
@@ -70,7 +71,7 @@ For more information, refer to <<discover, *Discover*>>.
 
 A dashboard is a collection of panels that you can use to view and analyze the data. Panels contain visualizations, interactive controls, Markdown, and more.
 
-. Open the menu, then click *Dashboard*. 
+. Open the main menu, then click *Dashboard*. 
 
 . Click *[eCommerce] Revenue Dashboard*.
 +
@@ -83,7 +84,7 @@ image::getting-started/images/tutorial-sample-dashboard.png[]
 
 To focus in on the data you want to view on the dashboard, use filters. 
 
-. From the *Controls* visualization, make a selection from the *Manufacturer* and *Category* dropdowns, then click *Apply changes*.
+. From the *[eCommerce] Controls* panel, make a selection from the *Manufacturer* and *Category* dropdowns, then click *Apply changes*.
 +
 For example, the following dashboard shows the data for women's clothing from Gnomehouse. 
 +
@@ -103,11 +104,11 @@ For more information, refer to <<dashboard,*Dashboard*>>.
 
 [float]
 [[create-a-visualization]]
-=== Create a visualization
+=== Create a visualization panel
 
-To create a treemap that shows the top regions and manufacturers, use *Lens*, then add the treemap to the dashboard.
+To create a treemap panel that shows the top regions and manufacturers, use *Lens*, then add the treemap panel to the dashboard.
 
-. From the {kib} toolbar, click *Edit*, then click *Create new*.
+. From the toolbar, click *Edit*, then click *Create new*.
 
 . On the *New Visualization* window, click *Lens*.
 
@@ -126,7 +127,7 @@ image::getting-started/images/tutorial-visualization-dropdown.png[Visualization
 
 . On the *Save Lens visualization*, enter a title and make sure *Add to Dashboard after saving* is selected, then click *Save and return*.
 +
-The treemap appears as the last visualization on the dashboard.
+The treemap appears as the last visualization panel on the dashboard.
 +
 [role="screenshot"]
 image::getting-started/images/tutorial-final-dashboard.gif[Final dashboard with new treemap visualization]

diff --git a/docs/images/Dashboard_add_new_visualization.png b/docs/images/Dashboard_add_new_visualization.png
diff --git a/docs/images/Dashboard_add_visualization.png b/docs/images/Dashboard_add_visualization.png
diff --git a/docs/images/Dashboard_example.png b/docs/images/Dashboard_example.png
diff --git a/docs/images/Dashboard_inspect.png b/docs/images/Dashboard_inspect.png
diff --git a/docs/images/Discover-Start.png b/docs/images/Discover-Start.png
diff --git a/docs/images/intro-dashboard.png b/docs/images/intro-dashboard.png
diff --git a/docs/images/intro-data-tutorial.png b/docs/images/intro-data-tutorial.png
diff --git a/docs/images/intro-discover.png b/docs/images/intro-discover.png
diff --git a/docs/images/intro-kibana.png b/docs/images/intro-kibana.png
diff --git a/docs/management/advanced-options.asciidoc b/docs/management/advanced-options.asciidoc
@@ -6,7 +6,7 @@ behavior of Kibana. For example, you can change the format used to display dates
 specify the default index pattern, and set the precision for displayed decimal
 values.
 
-. Open the menu, then go to *Stack Management > {kib} > Advanced Settings*.
+. Open the main menu, then click *Stack Management > Advanced Settings*.
 . Scroll or search for the setting you want to modify.
 . Enter a new value for the setting.
 . Click *Save changes*.

diff --git a/docs/management/alerting/alerts-and-actions-intro.asciidoc b/docs/management/alerting/alerts-and-actions-intro.asciidoc
@@ -6,8 +6,8 @@ beta[]
 
 The *Alerts and Actions* UI lets you <<alert-management, see and control all the alerts>> in a space, and provides tools to <<connector-management, create and manage connectors>> so that alerts can trigger actions like notification, indexing, and ticketing.
 
-To manage alerting and connectors, open the menu,
-then go to *Stack Management > Alerts and Insights > Alerts and Actions*.
+To manage alerting and connectors, open the main menu,
+then click *Stack Management > Alerts and Insights > Alerts and Actions*.
 
 [role="screenshot"]
 image:management/alerting/images/alerts-and-actions-ui.png[Example alert listing in the Alerts and Actions UI]

diff --git a/docs/management/index-patterns.asciidoc b/docs/management/index-patterns.asciidoc
@@ -25,8 +25,8 @@ image::images/management-index-read-only-badge.png[Example of Index Pattern Mana
 [[settings-create-pattern]]
 === Create an index pattern
 
-When you don't have an index pattern, {kib} prompts you to create one. Or, you can open the menu, 
-then go to *Stack Management > {kib} > Index Patterns* to go directly to the *Index Patterns* UI.
+When you don't have an index pattern, {kib} prompts you to create one. Or, you can open the main menu, 
+then click *Stack Management > Index Patterns*.
 
 [role="screenshot"]
 image:management/index-patterns/images/rollup-index-pattern.png["Menu with rollup index pattern"]

diff --git a/docs/management/index-patterns/images/index-pattern-ui.png b/docs/management/index-patterns/images/index-pattern-ui.png
diff --git a/docs/management/ingest-pipelines/ingest-pipelines.asciidoc b/docs/management/ingest-pipelines/ingest-pipelines.asciidoc
@@ -7,7 +7,7 @@ pipelines that perform common transformations and
 enrichments on your data.  For example, you might remove a field,
 rename an existing field, or set a new field.
 
-You’ll find *Ingest Node Pipelines* in *Stack Management > Ingest*. With this feature, you can:
+To begin, open the main menu, then click *Stack Management > Ingest Node Pipelines*. With *Ingest Node Pipelines*, you can:
 
 * View a list of your pipelines and drill down into details.
 * Create a pipeline that defines a series of tasks, known as processors.
@@ -23,7 +23,7 @@ image:management/ingest-pipelines/images/ingest-pipeline-list.png["Ingest node p
 The minimum required permissions to access *Ingest Node Pipelines* are
 the `manage_pipeline` and `cluster:monitor/nodes/info` cluster privileges.
 
-You can add these privileges in *Stack Management > Security > Roles*.
+To add privileges, open the main menu, then click *Stack Management > Roles*.
 
 [role="screenshot"]
 image:management/ingest-pipelines/images/ingest-pipeline-privileges.png["Privileges required for Ingest Node Pipelines"]

diff --git a/docs/management/managing-beats.asciidoc b/docs/management/managing-beats.asciidoc
@@ -4,7 +4,7 @@
 
 include::{asciidoc-dir}/../../shared/discontinued.asciidoc[tag=cm-discontinued]
 
-To use {beats} Central Management UI, open the menu, go to *Stack Management > Ingest >
+To use {beats} Central Management, open the main menu, click *Stack Management >
 {beats} Central Management*, then define and
 manage configurations in a central location in {kib} and quickly deploy
 configuration changes to all {beats} running across your enterprise. For more
@@ -18,8 +18,8 @@ about central management, see the related {beats} documentation:
 This feature requires an Elastic license that includes {beats} central
 management.
 
-Don't have a license? You can start a 30-day trial. Open the menu,
-go to *Stack Management > Stack > License Management*. At the end of the trial
+Don't have a license? You can start a 30-day trial. Open the main menu, then
+click *Stack Management > License Management*. At the end of the trial
 period, you can purchase a subscription to keep using central management. For
 more information, see https://www.elastic.co/subscriptions and
 <<managing-licenses>>.

diff --git a/docs/management/managing-fields.asciidoc b/docs/management/managing-fields.asciidoc
@@ -134,7 +134,7 @@ https://www.elastic.co/blog/using-painless-kibana-scripted-fields[Using Painless
 [[create-scripted-field]]
 === Create a scripted field
 
-. Open the menu, then go to *Stack Management > {kib} > Index Patterns*
+. Open the main menu, then click *Stack Management > Index Patterns*.
 . Select the index pattern you want to add a scripted field to.
 . Go to the *Scripted fields* tab for the index pattern, then click *Add scripted field*.
 . Enter a name for the scripted field.

diff --git a/docs/management/managing-indices.asciidoc b/docs/management/managing-indices.asciidoc
@@ -19,8 +19,7 @@ This page shows you how to use *Index Management* features to:
 * Create index templates to automatically configure new data streams and
 indices.
 
-To manage your indices, open the menu, then click *Stack Management > Index
-Management*.
+To manage your indices, open the main menu, then click *Stack Management > Index Management*.
 
 [role="screenshot"]
 image::images/management_index_labels.png[Index Management UI]

diff --git a/docs/management/managing-licenses.asciidoc b/docs/management/managing-licenses.asciidoc
@@ -7,7 +7,7 @@ with no expiration date. For the full list of features, refer to
 
 If you want to try out the full set of features, you can activate a free 30-day
 trial. To view the status of your license, start a trial, or install a new
-license, open the menu, then go to *Stack Management > Stack > License Management*.
+license, open the main menu, then click *Stack Management > License Management*.
 
 NOTE: You can start a trial only if your cluster has not already activated a
 trial license for the current major product version. For example, if you have
@@ -34,7 +34,7 @@ the features that will no longer be supported if you revert to a basic license.
 
 The `manage` cluster privilege is required to access *License Management*.
 
-You can add this privilege in *Stack Management > Security > Roles*.
+To add the privilege, open the main menu, then click *Stack Management > Roles*.
 
 [discrete]
 [[update-license]]

diff --git a/docs/management/managing-saved-objects.asciidoc b/docs/management/managing-saved-objects.asciidoc
@@ -5,13 +5,7 @@ The *Saved Objects* UI helps you keep track of and manage your saved objects. Th
 store data for later use, including dashboards, visualizations, maps, index patterns,
 Canvas workpads, and more.
 
-To get started, open the menu, then go to *Stack Management > {kib} > Saved Objects*. With this UI, you can:
-
-* <<managing-saved-objects-view, View&#44; edit&#44; and delete saved objects>>
-* <<managing-saved-objects-export-objects, Import and export saved objects>>
-* <<managing-saved-objects-copy-to-space, Copy saved objects to another {kib} space>>
-* <<managing-saved-objects-object-definition, Edit the object definition>>
-
+To get started, open the main menu, then click *Stack Management > Saved Objects*. 
 
 [role="screenshot"]
 image::images/management-saved-objects.png[Saved Objects]

diff --git a/docs/management/rollups/create_and_manage_rollups.asciidoc b/docs/management/rollups/create_and_manage_rollups.asciidoc
@@ -8,11 +8,7 @@ by an index pattern, and then rolls it into a new index. Rollup indices are a go
 compactly store months or years of historical
 data for use in visualizations and reports.
 
-To get started, open the menu, then go to *Stack Management > Data > Rollup Jobs*. With this UI,
-you can:
-
-* <<create-and-manage-rollup-job, Create a rollup job>>
-* <<manage-rollup-job, Start&comma; stop&comma; and delete rollup jobs>>
+To get started, open the main menu, then click *Stack Management > Rollup Jobs*.
 
 [role="screenshot"]
 image::images/management_rollup_list.png[][List of currently active rollup jobs]
@@ -25,7 +21,7 @@ Before using this feature, you should be familiar with how rollups work.
 
 The `manage_rollup` cluster privilege is required to access *Rollup jobs*.
 
-You can add this privilege in *Stack Management > Security > Roles*.
+To add the privilege, open the main menu, then click *Stack Management > Roles*.
 
 [float]
 [[create-and-manage-rollup-job]]
@@ -137,7 +133,7 @@ Your next step is to visualize your rolled up data in a vertical bar chart.
 Most visualizations support rolled up data, with the exception of Timelion and Vega visualizations.
 
 
-. Go to *Stack Management > {kib} > Index Patterns*.
+. Open the main menu, then click *Stack Management > Index Patterns*.
 
 . Click *Create index pattern*, and select *Rollup index pattern* from the dropdown.
 +
@@ -152,7 +148,7 @@ is `rollup_logstash,kibana_sample_data_logs`. In this index pattern, `rollup_log
 matches the rolled up index pattern and `kibana_sample_data_logs` matches the index
 pattern for raw data.
 
-. Go to *Dashboard* and create a vertical bar chart.
+. Open the main menu, click *Dashboard*, then create and add a vertical bar chart.
 
 . Choose `rollup_logstash,kibana_sample_data_logs`
 as your source to see both the raw and rolled up data.

diff --git a/docs/management/snapshot-restore/index.asciidoc b/docs/management/snapshot-restore/index.asciidoc
@@ -8,7 +8,7 @@ Snapshots are important because they provide a copy of your data in case
 something goes wrong. If you need to roll back to an older version of your data,
 you can restore a snapshot from the repository.
 
-To get started, open the menu, then go to *Stack Management > Data > Snapshot and Restore*.
+To get started, open the main menu, then click *Stack Management > Snapshot and Restore*.
 With this UI, you can:
 
 * Register a repository for storing your snapshots
@@ -32,7 +32,7 @@ The minimum required permissions to access *Snapshot and Restore* include:
 * Cluster privileges: `monitor`, `manage_slm`, `cluster:admin/snapshot`, and `cluster:admin/repository`
 * Index privileges: `all` on the `monitor` index if you want to access content in the *Restore Status* tab
 
-To add privileges, open the menu, then go to *Stack Management > Security > Roles*.
+To add privileges, open the main menu, then click *Stack Management > Roles*.
 
 [role="screenshot"]
 image:management/snapshot-restore/images/snapshot_permissions.png["Edit Role"]
@@ -191,7 +191,7 @@ your master and data nodes.  You can do this in one of two ways:
 Use *Snapshot and Restore* to register the repository where your snapshots
 will live.
 
-. Open the menu, then go to *Stack Management > Data > Snapshot and Restore*.
+. Open the main menu, then click *Stack Management > Snapshot and Restore*.
 . Click *Register a repository* in either the introductory message or *Repository view*.
 . Enter a name for your repository, for example, `my_backup`.
 . Select *Shared file system*.
@@ -212,7 +212,7 @@ The repository currently doesn’t have any snapshots.
 ==== Add a snapshot to the repository
 Use the {ref}/snapshots-take-snapshot.html[snapshot API] to create a snapshot.
 
-. Open the menu, go to *Dev Tools*, then select *Console*.
+. Open the main menu, click *Dev Tools*, then select *Console*.
 . Create the snapshot:
 +
 [source,js]

diff --git a/docs/management/upgrade-assistant/index.asciidoc b/docs/management/upgrade-assistant/index.asciidoc
@@ -4,7 +4,7 @@
 
 The Upgrade Assistant helps you prepare for your upgrade to the next major {es} version.
 For example, if you are using 6.8, the Upgrade Assistant helps you to upgrade to 7.0.
-To access the assistant, open the menu, then go to *Stack Management > Stack > Upgrade Assistant*.
+To access the assistant, open the main menu, then click *Stack Management > Upgrade Assistant*.
 
 The assistant identifies the deprecated settings in your cluster and indices
 and guides you through the process of resolving issues, including reindexing.
@@ -19,7 +19,7 @@ For example, if you want to upgrade to to 7.0, make sure that you are using 6.8.
 The `manage` cluster privilege is required to access the *Upgrade assistant*.
 Additional privileges may be needed to perform certain actions.
 
-You can add this privilege in *Stack Management > Security > Roles*.
+To add the privilege, open the main menu, then click *Stack Management > Roles*.
 
 [float]
 === Reindexing

diff --git a/docs/management/watcher-ui/index.asciidoc b/docs/management/watcher-ui/index.asciidoc
@@ -8,8 +8,8 @@ Watches are helpful for analyzing mission-critical and business-critical
 streaming data. For example, you might watch application logs for performance
 outages or audit access logs for security threats.
 
-To get started with the Watcher UI, open then menu,
-then go to *Stack Management > Alerts and Insights > Watcher*.
+To get started, open then main menu,
+then click *Stack Management > Watcher*.
 With this UI, you can:
 
 * <<watcher-create-threshold-alert, Create a simple threshold watch>>
@@ -41,7 +41,7 @@ and either of these watcher roles:
 * `watcher_admin`. You can perform all Watcher actions, including create and edit watches.
 * `watcher_user`. You can view watches, but not create or edit them.
 
-To manage roles, open then menu, then go to *Stack Management > Security > Roles*, or use the
+To manage roles, open then main menu, then click *Stack Management > Roles*, or use the
 <<role-management-api, Kibana Role Management API>>. Watches are shared between
 all users with the same role.