You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Scripted fields compute data on the fly from the data in your Elasticsearch indices. Scripted field data is shown on
110
-
the Discover tab as part of the document data, and you can use scripted fields in your visualizations.
111
-
Scripted field values are computed at query time so they aren't indexed and cannot be searched using Kibana's default
112
-
query language. However they can be queried using Kibana's new <<kuery-query, experimental query language>>. Scripted
113
-
fields are also supported in the filter bar.
109
+
Scripted fields compute data on the fly from the data in your {es} indices. The data is shown on
110
+
the Discover tab as part of the document data, and you can use scripted fields in your visualizations. You query scripted fields with the <<kuery-query, {kib} query language>>, and can filter them using the filter bar. The scripted field values are computed at query time, so they aren't indexed and cannot be searched using the {kib} default
111
+
query language.
114
112
115
113
WARNING: Computing data on the fly with scripted fields can be very resource intensive and can have a direct impact on
116
-
Kibana's performance. Keep in mind that there's no built-in validation of a scripted field. If your scripts are
114
+
{kib} performance. Keep in mind that there's no built-in validation of a scripted field. If your scripts are
117
115
buggy, you'll get exceptions whenever you try to view the dynamically generated data.
118
116
119
-
When you define a scripted field in Kibana, you have a choice of scripting languages. Starting with 5.0, the default
117
+
When you define a scripted field in {kib}, you have a choice of scripting languages. In 5.0 and later, the default
120
118
options are {ref}/modules-scripting-expression.html[Lucene expressions] and {ref}/modules-scripting-painless.html[Painless].
121
-
While you can use other scripting languages if you enable dynamic scripting for them in Elasticsearch, this is not recommended
119
+
While you can use other scripting languages if you enable dynamic scripting for them in {es}, this is not recommended
122
120
because they cannot be sufficiently {ref}/modules-scripting-security.html[sandboxed].
123
121
124
-
WARNING: Use of Groovy, JavaScript, and Python scripting is deprecated starting in Elasticsearch 5.0, and support for those
125
-
scripting languages will be removed in the future.
122
+
WARNING: In 5.0 and later, Groovy, JavaScript, and Python scripting are deprecated and unsupported.
126
123
127
124
You can reference any single value numeric field in your expressions, for example:
128
125
129
126
----
130
127
doc['field_name'].value
131
128
----
132
129
133
-
For more background on scripted fields and additional examples, refer to this blog:
134
-
https://www.elastic.co/blog/using-painless-kibana-scripted-fields[Using Painless in Kibana scripted fields]
130
+
For more information on scripted fields and additional examples, refer to
131
+
https://www.elastic.co/blog/using-painless-kibana-scripted-fields[Using Painless in {kib} scripted fields]
135
132
136
133
[float]
137
134
[[create-scripted-field]]
138
-
=== Creating a Scripted Field
139
-
To create a scripted field:
135
+
=== Create a scripted field
140
136
141
-
. Go to *Management > Kibana > Index Patterns*
137
+
. Go to *Management > {kib} > Index Patterns*
142
138
. Select the index pattern you want to add a scripted field to.
143
-
. Go to the pattern's *Scripted fields* tab.
144
-
. Click *Add scripted field*.
139
+
. Go to the *Scripted fields* tab for the index pattern, then click *Add scripted field*.
145
140
. Enter a name for the scripted field.
146
141
. Enter the expression that you want to use to compute a value on the fly from your index data.
147
142
. Click *Create field*.
148
143
149
-
For more information about scripted fields in Elasticsearch, see
144
+
For more information about scripted fields in {es}, see
150
145
{ref}/modules-scripting.html[Scripting].
151
146
152
147
[float]
153
148
[[update-scripted-field]]
154
-
=== Updating a Scripted Field
155
-
To modify a scripted field:
149
+
=== Update a scripted field
156
150
157
-
. Go to *Management > Kibana > Index Patterns*
158
-
. Click the index pattern's *Scripted fields* tab.
151
+
. Go to *Management > {kib} > Index Patterns*
152
+
. Click the *Scripted fields* tab for the index pattern.
159
153
. Click the *Edit* button for the scripted field you want to change.
160
-
. Make your changes and then click *Save field* to update the field.
154
+
. Make your changes, then click *Save field*.
161
155
162
-
WARNING: Keep in mind that there's no built-in validation of a scripted field. If your scripts are buggy, you'll get
156
+
WARNING: Built-in validation is unsupported for scripted fields. If your scripts are buggy, you'll get
163
157
exceptions whenever you try to view the dynamically generated data.
164
158
165
159
[float]
166
160
[[delete-scripted-field]]
167
-
=== Deleting a Scripted Field
168
-
To delete a scripted field:
161
+
=== Delete a scripted field
169
162
170
-
. Go to *Management > Kibana > Index Patterns*
171
-
. Click the index pattern's *Scripted fields* tab.
172
-
. Click the *Delete* button for the scripted field you want to remove.
173
-
. Click *Delete* in the confirmation window.
163
+
. Go to *Management > {kib} > Index Patterns*
164
+
. Click the *Scripted fields* tab for the index pattern.
165
+
. Click *Delete* for the scripted field you want to remove.
Copy file name to clipboardExpand all lines: docs/visualize/tilemap.asciidoc
+4-106Lines changed: 4 additions & 106 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,116 +1,14 @@
1
-
[[visualize-maps]]
2
-
== Maps
3
-
4
-
To tell a story and answer questions about your geographical data, you can create several types of interactive maps with Visualize.
5
-
6
-
Visualize supports the following maps:
7
-
8
-
* *Coordinate* — Display latitude and longitude coordinates that are associated to the specified bucket aggregation.
9
-
10
-
* *Region* — Display colored boundary vector shapes using a gradient. Darker colors indicate larger values, and lighter colors indicate smaller values.
11
-
12
-
* *Heat* — Display graphical representations of data where the individual values are represented by colors.
13
-
14
-
NOTE: The maps in Visualize have been replaced with <<maps>>, which offers more functionality.
15
-
16
-
[float]
17
-
[[coordinate-map]]
18
-
=== Coordinate map
19
-
20
-
Use a coordinate map when your data set includes latitude and longitude values. For example, use a coordinate map to see the varying popularity of destination airports using the sample flight data.
Configure the `kibana.yml` settings and add the aggregations.
30
-
31
-
. Configure the following `kibana.yml` settings:
32
-
33
-
* Set `xpack.maps.showMapVisualizationTypes` to `true`.
34
-
35
-
* To use a tile service provider for coordinate maps other than https://www.elastic.co/elastic-maps-service[Elastic Maps Service], configure the <<tilemap-settings,tilemap settings>>.
36
-
37
-
. To display your data on the coordinate map, use the following aggregations:
* *Precision* slider — Determines the granularity of the results displayed on the map. To show the *Precision* slider, deselect *Change precision on map zoom*. For information on the area specified by each precision level, refer to {ref}/search-aggregations-bucket-geohashgrid-aggregation.html#_cell_dimensions_at_the_equator[geohash grid].
46
-
+
47
-
NOTE: Higher precisions increase memory usage for the browser that displays {kib} and the underlying
48
-
{es} cluster.
49
-
50
-
* *Place markers off grid (use {ref}/search-aggregations-metrics-geocentroid-aggregation.html[geocentroid])* — When you selected, the markers are
51
-
placed in the center of all documents in the bucket, and a more accurate visualization is created. When deselected, the markers are placed in the center
52
-
of the geohash grid cell.
53
-
+
54
-
NOTE: When you have multiple values in the geo_point, the coordinate map is unable to accurately calculate the geo_centroid.
55
-
56
-
[float]
57
-
[[navigate-coordinate-map]]
58
-
==== Navigate the coordinate map
59
-
60
-
To navigate the coordinate map, use the navigation options.
61
-
62
-
* To move the map center, click and hold anywhere on the map and move the cursor.
63
-
64
-
* To change the zoom level, click *Zoom In* or *Zoom out* image:images/viz-zoom.png[].
65
-
66
-
* To automatically crop the map boundaries to the
67
-
geohash buckets that have at least one result, click *Fit Data Bounds* image:images/viz-fit-bounds.png[].
68
-
69
-
[float]
70
-
[[region-map]]
71
-
=== Region map
72
-
73
-
Use region maps when you want to show statistical data on a geographic area, such as a county, country, province, or state. For example, use a region map if you want to see the average sales for each country with the sample eCommerce order data.
74
-
75
-
[role="screenshot"]
76
-
image::images/visualize_region_map_example.png[]
77
-
78
-
[float]
79
-
[[build-region-maps]]
80
-
==== Build a region map
81
-
82
-
Configure the `kibana.yml` settings and add the aggregations.
83
-
84
-
. In `kibana.yml`, set `xpack.maps.showMapVisualizationTypes` to `true`.
85
-
86
-
. To display your data on the region map, use the following aggregations:
To navigate the region map, use the navigation options.
97
-
98
-
* To change the zoom level, click *Zoom In* or *Zoom out* image:images/viz-zoom.png[].
99
-
100
-
* To automatically crop the map boundaries, click *Fit Data Bounds* image:images/viz-fit-bounds.png[].
101
-
102
-
[float]
103
1
[[heat-map]]
104
-
=== Heat map
2
+
== Heat map
105
3
106
-
Use heat maps when your data set includes categorical data. For example, use a heat map to see the flights of origin countries compared to destination countries using the sample flight data.
4
+
Display graphical representations of data where the individual values are represented by colors. Use heat maps when your data set includes categorical data. For example, use a heat map to see the flights of origin countries compared to destination countries using the sample flight data.
107
5
108
6
[role="screenshot"]
109
7
image::images/visualize_heat_map_example.png[]
110
8
111
9
[float]
112
10
[[build-heat-map]]
113
-
==== Build a heat map
11
+
=== Build a heat map
114
12
115
13
To display your data on the heat map, use the supported aggregations.
116
14
@@ -123,7 +21,7 @@ Heat maps support the following aggregations:
123
21
124
22
[float]
125
23
[[navigate-heatmap]]
126
-
==== Change the color ranges
24
+
=== Change the color ranges
127
25
128
26
When only one color displays on the heat map, you might need to change the color ranges.
0 commit comments