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

High Cardinality RFC #282

Open
sean-zheng-amazon opened this issue Oct 20, 2020 · 2 comments
Open

High Cardinality RFC #282

sean-zheng-amazon opened this issue Oct 20, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@sean-zheng-amazon
Copy link
Contributor

We are planning to a category field to support high cardinality, more details here: https://github.com/opendistro-for-elasticsearch/anomaly-detection/blob/master/docs/high-cardinality-rfc.md. Please add your comment in this issue.
@sean-zheng-amazon sean-zheng-amazon added the enhancement New feature or request label Oct 20, 2020
@tejpochiraju
Copy link

This is an essential feature for IoT deployments as one needs to be able to:

  • detect which device is causing the anomaly
  • create distinct anomaly classes for different SKUs (e.g. 300A is OK for a 500A rated sensor but anomalous for a 200A rated sensor).

@kaituo
Copy link
Member

kaituo commented Feb 18, 2021

We have already implemented this feature in ES 7.9+. Please try it out.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kaituo @tejpochiraju @sean-zheng-amazon