-
Notifications
You must be signed in to change notification settings - Fork 245
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.
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
Adds anomaly detection FAQ items to the Troubleshooting page #2714
Conversation
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Istvan! Sorry for the delay. I finally managed to review the page and make some suggestions.
docs/en/stack/ml/anomaly-detection/ml-ad-troubleshooting.asciidoc
Outdated
Show resolved
Hide resolved
|
||
As model predictions, 95% confidence intervals, and actual values in | ||
documents in an index (if you enabled model plot) are available, you can use | ||
standard measures to assess prediction accuracy, interval calibration and so on. | ||
Aggregations can be used to compute these statistics. This might be useful if | ||
you would like to monitor data drifts; however, there are ways to automatically | ||
adapt to changing data characteristics. | ||
|
||
The purpose of {anomaly-detect} is to achieve the best ranking of periods where | ||
an anomaly happened. A useful way to evaluate this is to keep track of real | ||
incidents and see how well they correlate with the predictions of | ||
{anomaly-detect}. In practice, it is usually unambiguous qualitatively whether | ||
{anomaly-detect} is working well. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think, something is missing here. Let's catch up over zoom and see how to clarify this part.
docs/en/stack/ml/anomaly-detection/ml-ad-troubleshooting.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/stack/ml/anomaly-detection/ml-ad-troubleshooting.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/stack/ml/anomaly-detection/ml-ad-troubleshooting.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/stack/ml/anomaly-detection/ml-ad-troubleshooting.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/stack/ml/anomaly-detection/ml-ad-troubleshooting.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/stack/ml/anomaly-detection/ml-ad-troubleshooting.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/stack/ml/anomaly-detection/ml-ad-troubleshooting.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/stack/ml/anomaly-detection/ml-ad-troubleshooting.asciidoc
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Great work, @szabosteve, on translating my technobabble. This FAQ will be of great value to the customers. 🚀
* Adds anomaly detection FAQ. * Adds more FAQ items. * Adds items to the AD FAQ page. * Further edits. * Fixes bulleted lists. * [DOCS] Rephrase intro. * Adjusts structure. * [DOCS] Addresses feedback. (cherry picked from commit 3e1d41c)
* Adds anomaly detection FAQ. * Adds more FAQ items. * Adds items to the AD FAQ page. * Further edits. * Fixes bulleted lists. * [DOCS] Rephrase intro. * Adjusts structure. * [DOCS] Addresses feedback. (cherry picked from commit 3e1d41c)
Overview
This PR adds FAQ items to the Troubleshooting page.
Preview
Troubleshooting and FAQ