Skip to content

Commit a3f97b4

Browse files
kertalkertal
committed
Merge upstream/master, fix conflicts
2 parents b6c6fa3 + ea84cbf commit a3f97b4

384 files changed

Lines changed: 17296 additions & 14614 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎.github/workflows/pr-project-assigner.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ jobs:
88
name: Assign a PR to project based on label
99
steps:
1010
- name: Assign to project
11-
uses: elastic/github-actions/project-assigner@v1.0.1
11+
uses: elastic/github-actions/project-assigner@v1.0.2
1212
id: project_assigner
1313
with:
1414
issue-mappings: |

‎.github/workflows/project-assigner.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ jobs:
88
name: Assign issue or PR to project based on label
99
steps:
1010
- name: Assign to project
11-
uses: elastic/github-actions/project-assigner@v1.0.1
11+
uses: elastic/github-actions/project-assigner@v1.0.2
1212
id: project_assigner
1313
with:
1414
issue-mappings: '[{"label": "Team:AppArch", "projectName": "kibana-app-arch", "columnId": 6173895}, {"label": "Feature:Lens", "projectName": "Lens", "columnId": 6219363}, {"label": "Team:Canvas", "projectName": "canvas", "columnId": 6187593}]'

‎.i18nrc.json‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,7 @@
3434
"navigation": "src/plugins/navigation",
3535
"newsfeed": "src/plugins/newsfeed",
3636
"regionMap": "src/legacy/core_plugins/region_map",
37+
"savedObjects": "src/plugins/saved_objects",
3738
"server": "src/legacy/server",
3839
"statusPage": "src/legacy/core_plugins/status_page",
3940
"telemetry": "src/legacy/core_plugins/telemetry",

‎docs/images/management-index-patterns.png‎

52 KB
Loading

‎docs/management/advanced-options.asciidoc‎

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
[[advanced-options]]
2-
== Setting advanced options
2+
== Advanced Settings
33

4-
The *Advanced Settings* page enables you to directly edit settings that control the behavior of the Kibana application.
4+
The *Advanced Settings* UI enables you to edit settings that control the behavior of Kibana.
55
For example, you can change the format used to display dates, specify the default index pattern, and set the precision
66
for displayed decimal values.
77

@@ -69,6 +69,9 @@ into the document when displaying it.
6969
`metrics:max_buckets`:: The maximum numbers of buckets that a single
7070
data source can return. This might arise when the user selects a
7171
short interval (for example, 1s) for a long time period (1 year).
72+
`pageNavigation`:: The style of navigation menu for Kibana.
73+
Choices are Individual, the legacy style where every plugin is represented in the nav,
74+
and Grouped, a new format that bundles related plugins together in nested navigation.
7275
`query:allowLeadingWildcards`:: Allows a wildcard (*) as the first character
7376
in a query clause. Only applies when experimental query features are
7477
enabled in the query bar. To disallow leading wildcards in Lucene queries,

‎docs/management/index-lifecycle-policies/intro-to-lifecycle-policies.asciidoc‎

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,30 +1,30 @@
11
[role="xpack"]
22
[[index-lifecycle-policies]]
3-
== Index lifecycle policies
3+
== Index Lifecycle Policies
44

5-
If you're working with time series data, you don't want to continually dump
6-
everything into a single index. Instead, you might periodically roll over the
7-
data to a new index to keep it from growing so big it's slow and expensive.
8-
As the index ages and you query it less frequently, you’ll likely move it to
5+
If you're working with time series data, you don't want to continually dump
6+
everything into a single index. Instead, you might periodically roll over the
7+
data to a new index to keep it from growing so big it's slow and expensive.
8+
As the index ages and you query it less frequently, you’ll likely move it to
99
less expensive hardware and reduce the number of shards and replicas.
1010

11-
To automatically move an index through its lifecycle, you can create a policy
12-
to define actions to perform on the index as it ages. Index lifecycle policies
13-
are especially useful when working with {beats-ref}/beats-reference.html[Beats]
14-
data shippers, which continually
15-
send operational data, such as metrics and logs, to Elasticsearch. You can
16-
automate a rollover to a new index when the existing index reaches a specified
17-
size or age. This ensures that all indices have a similar size instead of having
18-
daily indices where size can vary based on the number of Beats and the number
11+
To automatically move an index through its lifecycle, you can create a policy
12+
to define actions to perform on the index as it ages. Index lifecycle policies
13+
are especially useful when working with {beats-ref}/beats-reference.html[Beats]
14+
data shippers, which continually
15+
send operational data, such as metrics and logs, to Elasticsearch. You can
16+
automate a rollover to a new index when the existing index reaches a specified
17+
size or age. This ensures that all indices have a similar size instead of having
18+
daily indices where size can vary based on the number of Beats and the number
1919
of events sent.
2020

21-
{kib}’s *Index Lifecycle Policies* walks you through the process for creating
22-
and configuring a policy. Before using this feature, you should be familiar
21+
{kib}’s *Index Lifecycle Policies* walks you through the process for creating
22+
and configuring a policy. Before using this feature, you should be familiar
2323
with index lifecycle management:
2424

25-
* For an introduction, see
26-
{ref}/getting-started-index-lifecycle-management.html[Getting started with index
27-
lifecycle management].
28-
* To dig into the concepts and technical details, see
25+
* For an introduction, refer to
26+
{ref}/getting-started-index-lifecycle-management.html[Getting started with index
27+
lifecycle management].
28+
* To dig into the concepts and technical details, see
2929
{ref}/index-lifecycle-management.html[Managing the index lifecycle].
3030
* To check out the APIs, see {ref}/index-lifecycle-management-api.html[Index lifecycle management API].

‎docs/management/index-patterns.asciidoc‎

Lines changed: 5 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -89,39 +89,11 @@ pattern: `*:logstash-*`.
8989
Once an index pattern is configured using the {ccs} syntax, all searches and
9090
aggregations using that index pattern in {kib} take advantage of {ccs}.
9191

92+
9293
[float]
94+
[[reload-fields]]
9395
=== Manage your index pattern
9496

95-
Once you create an index pattern, manually or with a sample data set,
96-
you can look at its fields and associated data types.
97-
You can also perform housekeeping tasks, such as making the
98-
index pattern the default or deleting it when you longer need it.
99-
To drill down into the details of an index pattern, click its name in
100-
the *Index patterns* overview.
101-
102-
[role="screenshot"]
103-
image:management/index-patterns/images/new-index-pattern.png["Index files and data types"]
104-
105-
From the detailed view, you can perform the following actions:
106-
107-
* *Manage the index fields.* You can add formatters to format values and create
108-
scripted fields.
109-
See <<managing-fields, Managing fields>> for more information.
110-
111-
* [[set-default-pattern]]*Set the default index pattern.* {kib} uses a badge to make users
112-
aware of which index pattern is the default. The first pattern
113-
you create is automatically designated as the default pattern. The default
114-
index pattern is loaded when you open *Discover*.
115-
116-
* [[reload-fields]]*Refresh the index fields list.* You can refresh the index fields list to
117-
pick up any newly-added fields. Doing so also resets Kibana’s popularity counters
118-
for the fields. The popularity counters are used in *Discover* to sort fields in lists.
119-
120-
* [[delete-pattern]]*Delete the index pattern.* This action removes the pattern from the list of
121-
Saved Objects in {kib}. You will not be able to recover field formatters,
122-
scripted fields, source filters, and field popularity data associated with the index pattern.
123-
Deleting an index pattern does
124-
not remove any indices or data documents from {es}.
125-
+
126-
WARNING: Deleting an index pattern breaks all visualizations, saved searches, and
127-
other saved objects that reference the pattern.
97+
To drill down into the fields and associated data types in an index pattern,
98+
click its name in the *Index patterns* overview page.
99+
For more information, refer to <<managing-fields, Index Patterns and Fields>>.

‎docs/management/index-patterns/images/edit_icon.png‎

495 Bytes
Loading

‎docs/management/managing-beats.asciidoc‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
[[managing-beats]]
22
[role="xpack"]
3-
== Managing {beats}
3+
== {beats} Central Management
44

55
include::{asciidoc-dir}/../../shared/discontinued.asciidoc[tag=cm-discontinued]
66

@@ -34,14 +34,14 @@ Central Management UI.
3434

3535
You need to enroll {beats} to register them in central management and establish
3636
trust. Enrolled {beats} will have the credentials needed to retrieve
37-
configurations from {kib}.
37+
configurations from {kib}.
3838

3939
[float]
4040
=== Create configuration tags
4141

4242
A _configuration tag_ is a group of configuration blocks that you can apply to
4343
one or more {beats}. For example, you can create a tag called `development` to
44-
group configurations for {beats} running in your development environment.
44+
group configurations for {beats} running in your development environment.
4545

4646
The first time you walk through the enrollment process, you'll create a
4747
configuration tag that's applied to the {beats} instance you're enrolling.
@@ -62,7 +62,7 @@ Central management supports configuration settings for:
6262
* {filebeat} modules
6363
* {metricbeat} modules
6464
* {filebeat} inputs
65-
* {filebeat} and {metricbeat} outputs
65+
* {filebeat} and {metricbeat} outputs
6666

6767
NOTE: Central management supports the following outputs only: {es}, {ls}, Kafka,
6868
and Redis. Other output types are not supported for {beats} that are enrolled in
@@ -72,7 +72,7 @@ Use the Central Management UI to define and manage settings for supported
7272
configuration blocks. You cannot define those settings in local {beats}
7373
configuration files. For configuration blocks that are not supported by central
7474
management, configure the settings in the local configuration file after
75-
enrolling the Beat in central management.
75+
enrolling the Beat in central management.
7676

7777
[float]
7878
=== Manage enrolled {beats}

‎docs/management/managing-fields.asciidoc‎

Lines changed: 50 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,56 @@
11
[[managing-fields]]
2-
== Managing Fields
2+
== Index Patterns and Fields
33

4-
The fields for the index pattern are listed in a table. Click a column header to sort the table by that column. Click
5-
the *Controls* button in the rightmost column for a given field to edit the field's properties. You can manually set
6-
the field's format from the *Format* drop-down. Format options vary based on the field's type.
4+
The *Index patterns* UI helps you create and manage
5+
the index patterns that retrieve your data from Elasticsearch.
76

8-
You can also set the field's popularity value in the *Popularity* text entry box to any desired value. Click the
9-
*Update Field* button to confirm your changes or *Cancel* to return to the list of fields.
7+
[role="screenshot"]
8+
image::images/management-index-patterns.png[]
9+
10+
[float]
11+
=== Create an index pattern
12+
13+
An index pattern is the glue that connects Kibana to your Elasticsearch data. Create an
14+
index pattern whenever you load your own data into Kibana. To get started,
15+
click *Create index pattern*, and then follow the guided steps. Refer to
16+
<<index-patterns, Creating an index pattern>> for the types of index patterns
17+
that you can create.
18+
19+
[float]
20+
=== Manage your index pattern
21+
22+
To view the fields and associated data types in an index pattern, click its name in
23+
the *Index patterns* overview.
24+
25+
[role="screenshot"]
26+
image::management/index-patterns/images/new-index-pattern.png["Index files and data types"]
27+
28+
Use the icons in the upper right to perform the following actions:
29+
30+
* [[set-default-pattern]]*Set the default index pattern.* {kib} uses a badge to make users
31+
aware of which index pattern is the default. The first pattern
32+
you create is automatically designated as the default pattern. The default
33+
index pattern is loaded when you open *Discover*.
34+
35+
* *Refresh the index fields list.* You can refresh the index fields list to
36+
pick up any newly-added fields. Doing so also resets Kibana’s popularity counters
37+
for the fields. The popularity counters are used in *Discover* to sort fields in lists.
38+
39+
* [[delete-pattern]]*Delete the index pattern.* This action removes the pattern from the list of
40+
Saved Objects in {kib}. You will not be able to recover field formatters,
41+
scripted fields, source filters, and field popularity data associated with the index pattern.
42+
Deleting an index pattern does
43+
not remove any indices or data documents from {es}.
44+
+
45+
WARNING: Deleting an index pattern breaks all visualizations, saved searches, and
46+
other saved objects that reference the pattern.
47+
48+
[float]
49+
=== Edit a field
50+
51+
To edit a field's properties, click the edit icon
52+
image:management/index-patterns/images/edit_icon.png[] in the detail view.
53+
You can set the field's format and popularity value.
1054

1155
Kibana has field formatters for the following field types:
1256

0 commit comments

Comments
 (0)