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
ISSUE
The documentation say that plugins.anomaly_detection.max_anomaly_features can be increased up to 10, (and is limiting but better than nothing)
I increased it to 10 via DevTools:
PUT /_cluster/settings
{
"persistent" : {
"plugins": {
"anomaly_detection": {
"max_anomaly_features": "10"
}
}
}
}
And GET /_cluster/settings/ tell me that is actually persistent even after shutting down the docker compose and bringing it back up.
But at the moment I try to insert the feature in the anomaly detection job in the dashboard, the maximum is locked at 5.
To Reproduce
Steps to reproduce the behavior:
Go to DevTools in dashboard
send and past the previous command
go to anomaly detection
5.try to set more than 5 features.
Host/Environment (please complete the following information):
OS: [Linux Manjaro]
Deployment: Docker compose
Version [latest]
Additional context
Sorry for my broken English, I'm Italian but trying to improve.
The text was updated successfully, but these errors were encountered:
ISSUE
The documentation say that plugins.anomaly_detection.max_anomaly_features can be increased up to 10, (and is limiting but better than nothing)
I increased it to 10 via DevTools:
PUT /_cluster/settings
{
"persistent" : {
"plugins": {
"anomaly_detection": {
"max_anomaly_features": "10"
}
}
}
}
And GET /_cluster/settings/ tell me that is actually persistent even after shutting down the docker compose and bringing it back up.
But at the moment I try to insert the feature in the anomaly detection job in the dashboard, the maximum is locked at 5.
To Reproduce
Steps to reproduce the behavior:
5.try to set more than 5 features.
Host/Environment (please complete the following information):
Additional context
Sorry for my broken English, I'm Italian but trying to improve.
The text was updated successfully, but these errors were encountered: