Skip to content

Commit 4201396

Browse files
committed
[DOCS] Clarify description of geo_results (elastic#91237)
1 parent 55cde1a commit 4201396

File tree

1 file changed

+13
-9
lines changed

1 file changed

+13
-9
lines changed

docs/reference/ml/anomaly-detection/apis/get-record.asciidoc

Lines changed: 13 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -142,15 +142,19 @@ configuration. For example, `max`.
142142
(string) The description of the function in which the anomaly occurs, as
143143
specified in the detector configuration.
144144

145-
`geo_results.actual_point`::
146-
(string) The actual value for the bucket formatted as a `geo_point`. If the
147-
detector function is `lat_long`, this is a comma delimited string of the
148-
latitude and longitude.
149-
150-
`geo_results.typical_point`::
151-
(string) The typical value for the bucket formatted as a `geo_point`. If the
152-
detector function is `lat_long`, this is a comma delimited string of the
153-
latitude and longitude.
145+
`geo_results`::
146+
(optional, object) If the detector function is `lat_long`, this object contains
147+
comma delimited strings for the latitude and longitude of the actual and typical values.
148+
+
149+
.Properties of `geo_results`
150+
[%collapsible%open]
151+
====
152+
`actual_point`::
153+
(string) The actual value for the bucket formatted as a `geo_point`.
154+
155+
`typical_point`::
156+
(string) The typical value for the bucket formatted as a `geo_point`.
157+
====
154158

155159
`influencers`::
156160
(array) If `influencers` was specified in the detector configuration, this array

0 commit comments

Comments
 (0)