Initiate a detection alert migration
Initiate a migration of detection alerts. Migrations are initiated per index. While the process is neither destructive nor interferes with existing data, it may be resource-intensive. As such, it is recommended that you plan your migrations accordingly.
Body Required
Alerts migration parameters
-
A string that is not empty and does not contain only whitespace
At least
1
element. Minimum length of each is1
. Format of each should match the following pattern:^(?! *$).+$
. -
requests_per_second integer
Minimum value is
1
. -
size integer
Minimum value is
1
. -
slices integer
Minimum value is
1
.
Responses
-
200 application/json; Elastic-Api-Version=2023-10-31
Successful response
-
400 application/json; Elastic-Api-Version=2023-10-31
Invalid input data response
-
401 application/json; Elastic-Api-Version=2023-10-31
Unsuccessful authentication response
-
500 application/json; Elastic-Api-Version=2023-10-31
Internal server error response
POST /api/detection_engine/signals/migration
curl \
-X POST https://localhost:5601/api/detection_engine/signals/migration \
-H "Content-Type: application/json; Elastic-Api-Version=2023-10-31"
Request examples
{
"index": [
"string"
],
"requests_per_second": 42,
"size": 42,
"slices": 42
}
Response examples (200)
{
"indices": [
{
"index": "string",
"migration_id": "string",
"migration_index": "string"
}
]
}
Response examples (400)
Security_detections_api_platformerrorresponse (generated)
{
"error": "string",
"message": "string",
"statusCode": 42
}
{
"message": "string",
"status_code": 42
}
Response examples (401)
{
"error": "string",
"message": "string",
"statusCode": 42
}
Response examples (500)
{
"message": "string",
"status_code": 42
}