mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 01:38:56 -04:00
[8.x] [Docs] Update nav instructions and sample data installation to accommodate for the solution views (#199163) (#199438)
# Backport This will backport the following commits from `main` to `8.x`: - [[Docs] Update nav instructions and sample data installation to accommodate for the solution views (#199163)](https://github.com/elastic/kibana/pull/199163) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"florent-leborgne","email":"florent.leborgne@elastic.co"},"sourceCommit":{"committedDate":"2024-11-08T10:10:32Z","message":"[Docs] Update nav instructions and sample data installation to accommodate for the solution views (#199163)\n\nThis PR:\r\n- updates navigation instructions to accommodate for the navigation\r\nchanges related to solution views.\r\n- updates instructions for adding sample data to rely on the\r\nintegrations page instead of the home page, that only exists with the\r\nclassic solution view\r\n- updates references to the home page to avoid confusing users using one\r\nof the new solution views\r\n\r\nCloses: https://github.com/elastic/platform-docs-team/issues/529\r\nCloses: https://github.com/elastic/platform-docs-team/issues/540","sha":"8e7fb7a77e2399e3e946bbba0462517fd7dad0f7","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","docs","v8.16.0","backport:version","v8.17.0"],"title":"[Docs] Update nav instructions and sample data installation to accommodate for the solution views","number":199163,"url":"https://github.com/elastic/kibana/pull/199163","mergeCommit":{"message":"[Docs] Update nav instructions and sample data installation to accommodate for the solution views (#199163)\n\nThis PR:\r\n- updates navigation instructions to accommodate for the navigation\r\nchanges related to solution views.\r\n- updates instructions for adding sample data to rely on the\r\nintegrations page instead of the home page, that only exists with the\r\nclassic solution view\r\n- updates references to the home page to avoid confusing users using one\r\nof the new solution views\r\n\r\nCloses: https://github.com/elastic/platform-docs-team/issues/529\r\nCloses: https://github.com/elastic/platform-docs-team/issues/540","sha":"8e7fb7a77e2399e3e946bbba0462517fd7dad0f7"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199163","number":199163,"mergeCommit":{"message":"[Docs] Update nav instructions and sample data installation to accommodate for the solution views (#199163)\n\nThis PR:\r\n- updates navigation instructions to accommodate for the navigation\r\nchanges related to solution views.\r\n- updates instructions for adding sample data to rely on the\r\nintegrations page instead of the home page, that only exists with the\r\nclassic solution view\r\n- updates references to the home page to avoid confusing users using one\r\nof the new solution views\r\n\r\nCloses: https://github.com/elastic/platform-docs-team/issues/529\r\nCloses: https://github.com/elastic/platform-docs-team/issues/540","sha":"8e7fb7a77e2399e3e946bbba0462517fd7dad0f7"}},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: florent-leborgne <florent.leborgne@elastic.co>
This commit is contained in:
Kibana Machine
GitHub
parent
a651e6d2f9
commit
418281b2d1
56 changed files with 153 additions and 152 deletions
|
|
@ -9,15 +9,11 @@ To familiarize yourself with *Canvas*, add the Sample eCommerce orders data, the
|
|||
|
||||
To create a workpad of the eCommerce store data, add the data set, then create the workpad.
|
||||
|
||||
. On the home page, click *Try sample data*.
|
||||
. <<gs-get-data-into-kibana,Install the eCommerce sample data>>.
|
||||
|
||||
. Click *Other sample data sets*.
|
||||
. Go to **Canvas** using the navigation menu or the <<kibana-navigation-search,global search field>>.
|
||||
|
||||
. On the *Sample eCommerce orders* card, click *Add data*.
|
||||
|
||||
. Open the main menu, then click *Canvas*.
|
||||
|
||||
. On the *Canvas workpads* page, click *Create workpad*.
|
||||
. Select *Create workpad*.
|
||||
|
||||
[float]
|
||||
=== Customize your workpad with images
|
||||
|
|
|
|||
|
|
@ -168,7 +168,7 @@ and field popularity data. Deleting a {data-source} does not remove any indices
|
|||
|
||||
WARNING: Deleting a {data-source} breaks all visualizations, saved searches, and other saved objects that reference the data view.
|
||||
|
||||
. Open the main menu, and then click *Stack Management > Data Views*.
|
||||
. Go to the **Data Views** management page using the navigation menu or the <<kibana-navigation-search,global search field>>.
|
||||
|
||||
. Find the {data-source} that you want to delete, and then
|
||||
click image:management/index-patterns/images/delete.png[Delete icon] in the *Actions* column.
|
||||
|
|
|
|||
|
|
@ -36,7 +36,8 @@ 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 main menu, click *Dev Tools*, then click *Grok Debugger*.
|
||||
. Find the *Grok Debugger* by navigating to the *Developer tools* page using the
|
||||
navigation menu or the <<kibana-navigation-search,global search field>>.
|
||||
. In *Sample Data*, enter a message that is representative of the data that you
|
||||
want to parse. For example:
|
||||
+
|
||||
|
|
|
|||
|
|
@ -12,7 +12,8 @@ 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 main menu, click *Dev Tools*, and then click *Painless Lab*.
|
||||
Find *Painless Lab* by navigating to the *Developer tools* page using the
|
||||
navigation menu or the <<kibana-navigation-search,global search field>>.
|
||||
|
||||
[role="screenshot"]
|
||||
image::dev-tools/painlesslab/images/painless-lab.png[Painless Lab]
|
||||
|
|
|
|||
|
|
@ -14,9 +14,8 @@ poorly performing queries much faster.
|
|||
[[search-profiler-getting-started]]
|
||||
=== Get started
|
||||
|
||||
*{searchprofiler}* is automatically enabled in {kib}. Open the main menu,
|
||||
click *Dev Tools*, and then click *{searchprofiler}*
|
||||
to get started.
|
||||
. Find the *{searchprofiler}* by navigating to the *Developer tools* page using the
|
||||
navigation menu or the <<kibana-navigation-search,global search field>>.
|
||||
|
||||
*{searchprofiler}* displays the names of the indices searched, the shards in each index,
|
||||
and how long it took for the query to complete. To try it out, replace the default `match_all` query
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ There are a couple ways to easily get data ingested into {es}.
|
|||
|
||||
The easiest is to install one or more of our available sample data packages. If you have no data, you should be
|
||||
prompted to install when running {kib} for the first time. You can also access and install the sample data packages
|
||||
by going to the home page and clicking "add sample data".
|
||||
by going to the **Integrations** page and selecting **Sample data**.
|
||||
|
||||
[discrete]
|
||||
=== makelogs script
|
||||
|
|
@ -27,5 +27,5 @@ Make sure to execute `node scripts/makelogs` *after* {es} is up and running!
|
|||
[discrete]
|
||||
=== CSV upload
|
||||
|
||||
You can also use the CSV uploader provided on the {kib} home page.
|
||||
You can also use the CSV uploader provided on the **Upload file** page available in the list of **Integrations**.
|
||||
Navigate to **Add data** > **Upload file** to upload your data from a file.
|
||||
|
|
@ -12,7 +12,7 @@ for the data and its cardinality?
|
|||
This example explores the fields in
|
||||
the <<gs-get-data-into-kibana, sample web logs data>>, or you can use your own data.
|
||||
|
||||
. Open the main menu, and click *Discover*.
|
||||
. Go to *Discover*.
|
||||
|
||||
. Expand the {data-source} dropdown, and select *Kibana Sample Data Logs*.
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ Log pattern analysis works on every text field.
|
|||
This example uses the <<gs-get-data-into-kibana, sample web logs data>>, or you
|
||||
can use your own data.
|
||||
|
||||
. Open the main menu, and click *Discover*.
|
||||
. Go to *Discover*.
|
||||
|
||||
. Expand the {data-source} dropdown, and select *Kibana Sample Data Logs*.
|
||||
|
||||
|
|
|
|||
|
|
@ -43,7 +43,7 @@ used for the saved search is also automatically selected.
|
|||
[float]
|
||||
=== Add search results to a dashboard
|
||||
|
||||
. Open the main menu, and then click *Dashboard*.
|
||||
. Go to *Dashboards*.
|
||||
. Open or create the dashboard, then click *Edit*.
|
||||
. Click *Add from library*.
|
||||
. From the *Types* dropdown, select *Saved search*.
|
||||
|
|
|
|||
|
|
@ -52,8 +52,8 @@ image::images/search-session-awhile.png[Search Session indicator displaying the
|
|||
Once you save a search session, you can start a new search,
|
||||
navigate to a different application, or close the browser.
|
||||
|
||||
. To view your saved searches, open the main menu, and then click
|
||||
*Stack Management > Search Sessions*.
|
||||
. To view your saved searches, go to the
|
||||
*Search Sessions* management page using the navigation menu or the <<kibana-navigation-search,global search field>>.
|
||||
For a saved or completed session, you can also open this view from the search sessions popup.
|
||||
|
||||
+
|
||||
|
|
|
|||
|
|
@ -113,8 +113,7 @@ To save the current search:
|
|||
. Click *Save* in the toolbar.
|
||||
. Enter a name for the search and click *Save*.
|
||||
|
||||
To import, export, and delete saved searches, open the main menu,
|
||||
then click *Stack Management > Saved Objects*.
|
||||
To import, export, and delete saved searches, go to the *Saved Objects* management page using the navigation menu or the <<kibana-navigation-search,global search field>>.
|
||||
|
||||
==== Open a saved search
|
||||
To load a saved search into Discover:
|
||||
|
|
|
|||
|
|
@ -23,10 +23,8 @@ To view the {esql} option in **Discover**, the `enableESQL` setting must be enab
|
|||
|
||||
To load the sample data:
|
||||
|
||||
. On the home page, click **Try sample data**.
|
||||
. Click **Other sample data sets**.
|
||||
. On the Sample web logs card, click **Add data**.
|
||||
. Open the main menu and select *Discover*.
|
||||
. <<gs-get-data-into-kibana,Install the web logs sample data>>.
|
||||
. Go to *Discover*.
|
||||
. Select *Try {esql}* from the application menu bar.
|
||||
|
||||
Let's say we want to find out what operating system users have and how much RAM is on their machine.
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ You can make a complete clone of a whole managed dashboard. If you clone a panel
|
|||
|
||||
To clone a dashboard:
|
||||
|
||||
. Open the main menu (≡) and click *Dashboards*.
|
||||
. Go to *Dashboards*.
|
||||
. Click on the name of the managed dashboard to view the dashboard.
|
||||
. Click *Clone* in the toolbar.
|
||||
. Click *Save and return* after editing the dashboard.
|
||||
|
|
|
|||
|
|
@ -22,18 +22,19 @@ include::{docs-root}/shared/cloud/ess-getting-started.asciidoc[]
|
|||
|
||||
[float]
|
||||
[[gs-get-data-into-kibana]]
|
||||
== Add the sample data
|
||||
== Add sample data
|
||||
|
||||
Sample data sets come with sample visualizations, dashboards, and more to help you explore {kib} before you ingest or add your own data.
|
||||
|
||||
. On the home page, click *Try sample data*.
|
||||
. Open the **Integrations** page from the navigation menu or using the <<kibana-navigation-search,global search field>>.
|
||||
|
||||
. Click *Other sample data sets*.
|
||||
. In the list of integrations, select **Sample Data**.
|
||||
|
||||
. On the *Sample eCommerce orders* card, click *Add data*.
|
||||
+
|
||||
[role="screenshot"]
|
||||
image::images/addData_sampleDataCards_8.6.0.png[Add data UI for the sample data sets]
|
||||
. On the page that opens, select *Other sample data sets*.
|
||||
|
||||
. Install the sample data sets that you want.
|
||||
|
||||
Once installed, you can access the sample data in the various {kib} apps available to you.
|
||||
|
||||
[float]
|
||||
[[explore-the-data]]
|
||||
|
|
@ -41,7 +42,7 @@ image::images/addData_sampleDataCards_8.6.0.png[Add data UI for the sample data
|
|||
|
||||
*Discover* displays the data in an interactive histogram that shows the distribution of data, or documents, over time, and a table that lists the fields for each document that matches the {data-source}. To view a subset of the documents, you can apply filters to the data, and customize the table to display only the fields you want to explore.
|
||||
|
||||
. Open the main menu, then click *Discover*.
|
||||
. Go to *Discover*.
|
||||
|
||||
. Change the <<set-time-filter, time filter>> to *Last 7 days*.
|
||||
+
|
||||
|
|
@ -67,7 +68,7 @@ image::images/availableFields_discover_8.4.0.png[Discover table that displays on
|
|||
|
||||
A dashboard is a collection of panels that you can use to visualize the data. Panels contain visualizations, interactive controls, text, and more.
|
||||
|
||||
. Open the main menu, then click *Dashboard*.
|
||||
. Go to *Dashboards*.
|
||||
|
||||
. Click *[eCommerce] Revenue Dashboard*.
|
||||
+
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ indicator is displayed:
|
|||
[role="screenshot"]
|
||||
image::images/settings-read-only-badge.png[Example of Advanced Settings Management's read only access indicator in Kibana's header]
|
||||
|
||||
To add the privilege, open the main menu, then click *Stack Management > Roles*.
|
||||
To add the privilege, go to the *Roles* management page using the navigation menu or the <<kibana-navigation-search,global search field>>.
|
||||
|
||||
For more information on granting access to {kib}, refer to <<xpack-security-authorization>>.
|
||||
|
||||
|
|
@ -30,7 +30,7 @@ For more information on granting access to {kib}, refer to <<xpack-security-auth
|
|||
|
||||
Change the settings that apply only to {kib} spaces.
|
||||
|
||||
. Open the main menu, then click *Stack Management > Advanced Settings*.
|
||||
. Go to the *Advanced settings* page using the navigation menu or the <<kibana-navigation-search,global search field>>.
|
||||
. Click *Space Settings*.
|
||||
. Scroll or search for the setting.
|
||||
. Make your change, then click *Save changes*.
|
||||
|
|
@ -644,7 +644,7 @@ Disable this option if you prefer to use the new heatmap charts with improved pe
|
|||
|
||||
Change the settings that apply only to {kib} spaces.
|
||||
|
||||
. Open the main menu, then click *Stack Management > Advanced Settings*.
|
||||
. Go to the *Advanced settings* page using the navigation menu or the <<kibana-navigation-search,global search field>>.
|
||||
. Click *Global Settings*.
|
||||
. Scroll or search for the setting.
|
||||
. Make your change, then click *Save changes*.
|
||||
|
|
|
|||
|
|
@ -285,7 +285,8 @@ IMPORTANT: Deprecated connectors will continue to function with the rules they w
|
|||
|
||||
To update a deprecated connector:
|
||||
|
||||
. Open the main menu and go to *{stack-manage-app} > {connectors-ui}*.
|
||||
. Go to the *{connectors-ui}* page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
. Select the deprecated connector to open the *Edit connector* flyout.
|
||||
. In the warning message, click *Update this connector*.
|
||||
. Complete the guided steps in the *Edit connector* flyout.
|
||||
|
|
|
|||
|
|
@ -338,7 +338,8 @@ IMPORTANT: Deprecated connectors will continue to function with the rules they w
|
|||
|
||||
To update a deprecated connector:
|
||||
|
||||
. Open the main menu and go to *{stack-manage-app} > {connectors-ui}*.
|
||||
. Go to the *{connectors-ui}* page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
. Select the deprecated connector to open the *Edit connector* flyout.
|
||||
. In the warning message, click *Update this connector*.
|
||||
. Complete the guided steps in the *Edit connector* flyout.
|
||||
|
|
|
|||
|
|
@ -66,7 +66,8 @@ Sensitive properties, such as passwords, can also be stored in the
|
|||
[[managing-preconfigured-connectors]]
|
||||
=== View preconfigured connectors
|
||||
|
||||
When you open the main menu, click *{stack-manage-app} > {connectors-ui}*.
|
||||
go to the *{connectors-ui}* page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
Preconfigured connectors appear regardless of which space you are in.
|
||||
They are tagged as “preconfigured”, and you cannot delete them.
|
||||
|
||||
|
|
|
|||
|
|
@ -39,7 +39,7 @@ then define the field values by emitting a single value using
|
|||
the {ref}/modules-scripting-painless.html[Painless scripting language].
|
||||
You can also add runtime fields in <<add-field-in-discover,*Discover*>> and <<change-the-fields,*Lens*>>.
|
||||
|
||||
. Open the main menu, then click *Stack Management > Data Views*.
|
||||
. Go to the *Data Views* management page using the navigation menu or the <<kibana-navigation-search,global search field>>.
|
||||
|
||||
. Select the data view that you want to add the runtime field to, then click *Add field*.
|
||||
|
||||
|
|
@ -162,7 +162,7 @@ else {
|
|||
|
||||
Edit the settings for runtime fields, or remove runtime fields from data views.
|
||||
|
||||
. Open the main menu, then click *Stack Management > Data Views*.
|
||||
. Go to the *Data Views* management page using the navigation menu or the <<kibana-navigation-search,global search field>>.
|
||||
|
||||
. Select the data view that contains the runtime field you want to manage, then open the runtime field edit options or delete the runtime field.
|
||||
|
||||
|
|
@ -198,7 +198,7 @@ https://www.elastic.co/blog/using-painless-kibana-scripted-fields[Using Painless
|
|||
|
||||
Create and add scripted fields to your data views.
|
||||
|
||||
. Open the main menu, then click *Stack Management > Data Views*.
|
||||
. Go to the *Data Views* management page using the navigation menu or the <<kibana-navigation-search,global search field>>.
|
||||
|
||||
. Select the data view you want to add a scripted field to.
|
||||
|
||||
|
|
@ -214,7 +214,7 @@ For more information about scripted fields in {es}, refer to {ref}/modules-scrip
|
|||
[[update-scripted-field]]
|
||||
==== Manage scripted fields
|
||||
|
||||
. Open the main menu, then click *Stack Management > Data Views*.
|
||||
. Go to the *Data Views* management page using the navigation menu or the <<kibana-navigation-search,global search field>>.
|
||||
|
||||
. Select the data view that contains the scripted field you want to manage.
|
||||
|
||||
|
|
@ -230,7 +230,7 @@ exceptions when you view the dynamically generated data.
|
|||
{kib} uses the same field types as {es}, however, some {es} field types are unsupported in {kib}.
|
||||
To customize how {kib} displays data fields, use the formatting options.
|
||||
|
||||
. Open the main menu, then click *Stack Management > Data Views*.
|
||||
. Go to the *Data Views* management page using the navigation menu or the <<kibana-navigation-search,global search field>>.
|
||||
|
||||
. Click the data view that contains the field you want to change.
|
||||
|
||||
|
|
|
|||
|
|
@ -11,14 +11,16 @@ If you need more than 30 days to complete your evaluation,
|
|||
request an extended trial at {extendtrial}.
|
||||
|
||||
To view the status of your license, start a trial, or install a new
|
||||
license, open the main menu, then click *Stack Management > License Management*.
|
||||
license, go to the *License Management* page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
|
||||
[discrete]
|
||||
=== Required permissions
|
||||
|
||||
The `manage` cluster privilege is required to access *License Management*.
|
||||
|
||||
To add the privilege, open the main menu, then click *Stack Management > Roles*.
|
||||
To add the privilege, go to the *Roles* management page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
|
||||
[discrete]
|
||||
[[license-expiration]]
|
||||
|
|
|
|||
|
|
@ -4,7 +4,8 @@
|
|||
Edit, import, export, and copy your saved objects. These objects include
|
||||
dashboards, visualizations, maps, {data-sources}, *Canvas* workpads, and other saved objects.
|
||||
|
||||
To get started, open the main menu, and then click *Stack Management > Saved Objects*.
|
||||
You can find the *Saved Objects* page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
|
||||
[role="screenshot"]
|
||||
image::images/management-saved-objects.png[Saved Objects]
|
||||
|
|
@ -14,7 +15,8 @@ image::images/management-saved-objects.png[Saved Objects]
|
|||
|
||||
To access *Saved Objects*, you must have the required `Saved Objects Management` {kib} privilege.
|
||||
|
||||
To add the privilege, open the main menu, and then click *Stack Management > Roles*.
|
||||
To add the privilege, go to the *Roles* management page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
|
||||
NOTE: Granting access to `Saved Objects Management` authorizes users to
|
||||
manage all saved objects in {kib}, including objects that are managed by
|
||||
|
|
|
|||
|
|
@ -5,7 +5,8 @@
|
|||
Use tags to categorize your saved objects,
|
||||
then filter for related objects based on shared tags.
|
||||
|
||||
To get started, open the main menu, and then click *Stack Management > Tags*.
|
||||
To get started, go to the *Tags* management page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
|
||||
[role="screenshot"]
|
||||
image::images/tags/tag-management-section.png[Tags management]
|
||||
|
|
@ -15,8 +16,8 @@ image::images/tags/tag-management-section.png[Tags management]
|
|||
|
||||
To create tags, you must meet the minimum requirements.
|
||||
|
||||
* Access to *Tags* requires the `Tag Management` Kibana privilege. To add the privilege, open the main menu,
|
||||
and then click *Stack Management > Roles*.
|
||||
* Access to *Tags* requires the `Tag Management` Kibana privilege. To add the privilege, go to the *Roles* page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
* The `read` privilege allows you to assign tags to the saved objects for which you have write permission.
|
||||
* The `write` privilege enables you to create, edit, and delete tags.
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,8 @@ an index pattern, and then rolls it into a new index. Rollup indices are a good
|
|||
way to compactly store months or years of historical data for use in
|
||||
visualizations and reports.
|
||||
|
||||
To get started, open the main menu, then click *Stack Management > Rollup Jobs*.
|
||||
You can go to the *Rollup Jobs* page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
|
||||
[role="screenshot"]
|
||||
image::images/management_rollup_list.png[List of currently active rollup jobs]
|
||||
|
|
@ -23,7 +24,8 @@ detailed information.
|
|||
|
||||
The `manage_rollup` cluster privilege is required to access *Rollup jobs*.
|
||||
|
||||
To add the privilege, open the main menu, then click *Stack Management > Roles*.
|
||||
To add the privilege, go to the *Roles* management page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
|
||||
[float]
|
||||
[[create-and-manage-rollup-job]]
|
||||
|
|
@ -142,7 +144,8 @@ rollup index, or you can remove or archive it using
|
|||
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.
|
||||
|
||||
. Open the main menu, then click *Stack Management > Data Views*.
|
||||
. Go to the *Data Views* page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
|
||||
. Click *Create data view*, and select *Rollup data view* from the dropdown.
|
||||
|
||||
|
|
@ -153,7 +156,7 @@ The notation for a combination data view with both raw and rolled up data is
|
|||
`rollup_logstash,kibana_sample_data_logs`. In this data view, `rollup_logstash`
|
||||
matches the rollup index and `kibana_sample_data_logs` matches the raw data.
|
||||
|
||||
. Open the main menu, click *Dashboard*, then *Create dashboard*.
|
||||
. Go to *Dashboards*, then select *Create dashboard*.
|
||||
|
||||
. Set the <<set-time-filter,time filter>> to *Last 90 days*.
|
||||
|
||||
|
|
|
|||
|
|
@ -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, open the main menu,
|
||||
then click *Stack Management > Watcher*.
|
||||
Go to the *Watcher* page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
With this UI, you can:
|
||||
|
||||
* <<watcher-create-threshold-alert, Create a simple threshold watch>>
|
||||
|
|
@ -39,7 +39,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 the main menu, then click *Stack Management > Roles*, or use the {api-kibana}/group/endpoint-roles[role APIs].
|
||||
To manage roles, go to the *Roles* management page, or use the {api-kibana}/group/endpoint-roles[role APIs].
|
||||
Watches are shared between all users with the same role.
|
||||
|
||||
NOTE: If you are creating a threshold watch, you must also have the `view_index_metadata` index privilege. See
|
||||
|
|
|
|||
|
|
@ -35,7 +35,8 @@ To get to the fun of visualizing and alerting on Portland public transport vehic
|
|||
[float]
|
||||
==== Step 1: Set up an Elasticsearch index
|
||||
|
||||
. In Kibana, open the main menu, then click *Dev Tools*.
|
||||
. In Kibana, go to *Developer tools* using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
. In *Console*, create the `tri_met_tracks` index lifecyle policy. This policy will keep the events in the hot data phase for 7 days. The data then moves to the warm phase. After 365 days in the warm phase, the data is deleted.
|
||||
+
|
||||
.ILM policy definition
|
||||
|
|
@ -503,7 +504,7 @@ TIP: You may want to tweak this Data View to adjust the field names and number o
|
|||
[float]
|
||||
==== Step 4: Explore the Portland TriMet data
|
||||
|
||||
. Open the main menu, and click *Discover*.
|
||||
. Go to *Discover*.
|
||||
. Set the data view to *{ems-asset-index-name}*.
|
||||
. Open the <<set-time-filter, time filter>>, and set the time range to the last 15 minutes.
|
||||
. Expand a document and explore some of the fields that you will use later in this tutorial: `trimet.bearing`, `trimet.inCongestion`, `trimet.location`, and `trimet.vehicleID`.
|
||||
|
|
@ -523,7 +524,7 @@ It's hard to get an overview of Portland vehicles by looking at individual event
|
|||
Create your map and set the theme for the default layer to dark mode.
|
||||
|
||||
|
||||
. Open the main menu, and click *Maps*.
|
||||
. Go to *Maps*.
|
||||
. Click *Create map*.
|
||||
. In the *Layers* list, click *Road map*, and then click *Edit layer settings*.
|
||||
. Open the *Tile service* dropdown, and select *Road map - dark*.
|
||||
|
|
|
|||
|
|
@ -19,8 +19,8 @@ GeoJSON is the most commonly used and flexible option.
|
|||
Follow these instructions to upload a GeoJSON data file, or try the
|
||||
<<indexing-geojson-data-tutorial, end-to-end integrated example>>.
|
||||
|
||||
. Open the main menu, click *Maps*, and then click *Add layer*.
|
||||
. Click *Uploaded GeoJSON*.
|
||||
. Go to *Maps*, and select *Add layer*.
|
||||
. Select *Uploaded GeoJSON*.
|
||||
+
|
||||
[role="screenshot"]
|
||||
image::maps/images/fu_gs_select_source_file_upload.png[]
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ To upload GeoJSON files, shapefiles, and draw features in {kib} with *Maps*, you
|
|||
* The `create` and `create_index` index privileges for destination indices
|
||||
* To use the index in *Maps*, you must also have the `read` and `view_index_metadata` index privileges for destination indices
|
||||
|
||||
To upload delimited files (such as CSV, TSV, or JSON files) on the {kib} home page, you must also have:
|
||||
To upload delimited files (such as CSV, TSV, or JSON files) from the **Upload file** integration, you must also have:
|
||||
|
||||
* The `all` {kib} privilege for *Discover*
|
||||
* The `manage_pipeline` or `manage_ingest_pipelines` cluster privilege
|
||||
|
|
@ -33,9 +33,9 @@ To upload delimited files (such as CSV, TSV, or JSON files) on the {kib} home pa
|
|||
[discrete]
|
||||
=== Upload delimited files with latitude and longitude columns
|
||||
|
||||
On the {kib} home page, you can upload a file and import it into an {es} index with latitude and longitude columns combined into a `geo_point` field.
|
||||
You can upload a file and import it into an {es} index with latitude and longitude columns combined into a `geo_point` field.
|
||||
|
||||
. Go to the {kib} home page and click *Upload a file*.
|
||||
. Go to the *Integrations* page and select *Upload file*.
|
||||
. Select a file in one of the supported file formats.
|
||||
. Click *Import*.
|
||||
. Select the *Advanced* tab.
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ refer to <<xpack-security-authorization,Granting access to {kib}>>.
|
|||
[[maps-create]]
|
||||
=== Step 1. Create a map
|
||||
|
||||
. Open the main menu, and then click *Dashboard*.
|
||||
. Go to *Dashboards*.
|
||||
. Click **Create dashboard**.
|
||||
. Set the time range to *Last 7 days*.
|
||||
. Click the **Create new Maps** icon image:maps/images/app_gis_icon.png[].
|
||||
|
|
|
|||
|
|
@ -26,12 +26,7 @@ GeoIP is a common way of transforming an IP address to a longitude and latitude.
|
|||
|
||||
You’ll use the <<get-started, web logs sample data set>> that comes with Kibana for this tutorial. Web logs sample data set has longitude and latitude. If your web log data does not contain longitude and latitude, use {ref}/geoip-processor.html[GeoIP processor] to transform an IP address into a {ref}/geo-point.html[geo_point] field.
|
||||
|
||||
To install web logs sample data set:
|
||||
|
||||
. On the home page, click *Try sample data*.
|
||||
. Expand *Other sample data sets*.
|
||||
. On the *Sample web logs* card, click *Add data*.
|
||||
|
||||
To install the web logs sample data set, refer to <<gs-get-data-into-kibana,Add sample data>>.
|
||||
|
||||
[float]
|
||||
=== Step 2: Index Combined Statistical Area (CSA) regions
|
||||
|
|
@ -46,7 +41,7 @@ To get the CSA boundary data:
|
|||
|
||||
. Go to the https://www.census.gov/geographies/mapping-files/time-series/geo/carto-boundary-file.html[Census Bureau’s website] and download the `cb_2018_us_csa_500k.zip` file.
|
||||
. Uncompress the zip file.
|
||||
. In Kibana, open the main menu, and click *Maps*.
|
||||
. In Kibana, go to *Maps*.
|
||||
. Click *Create map*.
|
||||
. Click *Add layer*.
|
||||
. Click *Upload file*.
|
||||
|
|
@ -71,7 +66,8 @@ image::maps/images/reverse-geocoding-tutorial/csa_regions.png[Map showing metro
|
|||
=== Step 3: Reverse geocoding
|
||||
To visualize CSA regions by web log traffic, the web log traffic must contain a CSA region identifier. You'll use {es} {ref}/enrich-processor.html[enrich processor] to add CSA region identifiers to the web logs sample data set. You can skip this step if your source data already contains region identifiers.
|
||||
|
||||
. Open the main menu, and then click *Dev Tools*.
|
||||
. Go to *Developer tools* using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
. In *Console*, create a {ref}/geo-match-enrich-policy-type.html[geo_match enrichment policy]:
|
||||
+
|
||||
[source,js]
|
||||
|
|
@ -142,7 +138,7 @@ PUT kibana_sample_data_logs/_settings
|
|||
}
|
||||
----------------------------------
|
||||
|
||||
. Open the main menu, and click *Discover*.
|
||||
. Go to *Discover*.
|
||||
. Set the data view to *Kibana Sample Data Logs*.
|
||||
. Open the <<set-time-filter, time filter>>, and set the time range to the last 30 days.
|
||||
. Scan through the list of *Available fields* until you find the `csa.GEOID` field. You can also search for the field by name.
|
||||
|
|
@ -158,7 +154,7 @@ image::maps/images/reverse-geocoding-tutorial/discover_enriched_web_log.png[View
|
|||
=== Step 4: Visualize Combined Statistical Area (CSA) regions by web traffic
|
||||
Now that our web traffic contains CSA region identifiers, you'll visualize CSA regions by web traffic.
|
||||
|
||||
. Open the main menu, and click *Maps*.
|
||||
. Go to *Maps*.
|
||||
. Click *Create map*.
|
||||
. Click *Add layer*.
|
||||
. Click *Choropleth*.
|
||||
|
|
|
|||
|
|
@ -85,7 +85,7 @@ Create filters from your map to focus in on just the data you want. *Maps* provi
|
|||
|
||||
To filter your dashboard by your map bounds as you pan and zoom your map:
|
||||
|
||||
. Open the main menu, and then click *Dashboard*.
|
||||
. Go to *Dashboards*.
|
||||
. Select your dashboard from the list or click *Create dashboard*.
|
||||
. If your dashboard does not have a map, add a map panel.
|
||||
. Click the gear icon image:maps/images/gear_icon.png[gear icon] to open the map panel menu.
|
||||
|
|
|
|||
|
|
@ -53,7 +53,8 @@ Any changes you make to `packs` from this field are not reflected in the UI on t
|
|||
While this allows you to use advanced Osquery functionality like pack discovery queries, you do lose the ability to manage packs defined this way from the Osquery *Packs* page.
|
||||
=========================
|
||||
|
||||
. From the {kib} main menu, click *Fleet*, then the *Agent policies* tab.
|
||||
. Go to *Fleet* using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>, then open the *Agent policies* tab.
|
||||
|
||||
. Click the name of the agent policy where you want to adjust the Osquery configuration. The configuration changes you make only apply to the policy you select.
|
||||
|
||||
|
|
@ -136,7 +137,8 @@ and Osquerybeat in the agent directory. Refer to the {fleet-guide}/installation-
|
|||
|
||||
To get more details in the logs, change the agent logging level to debug:
|
||||
|
||||
. Open the main menu, and then select **Fleet**.
|
||||
. Go to **Fleet** using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
|
||||
. Select the agent that you want to debug.
|
||||
|
||||
|
|
|
|||
|
|
@ -36,7 +36,8 @@ view live and scheduled query results, but you cannot run live queries or edit.
|
|||
To inspect hosts, run a query against one or more agents or policies,
|
||||
then view the results.
|
||||
|
||||
. Open the main menu, and then click *Osquery*.
|
||||
. Go to *Osquery* using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
. In the *Live queries* view, click **New live query**.
|
||||
. Choose to run a single query or a query pack.
|
||||
. Select one or more agents or groups to query. Start typing in the search field,
|
||||
|
|
|
|||
|
|
@ -48,9 +48,10 @@ NOTE: If you use the default settings, you can still create a custom role that g
|
|||
|
||||
. Create the reporting role.
|
||||
|
||||
.. Open the main menu, then click *Stack Management*.
|
||||
.. Go to the *Roles* management page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
|
||||
.. Click *Roles > Create role*.
|
||||
.. Click *Create role*.
|
||||
|
||||
. Specify the role settings.
|
||||
|
||||
|
|
@ -86,9 +87,10 @@ NOTE: If the *Reporting* options for application features are unavailable, and t
|
|||
|
||||
. Assign the reporting role to a user.
|
||||
|
||||
.. Open the main menu, then click *Stack Management*.
|
||||
.. Go to the *Users* management page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
|
||||
.. Click *Users*, then click the user you want to assign the reporting role to.
|
||||
.. Select the user you want to assign the reporting role to.
|
||||
|
||||
.. From the *Roles* dropdown, select *custom_reporting_user*.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,8 +6,7 @@ which are pre-packaged assets that are available for a wide array of popular
|
|||
services and platforms. With integrations, you can add monitoring for logs and
|
||||
metrics, protect systems from security threats, and more.
|
||||
|
||||
All integrations are available in a single view, and
|
||||
{kib} guides you there from the *Welcome* screen, home page, and main menu.
|
||||
All integrations are available in a single view on the **Integrations** page.
|
||||
|
||||
[role="screenshot"]
|
||||
image::images/add-integration.png[Integrations page from which you can choose integrations to start collecting and analyzing data]
|
||||
|
|
|
|||
|
|
@ -43,7 +43,8 @@ To create workpads, you must meet the minimum requirements.
|
|||
* Make sure you have sufficient privileges to create and save workpads. When the read-only indicator appears, you have insufficient privileges,
|
||||
and the options to create and save workpads are unavailable. For more information, refer to <<xpack-security-authorization,Granting access to {kib}>>.
|
||||
|
||||
To open *Canvas*, open the main menu, then click *Canvas*.
|
||||
You can open *Canvas* using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
|
||||
[float]
|
||||
[[start-with-a-blank-workpad]]
|
||||
|
|
@ -175,7 +176,7 @@ To share workpads with a larger audience, click *Share* in the toolbar. For deta
|
|||
[[export-single-workpad]]
|
||||
== Export workpads
|
||||
|
||||
Want to export multiple workpads? Go to the *Canvas* home page, select the workpads you want to export, then click *Export*.
|
||||
Want to export multiple workpads? Go to the *Canvas* page, select the workpads you want to export, then click *Export*.
|
||||
|
||||
--
|
||||
|
||||
|
|
|
|||
|
|
@ -140,13 +140,9 @@ a bar chart that displays the top five log traffic sources for every three hours
|
|||
|
||||
Add the sample web logs data that you'll use to create the bar chart, then create the dashboard.
|
||||
|
||||
. On the home page, click *Try sample data*.
|
||||
. <<gs-get-data-into-kibana,Install the web logs sample data set>>.
|
||||
|
||||
. Click *Other sample data sets*.
|
||||
|
||||
. On the *Sample web logs* card, click *Add data*.
|
||||
|
||||
. Open the main menu, then click *Dashboard*.
|
||||
. Go to *Dashboards*.
|
||||
|
||||
. On the *Dashboards* page, click *Create dashboard*.
|
||||
|
||||
|
|
|
|||
|
|
@ -289,7 +289,8 @@ To personalize your dashboards, add your own logos and graphics with the *Image*
|
|||
[role="screenshot"]
|
||||
image::images/dashboard_addImageEditor_8.7.0.png[Add image editor]
|
||||
|
||||
To manage your uploaded image files, open the main menu, then click *Stack Management > Kibana > Files*.
|
||||
To manage your uploaded image files, go to the *Files* management page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
|
||||
|
||||
[WARNING]
|
||||
|
|
|
|||
|
|
@ -16,15 +16,9 @@ Before you begin, you should be familiar with the <<kibana-concepts-analysts>>.
|
|||
|
||||
Add the sample eCommerce data, and create and set up the dashboard.
|
||||
|
||||
. On the home page, click *Try sample data*.
|
||||
. <<gs-get-data-into-kibana,Install the eCommerce sample data set>>.
|
||||
|
||||
. Expand *Other sample data sets*.
|
||||
|
||||
. On the *Sample eCommerce orders* card, click *Add data*.
|
||||
|
||||
Create the dashboard where you'll display the visualization panels.
|
||||
|
||||
. Open the main menu, then click *Dashboards*.
|
||||
. Go to *Dashboards*.
|
||||
|
||||
. On the *Dashboards* page, click *Create dashboard*.
|
||||
|
||||
|
|
|
|||
|
|
@ -88,7 +88,7 @@ Set up Metricbeat, then create the dashboard.
|
|||
|
||||
. To set up Metricbeat, go to {metricbeat-ref}/metricbeat-installation-configuration.html[Metricbeat quick start: installation and configuration]
|
||||
|
||||
. From {kib}, open the main menu, then click *Dashboard*.
|
||||
. Go to *Dashboards*.
|
||||
|
||||
. On the *Dashboards* page, click *Create dashboard*.
|
||||
|
||||
|
|
|
|||
|
|
@ -18,15 +18,9 @@ Before you begin, you should be familiar with the <<kibana-concepts-analysts>>.
|
|||
|
||||
Add the sample web logs data, and create and set up the dashboard.
|
||||
|
||||
. On the home page, click *Try sample data*.
|
||||
. <<gs-get-data-into-kibana,Install the web logs sample data set>>.
|
||||
|
||||
. Expand *Other sample data sets*.
|
||||
|
||||
. On the *Sample web logs* card, click *Add data*.
|
||||
|
||||
Create the dashboard where you'll display the visualization panels.
|
||||
|
||||
. Open the main menu, then click *Dashboards*.
|
||||
. Go to *Dashboards*.
|
||||
|
||||
. Click *Create dashboard*.
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
Learn more about building dashboards and creating visualizations with the following tutorials.
|
||||
|
||||
These tutorials use sample data available in {kib} as a way to get started more easily, but you can apply and adapt these instructions to your own data as well.
|
||||
These tutorials use <<gs-get-data-into-kibana,sample data>> available in {kib} as a way to get started more easily, but you can apply and adapt these instructions to your own data as well.
|
||||
|
||||
|
||||
include::tutorial-create-a-dashboard-of-lens-panels.asciidoc[]
|
||||
|
|
|
|||
|
|
@ -40,13 +40,9 @@ As you edit the specs, work in small steps, and frequently save your work. Small
|
|||
|
||||
Before starting, add the eCommerce sample data that you'll use in your spec, then create the dashboard.
|
||||
|
||||
. On the home page, click *Try sample data*.
|
||||
. <<gs-get-data-into-kibana,Install the eCommerce sample data set>>.
|
||||
|
||||
. Click *Other sample data sets*.
|
||||
|
||||
. On the *Sample eCommerce orders* card, click *Add data*.
|
||||
|
||||
. Open the main menu, then click *Dashboard*.
|
||||
. Go to *Dashboards*.
|
||||
|
||||
. On the *Dashboards* page, click *Create dashboard*.
|
||||
|
||||
|
|
@ -90,7 +86,8 @@ To check your work, open and use the <<console-kibana,*Console*>> on a separate
|
|||
|
||||
. Open {kib} on a new tab.
|
||||
|
||||
. Open the main menu, then click *Dev Tools*.
|
||||
. Go to the *Developer tools* page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
|
||||
. On the *Console* editor, enter the aggregation, then click *Click to send request*:
|
||||
|
||||
|
|
|
|||
|
|
@ -48,7 +48,7 @@ and <<kibana-concepts-analysts, {kib} concepts>>.
|
|||
|
||||
Tell {kib} where to find the data you want to explore, and then specify the time range in which to view that data.
|
||||
|
||||
. Open the main menu, and select **Discover**.
|
||||
. Go to **Discover**.
|
||||
|
||||
. Select the data you want to work with.
|
||||
+
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ You must index data into {es} before you can create a graph.
|
|||
[[exploring-connections]]
|
||||
=== Graph a data connection
|
||||
|
||||
. Open the main menu, then click *Graph*.
|
||||
. Go to *Graph*.
|
||||
+
|
||||
If this is your first graph, follow the prompts to create it.
|
||||
For subsequent graphs, click *New*.
|
||||
|
|
|
|||
|
|
@ -71,7 +71,7 @@ affecting the cluster.
|
|||
|
||||
Use *Graph* to reveal the relationships in your data.
|
||||
|
||||
. Open the main menu, and then click *Graph*.
|
||||
. Go to *Graph*.
|
||||
+
|
||||
If you're new to {kib}, and don't yet have any data, follow the link to add sample data.
|
||||
This example uses the {kib} sample web logs data set.
|
||||
|
|
|
|||
|
|
@ -71,8 +71,7 @@ image::images/visualization-journey.png[User data analysis journey]
|
|||
|
||||
| *1*
|
||||
| *Add data.* The best way to add data to the Elastic Stack is to use one of our many <<connect-to-elasticsearch,integrations>>.
|
||||
Alternatively, you can add a sample data set or upload a file. All three options are available
|
||||
on the home page.
|
||||
On the **Integrations** page, you can also find options to add sample data sets or to upload a file.
|
||||
|
||||
| *2*
|
||||
| *Explore.* With <<discover,*Discover*>>, you can search your data for hidden
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ in the {ref}/monitoring-production.html[{es} monitoring documentation].
|
|||
To collect {kib} monitoring data, add a {kib} integration to an {agent} and
|
||||
deploy it to the host where {kib} is running.
|
||||
|
||||
. Go to the {kib} home page and click **Add integrations**.
|
||||
. Go to the **Integrations** page.
|
||||
+
|
||||
NOTE: If you're using a monitoring cluster, use the {kib} instance connected to
|
||||
the monitoring cluster.
|
||||
|
|
|
|||
|
|
@ -49,7 +49,8 @@ By default, if you are running {kib} locally, go to `http://localhost:5601/`.
|
|||
If {security-features} are enabled, log in.
|
||||
--
|
||||
|
||||
... Open the main menu, then click *Stack Monitoring*. If data collection is
|
||||
... Go to the *Stack Monitoring* page using the
|
||||
<<kibana-navigation-search,global search field>>. If data collection is
|
||||
disabled, you are prompted to turn it on.
|
||||
|
||||
** From the Console or command line, set `xpack.monitoring.collection.enabled`
|
||||
|
|
|
|||
|
|
@ -86,7 +86,8 @@ By default, if you are running {kib} locally, go to `http://localhost:5601/`.
|
|||
If the Elastic {security-features} are enabled, log in.
|
||||
--
|
||||
|
||||
. Open the main menu, then click *Stack Monitoring*.
|
||||
. Go to the *Stack Monitoring* page using the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
+
|
||||
--
|
||||
If data collection is disabled, you are prompted to turn on data collection.
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ Create the POST URL that triggers a report to generate PDF and CSV reports.
|
|||
|
||||
To create the POST URL for PDF reports:
|
||||
|
||||
. Open the main menu, then click *Dashboard*, *Visualize Library*, or *Canvas*.
|
||||
. Go to *Dashboards*, *Visualize Library*, or *Canvas*.
|
||||
|
||||
. Open the dashboard, visualization, or **Canvas** workpad you want to view as a report.
|
||||
|
||||
|
|
@ -24,7 +24,7 @@ To create the POST URL for PDF reports:
|
|||
|
||||
To create the POST URL for CSV reports:
|
||||
|
||||
. Open the main menu, then click *Discover*.
|
||||
. Go to *Discover*.
|
||||
|
||||
. Open the saved search you want to share.
|
||||
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@ In the following dashboard, the shareable container is highlighted:
|
|||
[role="screenshot"]
|
||||
image::user/reporting/images/shareable-container.png["Shareable Container"]
|
||||
|
||||
. Open the main menu, then open the saved search, dashboard, visualization, or workpad you want to share.
|
||||
. Open the saved search, dashboard, visualization, or workpad you want to share.
|
||||
|
||||
. From the toolbar, click *Share*, then select the report option.
|
||||
|
||||
|
|
@ -94,7 +94,7 @@ include::reporting-pdf-limitations.asciidoc[]
|
|||
|
||||
Create and share JSON files for workpads.
|
||||
|
||||
. Open the main menu, then click *Canvas*.
|
||||
. Go to *Canvas*.
|
||||
|
||||
. Open the workpad you want to share.
|
||||
|
||||
|
|
@ -118,7 +118,7 @@ change {kib} sizing, {ess-console}[edit the deployment].
|
|||
|
||||
beta[] Create and securely share static *Canvas* workpads on a website. To customize the behavior of the workpad on your website, you can choose to autoplay the pages or hide the workpad toolbar.
|
||||
|
||||
. Open the main menu, then click *Canvas*.
|
||||
. Go to *Canvas*.
|
||||
|
||||
. Open the workpad you want to share.
|
||||
|
||||
|
|
@ -140,7 +140,7 @@ Display your dashboards on an internal company website or personal web page with
|
|||
|
||||
For information about granting access to embedded dashboards, refer to <<kibana-authentication>>.
|
||||
|
||||
. Open the main menu, then open the dashboard you want to share.
|
||||
. Open the dashboard you want to share.
|
||||
|
||||
. Click *Share > Embed code*.
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,8 @@ You can use {kib} to manage your different API keys:
|
|||
* Cross-cluster API key: allows other clusters to connect to this cluster.
|
||||
* Managed API key: created and managed by Kibana to run background tasks.
|
||||
|
||||
To manage API keys, open the main menu, then click *Stack Management > Security > API Keys*.
|
||||
To manage API keys, go to the *API Keys* management page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
|
||||
[role="screenshot"]
|
||||
image:images/api-keys.png["API Keys UI"]
|
||||
|
|
@ -28,13 +29,15 @@ image:images/api-keys.png["API Keys UI"]
|
|||
* To create or update a *cross-cluster API key*, you must have the `manage_security` privilege and an Enterprise license.
|
||||
* To have a read-only view on the API keys, you must have access to the page and the `read_security` cluster privilege.
|
||||
|
||||
To manage roles, open the main menu, then click *Stack Management > Security > Roles*, or use the {api-kibana}/group/endpoint-roles[role APIs].
|
||||
To manage roles, go to the *Roles* management page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>, or use the {api-kibana}/group/endpoint-roles[role APIs].
|
||||
|
||||
[float]
|
||||
[[create-api-key]]
|
||||
=== Create an API key
|
||||
|
||||
To create an API key, open the main menu, then click *Stack Management > Security > API Keys > Create API key*.
|
||||
To create an API key, go to the *API Keys* management page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>, and select *Create API key*.
|
||||
|
||||
[role="screenshot"]
|
||||
image:images/create-ccr-api-key.png["Create API Key UI"]
|
||||
|
|
@ -48,7 +51,8 @@ Refer to the {ref}/security-api-create-cross-cluster-api-key.html[create cross-c
|
|||
[[udpate-api-key]]
|
||||
=== Update an API key
|
||||
|
||||
To update an API key, open the main menu, click *Stack Management > Security > API Keys*, and then click on the name of the key. You cannot update the name or the type of API key.
|
||||
To update an API key, go to the *API Keys* management page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>, and then click on the name of the key. You cannot update the name or the type of API key.
|
||||
|
||||
Refer to the {ref}/security-api-update-api-key.html[update API key] documentation to learn more about updating user API keys.
|
||||
|
||||
|
|
|
|||
|
|
@ -21,7 +21,8 @@ The `manage_security` cluster privilege is required to access all Security featu
|
|||
[float]
|
||||
=== Users
|
||||
|
||||
To create and manage users, open the main menu, then click *Stack Management > Users*.
|
||||
To create and manage users, go to the *Users* management page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
You can also change their passwords and roles. For more information about
|
||||
authentication and built-in users, see
|
||||
{ref}/setting-up-authentication.html[Setting up user authentication].
|
||||
|
|
@ -29,7 +30,8 @@ authentication and built-in users, see
|
|||
[float]
|
||||
=== Roles
|
||||
|
||||
To manage roles, open the main menu, then click *Stack Management > Roles*, or use
|
||||
To manage roles, go to the *Roles* management page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>, or use
|
||||
the {api-kibana}/group/endpoint-roles[role APIs]. For more information on configuring roles for {kib}, see <<xpack-security-authorization,Granting access to {kib}>>.
|
||||
|
||||
For a more holistic overview of configuring roles for the entire stack,
|
||||
|
|
|
|||
|
|
@ -8,7 +8,8 @@ describe which roles to assign to your users using a set of rules.
|
|||
Role mappings are required when authenticating via an external identity provider, such as Active Directory, Kerberos, PKI, OIDC, or SAML.
|
||||
Role mappings have no effect for users inside the `native` or `file` realms.
|
||||
|
||||
To manage your role mappings, open the main menu, then click *Stack Management > Role Mappings*.
|
||||
You can find the *Role mappings* management page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
|
||||
With *Role mappings*, you can:
|
||||
|
||||
|
|
@ -27,7 +28,8 @@ The `manage_security` cluster privilege is required to manage Role Mappings.
|
|||
[float]
|
||||
=== Create a role mapping
|
||||
|
||||
. Open the main menu, then click *Stack Management > Role Mappings*.
|
||||
. Go to the *Role mappings* management page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
. Click *Create role mapping*.
|
||||
. Give your role mapping a unique name, and choose which roles you wish to assign to your users.
|
||||
+
|
||||
|
|
|
|||
|
|
@ -65,10 +65,12 @@ the `elastic` user or other built-in users, run the
|
|||
. [[kibana-roles]]Create roles and users to grant access to {kib}.
|
||||
+
|
||||
--
|
||||
To manage privileges in {kib}, open the main menu, then click *Stack Management > Roles*. The built-in `kibana_admin` role will grant
|
||||
To manage privileges in {kib}, go to the *Roles* management page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>. The built-in `kibana_admin` role will grant
|
||||
access to {kib} with administrator privileges. Alternatively, you can create additional roles that grant limited access to {kib}.
|
||||
|
||||
If you're using the default native realm with Basic Authentication, open the main menu, then click *Stack Management > Users* to create
|
||||
If you're using the default native realm with Basic Authentication, go to the *Users* management page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>> to create
|
||||
users and assign roles, or use the {es} {ref}/security-api.html#security-user-apis[user management APIs]. For example, the following creates
|
||||
a user named `jacknich` and assigns it the `kibana_admin` role:
|
||||
|
||||
|
|
|
|||
|
|
@ -52,8 +52,8 @@ Let’s work through an example together. Consider a marketing analyst who wants
|
|||
|
||||
Create a Marketing space for your marketing analysts to use.
|
||||
|
||||
. Open the main menu, and select **Stack Management**.
|
||||
. Under **{kib}**, select **Spaces**.
|
||||
. Go to the *Spaces* management page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
. Click **Create a space**.
|
||||
. Give this space a unique name. For example: `Marketing`.
|
||||
. Click **Create space**.
|
||||
|
|
@ -75,8 +75,8 @@ In this example, a marketing analyst will need:
|
|||
|
||||
To create the role:
|
||||
|
||||
. Open the main menu, and select **Stack Management**.
|
||||
. Under **Security**, select **Roles**.
|
||||
. Go to the *Roles* management page using the navigation menu or the
|
||||
<<kibana-navigation-search,global search field>>.
|
||||
. Click **Create role**.
|
||||
. Give this role a unique name. For example: `marketing_dashboards_role`.
|
||||
. For this example, you want to store all marketing data in the `acme-marketing-*` set of indices. To grant this access, locate the **Index privileges** section and enter:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue