@@ -38,6 +38,7 @@ of example values, and preview them on a map. For example:
38
38
39
39
[role="screenshot"]
40
40
image::images/weblogs-data-visualizer-geopoint.jpg[A screenshot of a geo_point field in {data-viz}]
41
+ // NOTE: This is an autogenerated screenshot. Do not edit it directly.
41
42
42
43
[discrete]
43
44
[[geographic-anomalies-jobs]]
@@ -65,6 +66,7 @@ past behavior of each customer (`user` ID):
65
66
66
67
[role="screenshot"]
67
68
image::images/ecommerce-advanced-wizard-geopoint.jpg[A screenshot of creating an {anomaly-job} using the eCommerce data in {kib}]
69
+ // NOTE: This is an autogenerated screenshot. Do not edit it directly.
68
70
69
71
.API example
70
72
[%collapsible]
@@ -128,6 +130,7 @@ sums of transferred data (`bytes` values):
128
130
129
131
[role="screenshot"]
130
132
image::images/weblogs-advanced-wizard-geopoint.jpg[A screenshot of creating an {anomaly-job} using the web logs data in {kib}]
133
+ // NOTE: This is an autogenerated screenshot. Do not edit it directly.
131
134
132
135
.API example
133
136
[%collapsible]
@@ -206,13 +209,15 @@ behavior:
206
209
207
210
[role="screenshot"]
208
211
image::images/ecommerce-anomaly-explorer-geopoint.jpg[A screenshot of an anomalous event in the eCommerce data in Anomaly Explorer]
212
+ // NOTE: This is an autogenerated screenshot. Do not edit it directly.
209
213
210
214
Likewise, there are time periods in the web logs sample data where there are
211
215
both unusually high sums of data transferred and unusual geographical
212
216
coordinates:
213
217
214
218
[role="screenshot"]
215
219
image::images/weblogs-anomaly-explorer-geopoint.jpg[A screenshot of an anomalous event in the web logs data in Anomaly Explorer]
220
+ // NOTE: This is an autogenerated screenshot. Do not edit it directly.
216
221
217
222
You can use the top influencer values to further filter your results and
218
223
identify possible contributing factors or patterns of behavior.
@@ -222,6 +227,7 @@ in the action menu in the anomaly table.
222
227
223
228
[role="screenshot"]
224
229
image::images/view-in-maps.jpg[A screenshot of the anomaly table with the Action menu opened and the "View in Maps" option selected]
230
+ // NOTE: This is an autogenerated screenshot. Do not edit it directly.
225
231
226
232
When you try this type of {anomaly-job} with your own data, it might take
227
233
some experimentation to find the best combination of buckets, detectors, and
0 commit comments