Skip to content
This repository was archived by the owner on Aug 16, 2022. It is now read-only.

Commit 52004b9

Browse files
Merge pull request #334 from ashwinkumar12345/high-cardinality-updates
High cardinality updates
2 parents c79791f + 385ae3a commit 52004b9

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/ad/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -58,11 +58,11 @@ You can add a maximum of five features for a detector.
5858
1. On the **Model configuration** page, enter the **Feature name**.
5959
1. For **Find anomalies based on**, choose the method to find anomalies. For **Field Value** menu, choose the **field** and the **aggregation method**. Or choose **Custom expression**, and add in your own JSON aggregation query.
6060

61-
#### (Optional) Set a category field
61+
#### (Optional) Set a category field for high cardinality
6262

6363
You can categorize anomalies based on a keyword or IP field type.
6464

65-
If you specify a category in the same time series but sliced with a different dimension like IP addresses, product IDs, country codes, and so on, you’ll see a granular view of anomalies within each entity of that field. This helps to dive deeper into anomalies of a unique entity or ID and isolate and debug issues.
65+
The category field categorizes or slices the source time series with a dimension like IP addresses, product IDs, country codes, and so on. This helps to see a granular view of anomalies within each entity of the category field to isolate and debug issues.
6666

6767
To set a category field, choose **Enable a category field** and select a field.
6868

@@ -78,7 +78,7 @@ For example, for a cluster with 3 data nodes, each with 8G of JVM heap size, the
7878

7979
Set the number of aggregation intervals from your data stream to consider in a detection window. We recommend you choose this value based on your actual data to see which one leads to the best results for your use case.
8080

81-
Based on experiments performed on a wide variety of one-dimensional data streams, we recommend using a window size between 1 and 16. The default window size is 8.
81+
Based on experiments performed on a wide variety of one-dimensional data streams, we recommend using a window size between 1 and 16. The default window size is 8. If you have set the category field for high cardinality, the default window size is 1.
8282

8383
If you expect missing values in your data or if you want the anomalies based on the current interval, choose 1. If your data is continuously ingested and you want the anomalies based on multiple intervals, choose a larger window size.
8484

@@ -113,7 +113,7 @@ If you see the detector pending in "initialization" for longer than a day, aggre
113113

114114
Anomaly grade is a number between 0 and 1 that indicates the level of severity of how anomalous a data point is. An anomaly grade of 0 represents “not an anomaly,” and a non-zero value represents the relative severity of the anomaly. The confidence score is an estimate of the probability that the reported anomaly grade matches the expected anomaly grade. Confidence increases as the model observes more data and learns the data behavior and trends. Note that confidence is distinct from model accuracy.
115115

116-
If you set the category field, you see an additional **Heat map** chart. The heat map correlates results for anomalous entities.
116+
If you set the category field, you see an additional **Heat map** chart. The heat map correlates results for anomalous entities. This chart is empty until you select an anomalous entity. You also see the anomaly and feature line chart for the time period of the anomaly (`anomaly_grade` > 0).
117117

118118
Choose a filled rectangle to see a more detailed view of the anomaly.
119119
{: .note }

0 commit comments

Comments
 (0)