Hey,
Yes absolutely so the syslog datastream where i've triggered manually seems to be doing "fine"
Here is the ilm explain of the current backing index :
{
"indices" : {
".ds-filebeat-linux-syslog-2023.12.07-000003" : {
"index" : ".ds-filebeat-linux-syslog-2023.12.07-000003",
"managed" : true,
"policy" : "30d",
"lifecycle_date_millis" : 1701944834271,
"age" : "5.63h",
"phase" : "hot",
"phase_time_millis" : 1701944834434,
"action" : "rollover",
"action_time_millis" : 1701944834434,
"step" : "check-rollover-ready",
"step_time_millis" : 1701944834434,
"phase_execution" : {
"policy" : "30d",
"phase_definition" : {
"min_age" : "0ms",
"actions" : {
"rollover" : {
"max_primary_shard_size" : "50gb",
"max_age" : "1d"
}
}
},
"version" : 3,
"modified_date_in_millis" : 1701181053442
}
}
}
}
We can see that it seems to work pretty fine
However another data stream where i didnt ran the POST rollover query
{
"indices" : {
".ds-filebeat-xx-2023.11.25-000001" : {
"index" : ".ds-filebeat-xx-2023.11.25-000001",
"managed" : true,
"policy" : "30d",
"lifecycle_date_millis" : 1700927237089,
"age" : "12.03d",
"phase" : "hot",
"phase_time_millis" : 1700927237227,
"action" : "complete",
"action_time_millis" : 1700927237026,
"step" : "complete",
"step_time_millis" : 1700927237227,
"phase_execution" : {
"policy" : "30d",
"phase_definition" : {
"min_age" : "0ms",
"actions" : { }
},
"version" : 1,
"modified_date_in_millis" : 1698406220853
}
}
}
}
We can see that the actions rollover is not present depsite having the same ILM policy ?