File tree 1 file changed +13
-4
lines changed
docs/reference/ml/anomaly-detection/apis 1 file changed +13
-4
lines changed Original file line number Diff line number Diff line change @@ -23,7 +23,14 @@ Predicts the future behavior of a time series by using its historical behavior.
23
23
[[ml-forecast-desc]]
24
24
==== {api-description-title}
25
25
26
- See {ml-docs}/ml-overview.html#ml-forecasting[Forecasting the future].
26
+ You can create a forecast job based on an {anomaly-job} to extrapolate future
27
+ behavior. Refer to
28
+ {ml-docs}/ml-overview.html#ml-forecasting[Forecasting the future] and
29
+ {ml-docs}/ml-limitations.html#ml-forecast-limitations[forecast limitations] to
30
+ learn more.
31
+
32
+ You can delete a forecast by using the
33
+ <<ml-delete-forecast,Delete forecast API>>.
27
34
28
35
[NOTE]
29
36
===============================
@@ -50,9 +57,11 @@ include::{docdir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
50
57
processed.
51
58
52
59
`expires_in`::
53
- (Optional, <<time-units, time units>>) The period of time that forecast results are retained.
54
- After a forecast expires, the results are deleted. The default value is 14 days.
55
- If set to a value of `0`, the forecast is never automatically deleted.
60
+ (Optional, <<time-units, time units>>) The period of time that forecast
61
+ results are retained. After a forecast expires, the results are deleted. The
62
+ default value is 14 days. If set to a value of `0`, the forecast is never
63
+ automatically deleted.
64
+
56
65
57
66
[[ml-forecast-example]]
58
67
==== {api-examples-title}
You can’t perform that action at this time.
0 commit comments