After assigning my ILM policy as follows:
PUT /_ilm/policy/my_policy
{
"policy": {
"phases": {
"hot": {
"actions": {
"rollover": {
"max_size": "50gb",
"max_age": "30d"
}
}
}
}
}
}
And configuring my Metricbeat file with date-based indexing as follows:
output.elasticsearch:
hosts: ***
protocol: "https"
username: ***
password: ****
index: "metric-example-%{+yyyy.MM.dd}"
However, I noticed that it only works for one day, such as "2023-09-20," and does not proceed to the next day. Why is this error occurring?
When I try to index without specifying the date, like "PUT metricbeat-***," I encounter the following error:
{
"error": {
"root_cause": [
{
"type": "invalid_index_name_exception",
"reason": "Invalid index name [pororometrics], already exists as alias",
"index_uuid": "_na_",
"index": "pororometrics"
}
],
"type": "invalid_index_name_exception",
"reason": "Invalid index name [pororometrics], already exists as alias",
"index_uuid": "_na_",
"index": "pororometrics"
},
"status": 400
}
and for my first index, it turns like "<metrics-{now/d}-000001>" for provided_name. I think it should be metrics-2023-09-20-00001.
{
"settings": {
"index": {
"mapping": {
"total_fields": {
"limit": "10000"
}
},
"refresh_interval": "30s",
"provided_name": "<metrics-{now/d}-000001>",
"query": {
"default_field": [
Can you explain why these issues are happening?