Shard Allocation after new indexes is created

Elastic Stack Elasticsearch
1

When my indexes rolled over nothing is being written to the new index. How can I fix this?

image
image.png919×610 73.5 KB

2

Anyone have any thoughts?

Thanks

3

I might be on the right track but need some help on fixing the issue. I think I have configured Logstash to send all data to a specific index but not sure how to configure the handling of the rollover?

output {
  if [@metadata][pipeline] {
    elasticsearch {
    hosts => ["http://10.3.200.45:9200", "http://10.3.200.46:9200"]
	index => "%{[@metadata][beat]}-%{[@metadata][version]}-000001"
      pipeline => "%{[@metadata][pipeline]}" 
    }
  } else {
    elasticsearch {
    hosts => ["http://10.3.200.45:9200", "http://10.3.200.46:9200"]
	index => "%{[@metadata][beat]}-%{[@metadata][version]}-000001"
    }
  }
}
4

That indeed looks incorrect. You are supposed to index into the write alias, not a specific index.

5

How would I go about getting that fixed without breaking something else?

Can I set the ILM Pattern in the Logstash Conf file?

Thank you

6

In my Logstash Conf file will this fix my issue? Do I have to enable ILM and then change my index to the following?

index => "%{[@metadata][beat]}-%{[@metadata][version]}"

Thank you for your help

7

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.