Kibana is triggering logs 300% more than usual


(Anam ) #1

kibana is Triggering logs three times more than usual

I have updated ELK from 5.6 to 6.4 and the kibana dashboard works fine and all the services are active but the log volume in kibana is increased by 300% and also the elasticsearch logs throws the status as
[2018-12-05T10:24:49,770][WARN ][o.e.g.DanglingIndicesState] [8qBpdIM] [[authlog-2017.05.19/vZpZF_JsTKK1r4bki6OcKA]] can not be imported as a dangling index, as index with same name already exists in cluster metadata

[2018-12-05T10:24:49,770][WARN ][o.e.g.DanglingIndicesState] [8qBpdIM] [[logstash-dhcp4-2017.05.18/OhQHYndYTrWrTAJ2HDcQVA]] can not be imported as a dangling index, as index with same name already exists in cluster metadata

[2018-12-05T10:24:49,770][WARN ][o.e.g.DanglingIndicesState] [8qBpdIM] [[logstash-dhcp4-2017.05.19/kSQJztDmTbyjFlOPdgwduw]] can not be imported as a dangling index, as index with same name already exists in cluster metadata

[2018-12-05T10:24:49,770][WARN ][o.e.g.DanglingIndicesState] [8qBpdIM] [[logstash-dhcp4-2017.05.20/ZrqZlBLSTZiI0aFCHcqj8Q]] can not be imported as a dangling index, as index with same name already exists in cluster metadata

[2018-12-05T10:24:49,770][WARN ][o.e.g.DanglingIndicesState] [8qBpdIM] [[syslog-2017.05.19/jW8OmJceT4-4F-guo-y0yw]] can not be imported as a dangling index, as index with same name already exists in cluster metadata

How can I solve this. Making kibana logs to be triggered normal.