It is fine, you got it right. The doc uses localhost because their ES resides on the same machine as Kibana. If your output was incorrect, you would not have been able to create those indices. We need to take a look at "ignore_older".
What is the date time on your ES, Kibana, and Windows event machine?
Thanks, I didn't choose that setting its just the default in the config file. What I can't get my head around is that I've hit a limit in Elasticsearch just by uploading data from one laptop - what happens when I want to collect the event logs from hundreds of machines? There must be something I'm doing wrong.
Each shard comes with some overhead in terms of file handles and heap usage, so having a very large number of small shards is very inefficient and can cause problems, as described in this blog post. If you have small data volumes coming in and want to keep it for a long time, as the data you accidentally uploaded, it makes sense to reduce the number of primary shards per index and often also switch from daily to e.g. monthly indices.
Thanks for the input; I'm still very new to all this so I'm not quite sure what you mean by daily and monthly indices - does winlogbeat / Elastic stack create an index for each day and therefore are you saying that a monthly index is better as there would be fewer shards?
The problem was me not understanding indexes properly and simply using the examples in the documentation for a laptop containing 3 years of event log data - you've opened my eyes
Just out of curiosity, is it possible to use a yearly index?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.