Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOCS] Expands forecast limitations #1101

Merged
merged 2 commits into from
May 25, 2020
Merged

[DOCS] Expands forecast limitations #1101

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
84d14fc
[DOCS] Expands forecast limitations.
szabosteve May 21, 2020
8220d41
[DOCS] Changes wording.
szabosteve May 21, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions docs/en/stack/ml/anomaly-detection/limitations.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -241,9 +241,10 @@ create jobs in {kib} or by using APIs.

There are some limitations that affect your ability to create a forecast:

* You can generate only three forecasts concurrently. There is no limit to the
number of forecasts that you retain. Existing forecasts are not overwritten when
you create new forecasts. Rather, they are automatically deleted when they expire.
* You can generate only three forecasts per {anomaly-job} concurrently. There is
no limit to the number of forecasts that you retain. Existing forecasts are not
overwritten when you create new forecasts. Rather, they are automatically
deleted when they expire.
* If you use an `over_field_name` property in your {anomaly-job} (that is to say,
it's a _population job_), you cannot create a forecast.
* If you use any of the following analytical functions in your {anomaly-job},
Expand Down