Skip to content

Commit a7ac1d1

Browse files
kibanamachinekibanamachine
authored
Merge branch '7.x' into backport/7.x/pr-93282
2 parents a881eae + b528e66 commit a7ac1d1

12 files changed

Lines changed: 86 additions & 45 deletions

File tree

‎dev_docs/kibana_server_core_components.mdx‎

Lines changed: 2 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,30 +1,16 @@
11
---
22
id: kibServerAndCoreComponents
33
slug: /kibana-dev-docs/core-intro
4-
title: Core components
4+
title: Kibana Server and Core components
55
summary: An introduction to the Kibana server and core components.
66
date: 2021-02-26
77
tags: ['kibana','onboarding', 'dev', 'architecture']
88
---
99

1010
Core is a set of systems (frontend, backend etc.) that Kibana and its plugins are built on top of.
1111

12-
## Integration with the "legacy" Kibana
13-
14-
Most of the existing core functionality is still spread over "legacy" Kibana and it will take some time to upgrade it.
15-
Kibana is started using existing "legacy" CLI that bootstraps `core` which in turn creates the "legacy" Kibana server.
16-
At the moment `core` manages HTTP connections, handles TLS configuration and base path proxy. All requests to Kibana server
17-
will hit HTTP server exposed by the `core` first and it will decide whether request can be solely handled by the new
18-
platform or request should be proxied to the "legacy" Kibana. This setup allows `core` to gradually introduce any "pre-route"
19-
processing logic, expose new routes or replace old ones handled by the "legacy" Kibana currently.
20-
21-
Once config has been loaded and some of its parts were validated by the `core` it's passed to the "legacy" Kibana where
22-
it will be additionally validated so that we can make config validation stricter with the new config validation system.
23-
Even though the new validation system provided by the `core` is also based on Joi internally it is complemented with custom
24-
rules tailored to our needs (e.g. `byteSize`, `duration` etc.). That means that config values that were previously accepted
25-
by the "legacy" Kibana may be rejected by the `core` now.
26-
2712
### Logging
2813
`core` has its own <DocLink id="kibCoreLogging" text="logging system"/> and will output log records directly (e.g. to file or terminal) when configured. When no specific configuration is provided, logs are forwarded to the "legacy" Kibana so that they look the same as the rest of the
2914
log records throughout Kibana.
3015

16+
<DocBadgeComingSoon tipTitle="Other core components" tipContent="I will be content on the other components offered by core">Other components</DocBadgeComingSoon>

‎docs/discover/images/discover-add-filter.png‎

91.7 KB
Loading

‎docs/discover/images/discover-maps.png‎

401 KB
Loading

‎docs/discover/images/discover-save-saved-search.png‎

78.8 KB
Loading

‎docs/discover/images/discover-search-field.png‎

12.6 KB
Loading

‎docs/discover/images/discover-sidebar-available-fields.png‎

38.5 KB
Loading

‎docs/discover/images/discover-visualize.png‎

77.8 KB
Loading

‎docs/discover/images/geoip-icon.png‎

5.53 KB
Loading

‎docs/user/discover.asciidoc‎

Lines changed: 56 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,29 @@
33

44
[partintro]
55
--
6-
**_Tell {kib} where to find your data, then search and filter it for hidden insights and relationships._**
6+
**_Gain insight to your data._**
7+
8+
*Discover* enables you to quickly search and filter your data, get information
9+
about structure of the fields, and visualize your data with *Lens* and *Maps*.
10+
You can customize and save your searches and place them on a dashboard.
11+
12+
++++
13+
<script type="text/javascript" async src="https://play.vidyard.com/embed/v4.js">
14+
</script>
15+
<img
16+
style="width: 100%; margin: auto; display: block;"
17+
class="vidyard-player-embed"
18+
src="https://play.vidyard.com/c2qBPz74BU16ncbvDWGvbz.jpg"
19+
data-uuid="c2qBPz74BU16ncbvDWGvbz"
20+
data-v="4"
21+
data-type="inline"
22+
/>
23+
++++
724

8-
You’ve added your data, and now you’re ready to dig in. You have questions about your data.
25+
[float]
26+
=== Explore and query your data
27+
28+
You have questions about your data.
929
What pages on your website contain a
1030
specific word or phrase? What events were logged most recently?
1131
What processes take longer than 500 milliseconds to respond?
@@ -23,9 +43,6 @@ that summarize the contents of the data.
2343
At the end of this tutorial, you’ll be ready to start exploring with your own
2444
data in *Discover*.
2545

26-
[role="screenshot"]
27-
image::images/Discover-Start.png[Discover]
28-
2946

3047
[float]
3148
=== Prerequisites
@@ -36,24 +53,6 @@ image::images/Discover-Start.png[Discover]
3653
- You should have an understanding of {ref}/documents-indices.html[{es} documents and indices].
3754

3855

39-
[float]
40-
[[whats-you-goal-in-discover]]
41-
=== Define your goal
42-
43-
When you explore your data in **Discover**, it's common to start with one or two goals:
44-
45-
- **Get an overview of what is happening.**
46-
For example, you might look for
47-
information on the overall health and performance of your ecommerce business,
48-
and then share your findings in a report.
49-
50-
- **Find an answer to a specific question.** You want
51-
to determine your customers' shopping preferences,
52-
and then visualize your findings on a dashboard.
53-
54-
For this tutorial, your goal is to better manage your product inventory. You want to
55-
know the top-selling products and on what day of the week these products sell the most.
56-
5756
[float]
5857
[[find-the-data-you-want-to-use]]
5958
=== Find your data
@@ -90,6 +89,9 @@ which can be overwhelming. You’ll modify this table to display only your field
9089

9190
. Scan through the list of **Available fields** to see
9291
what’s in your data. You can also search for a field by name.
92+
+
93+
[role="screenshot"]
94+
image:images/discover-sidebar-available-fields.png[Fields list that displays the top five search results, width=50%]
9395

9496
. Find the `manufacturer` field, and then click it to view the five most popular values for that field.
9597
+
@@ -114,7 +116,13 @@ column header, and then use the move and sort controls.
114116

115117
One of the unique capabilities of **Discover** is the ability to combine
116118
free text search with filtering based on structured data.
117-
To search all fields, enter a simple string in the **Search** field. To search particular fields and
119+
To search all fields, enter a simple string in the **Search** field.
120+
121+
[role="screenshot"]
122+
image:images/discover-search-field.png[Search field in Discover]
123+
124+
125+
To search particular fields and
118126
build more complex queries, use the <<kuery-query,Kibana Query language>>.
119127
As you type, KQL prompts you with the fields you can search and the operators
120128
you can use to build a structured query.
@@ -137,6 +145,9 @@ You can filter results to include or exclude specific fields, filter for a value
137145
and more. The **Add filter** popup prompts you with the fields you can filter
138146
and the operators you can use.
139147

148+
[role="screenshot"]
149+
image:images/discover-add-filter.png[Add filter dialog in Discover]
150+
140151
Exclude documents where day of week is not Wednesday:
141152

142153
. Click **Add filter**.
@@ -178,6 +189,9 @@ Saving a search saves the query and the filters.
178189
. In the toolbar, click **Save**.
179190

180191
. Give your search a title, and then click **Save**.
192+
+
193+
[role="screenshot"]
194+
image:images/discover-save-saved-search.png[Save saved search in Discover, width=50%]
181195

182196
[float]
183197
=== Visualize your findings
@@ -186,6 +200,9 @@ visualize it from **Discover**.
186200

187201
. From the **Selected fields** list, click `day_of_week`, and then click **Visualize**.
188202
+
203+
[role="screenshot"]
204+
image:images/discover-visualize.png[Discover sidebar field popover with visualize button, width=75%]
205+
+
189206
{kib} creates a visualization best suited for this field.
190207

191208
. Drag `manufacturer.keyword` from the field list and drop it on
@@ -196,11 +213,26 @@ image:images/visualize-from-discover.png[Visualization that opens from Discover
196213

197214
. Save your visualization for use on a dashboard.
198215

216+
If your documents contain geo point fields (image:images/geoip-icon.png[Geo point field icon, width=20px]), you can visualize them in **Maps**.
217+
218+
. Make sure the index pattern is set to **kibana_sample_data_ecommerce** and the configured time range
219+
contains data.
220+
221+
. From the **Available fields** list, click `geoip.location`, and then click **Visualize**.
222+
+
223+
[role="screenshot"]
224+
image:images/discover-maps.png[Map containing documents]
225+
226+
. Save your map for use on a dashboard.
227+
228+
199229
[float]
200230
=== What’s next?
201231

202232
* <<kuery-query, Learn more about the structure of a KQL query>>.
203233

234+
* <<discover-search-for-relevance, Search for relevance>>.
235+
204236
* <<kibana-discover-settings, Configure Discover>> to better meet your needs.
205237
In **Advanced Settings**, you can configure the number of documents to show,
206238
the table columns that display by default, and more.
@@ -209,8 +241,6 @@ the table columns that display by default, and more.
209241

210242
* <<reporting-getting-started, Present your findings in a report>>.
211243

212-
* <<discover-search-for-relevance, Search for relevance>>.
213-
214244
--
215245

216246
include::{kib-repo-dir}/management/index-patterns.asciidoc[]

‎src/core/server/ui_settings/saved_objects/migrations.ts‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,34 @@ export const migrations = {
2828
}),
2929
references: doc.references || [],
3030
}),
31+
'7.12.0': (doc: SavedObjectUnsanitizedDoc<any>): SavedObjectSanitizedDoc<any> => ({
32+
...doc,
33+
...(doc.attributes && {
34+
attributes: Object.keys(doc.attributes).reduce((acc, key) => {
35+
if (key === 'timepicker:quickRanges' && doc.attributes[key].indexOf('section') > -1) {
36+
const ranges = JSON.parse(doc.attributes[key]).map(
37+
({ from, to, display }: { from: string; to: string; display: string }) => {
38+
return {
39+
from,
40+
to,
41+
display,
42+
};
43+
}
44+
);
45+
return {
46+
...acc,
47+
'timepicker:quickRanges': JSON.stringify(ranges, null, 2),
48+
};
49+
} else {
50+
return {
51+
...acc,
52+
[key]: doc.attributes[key],
53+
};
54+
}
55+
}, {}),
56+
}),
57+
references: doc.references || [],
58+
}),
3159
'7.13.0': (doc: SavedObjectUnsanitizedDoc<any>): SavedObjectSanitizedDoc<any> => ({
3260
...doc,
3361
...(doc.attributes && {

0 commit comments

Comments
 (0)