You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we create a custom rule for an open anomaly detection job, e.g. using Kibana or the Anomaly Detection Job Update API, the rule is stored in the Java job configuration and passed to the native process, but the job configuration is not updated on the fly. This behavior can be reproduced in recent Elasticsearch versions, at least 8.13+.
The only workaround is to stop and restart the job.
The text was updated successfully, but these errors were encountered:
When we create a custom rule for an open anomaly detection job, e.g. using Kibana or the Anomaly Detection Job Update API, the rule is stored in the Java job configuration and passed to the native process, but the job configuration is not updated on the fly. This behavior can be reproduced in recent Elasticsearch versions, at least 8.13+.
The only workaround is to stop and restart the job.
The text was updated successfully, but these errors were encountered: