[DOCS] Fix doc build errors for elastic/x-pack-elasticsearch#1197 (elastic/x-pack-elasticsearch#1199)
Original commit: elastic/x-pack-elasticsearch@30f69513ab
This commit is contained in:
parent
4b39d858b7
commit
019b1f7ece
|
@ -17,11 +17,11 @@ This is a summary of all the anomalies, pinpointing when they occurred.
|
||||||
Influencer results show which entities were anomalous and when.
|
Influencer results show which entities were anomalous and when.
|
||||||
For example, at 16:05 `user_name: Bob` was unusual.
|
For example, at 16:05 `user_name: Bob` was unusual.
|
||||||
This is a summary of all anomalies for each entity, so there can be a lot of these results.
|
This is a summary of all anomalies for each entity, so there can be a lot of these results.
|
||||||
Once you have identified a noteable bucket time, you can look to see which entites were significant.
|
Once you have identified a notable bucket time, you can look to see which entites were significant.
|
||||||
|
|
||||||
Record results provide the detail showing what the individual anomaly was, when it occurred and which entity was involved.
|
Record results provide the detail showing what the individual anomaly was, when it occurred and which entity was involved.
|
||||||
For example, at 16:05 Bob sent 837262434 bytes, when the typical value was 1067 bytes.
|
For example, at 16:05 Bob sent 837262434 bytes, when the typical value was 1067 bytes.
|
||||||
Once you have identifed a bucket time and/or a significant entity, you can drill through to the record results
|
Once you have identified a bucket time and/or a significant entity, you can drill through to the record results
|
||||||
in order to investigate the anomalous behavior.
|
in order to investigate the anomalous behavior.
|
||||||
|
|
||||||
//TBD Add links to categorization
|
//TBD Add links to categorization
|
||||||
|
@ -91,16 +91,14 @@ A bucket resource has the following properties:
|
||||||
|
|
||||||
`timestamp`::
|
`timestamp`::
|
||||||
(date) The start time of the bucket. This timestamp uniquely identifies the bucket. +
|
(date) The start time of the bucket. This timestamp uniquely identifies the bucket. +
|
||||||
+
|
|
||||||
--
|
|
||||||
NOTE: Events that occur exactly at the timestamp of the bucket are included in
|
NOTE: Events that occur exactly at the timestamp of the bucket are included in
|
||||||
the results for the bucket.
|
the results for the bucket.
|
||||||
|
|
||||||
--
|
|
||||||
|
|
||||||
[float]
|
[float]
|
||||||
[[ml-results-bucket-influencers]]
|
[[ml-results-bucket-influencers]]
|
||||||
====== Bucket Influencers
|
===== Bucket Influencers
|
||||||
|
|
||||||
Bucket influencer results are available as nested objects contained within bucket results.
|
Bucket influencer results are available as nested objects contained within bucket results.
|
||||||
These results are an aggregation for each the type of influencer.
|
These results are an aggregation for each the type of influencer.
|
||||||
|
|
Loading…
Reference in New Issue