Ok...I have winlogbeat pipeline configured:
ilm_rollover_alias => "winlogbeat"
ilm_pattern => "{now/d}-0001"
ilm_policy => "Delete_After_30D"
When I do a GET /_alias/winlogbeat
, I get below (just showing the first few values)
{
"winlogbeat-7.2.0-2019.07.20" : {
"aliases" : {
"winlogbeat" : { }
}
},
"winlogbeat-7.2.0-2019.06.30" : {
"aliases" : {
"winlogbeat" : { }
}
},
"winlogbeat-6.3.2-2019.07.17" : {
"aliases" : {
"winlogbeat" : { }
}
},
...
If I do a GET /winlogbeat
, the first entry is winlogbeat-0001
and it shows is_write_index
is set to true. This seems to be good to go and I am not getting any index errors on winlogbeat-0001, however, I am getting mapping conflicts.
Running GET /_template/winlogbeat
, the below settings are configured. I manually created this template by exporting the template from winlogbeat then modifying the pattern and lifecycle settings before performing a PUT /template/winlogbeat
{
"winlogbeat" : {
"order" : 1,
"index_patterns" : [
"winlogbeat-*"
],
"settings" : {
"index" : {
"lifecycle" : {
"name" : "Delete_After_30D",
"rollover_alias" : "winlogbeat"
},
"codec" : "best_compression",
"mapping" : {
"total_fields" : {
"limit" : "10000"
}
},
"refresh_interval" : "5s",
"number_of_shards" : "1",
"query" : {
"default_field" : [
"message",
"tags",
"agent.ephemeral_id",
"agent.id",
"agent.name",
"agent.type",
"agent.version",
"client.address",
...
GET /winlogbeat-0001
shows
{
"winlogbeat-0001" : {
"aliases" : {
"winlogbeat" : {
"is_write_index" : true
}
},
"mappings" : {
"_meta" : {
"beat" : "winlogbeat",
"version" : "7.2.0"
},
"dynamic_templates" : [
Why is it using a dynamic template when it's pattern matches my template index pattern?