Hi. I am having some difficulties with the indexing of filebeat instead of using the "filebeat-YYYY.MM.dd" it sporadically indexes as %{[@metadata][beat]}-%{+YYYY.MM.dd}.. like it does not handle the metadata: ** curl 'localhost:9200/_cat/indices?v'** health status index …

Filebeat: Wrong index structure

Steiniche (Rasmus Steiniche) January 13, 2016, 2:04pm 8

I have the exact same issue.
It seems like it is only some messeges send from filebeat that does not contain the metadata information.
It is, as far as I know, only an issue when this tag is present: beats_input_flushed_by_end_of_connection

Topic		Replies	Views
Filebeat not indexing data correctly " %{[@metadata][beat]}- " Beats	2	926	July 19, 2016
Elastic not indexing correctly. Showing "%{[@metadata][beat]}- Beats	4	988	July 5, 2017
@metadata.beats not sending data to filebeat index Logstash	2	951	June 13, 2017
Indexes being created as %{[@metadata][beat]}-2017.05.26 instead of "filebeat-2017.05.26" Beats	3	1528	June 16, 2017
Unable to specify index Beats filebeat	2	868	July 5, 2017

Filebeat: Wrong index structure

Related topics