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.

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

[ML] Anomaly detection custom rules request #63843

Open
ghost opened this issue Apr 17, 2020 · 2 comments
Open

[ML] Anomaly detection custom rules request #63843

ghost opened this issue Apr 17, 2020 · 2 comments

Comments

@ghost
Copy link

ghost commented Apr 17, 2020

Describe the feature:
Being able to set cross condtion from other detectors or a specific field in the datafeed.

Describe a specific use case for the feature:
We are trying to detect anomalies from a wide population of pumps (influencers). One specific job is to monitor the motor temperature (detector) and when it's increasing or decrasing (compared to the average of the history ) we may have an issue. That's true when the the pump is running stable at the nominal speed. It's not true anymore when we have to stop and restart the pump, motor temperature is going to drop and speed is equal to zero. We don't want this transitional behavior to impact the anomaly detection (it's not an anomaly it's just a start and stop).

Something like: do not consider the motor temperature if the speed is unstable over the last 15min would do the job. It's not possible to filter the datafeed because each pump has its own nominal speed.

@elastic/machine-learning

@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui (:ml)

@peteharverson peteharverson changed the title Anomaly detection custom rules request [ML] Anomaly detection custom rules request Apr 17, 2020
@ghost
Copy link
Author

ghost commented Apr 20, 2020

Hello,
Here is an other idea related to ML custom rules:
Consider anomaly if the average value of the detector over the last the bucket is 10% higher (or lower) compared to the average. We have some issue where the parameter is super stable and a slight variation creates an important severity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants