This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 18
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add release notes for ODFE 1.7.0 (#109)
- Loading branch information
Showing
1 changed file
with
23 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
## Open Distro for Elasticsearch 1.7.0 Release Notes | ||
|
||
## Initial Release | ||
The Anomaly Detection Kibana plugin provides a Kibana view for the [Anomaly Detection Elasticsearch plugin](https://github.com/opendistro-for-elasticsearch/anomaly-detection). | ||
|
||
Anomaly detection uses the Random Cut Forest (RCF) algorithm for detecting anomalous data points in streaming time series. | ||
|
||
You can use the plugin with the same version of the [Open Distro Alerting Kibana plugin](https://github.com/opendistro-for-elasticsearch/alerting-kibana-plugin) to get alert notifications. You can create a monitor based on an anomaly detector directly on the Alerting Kibana plugin. Monitors run checks on the anomaly detection results regularly and trigger alerts based on custom trigger conditions. | ||
|
||
## Features | ||
|
||
1. Create an anomaly detector on an index and configure features for the detector | ||
2. Preview sample anomaly results for historical data | ||
3. Monitor live anomalies | ||
4. Review anomaly history together with alerts | ||
|
||
## Current Limitations | ||
|
||
- Supports Elasticsearch / Kibana 7.6.1. | ||
- Page may load slowly if you load/review data in a long time range. | ||
- Not all API calls have complete error handling. | ||
- We will continuously add new unit test cases, but we don't have 100% unit test coverage for now. This is a great area for developers from the community to contribute and help improve test coverage. | ||
- Please see documentation links and GitHub issues for other details. |