Love your work. Please keep them coming.
Nice video Clear sound. Thanks
Great...you got yourself a subscriber 👏👏
i wish there were a like button which can generate tons of likes..i would do that on this video!! you have solve my biggest problem!!thanks a lot boss
Great vids!
Hi, Thanks for sharing. But we use rollover mechanism for shard optimization and performance tuning. You said that logstash creates index and you don't like pattern numbers :) But firewall-2022.11.08 index has static shard number. There are many shard limitations in elasticsearch. If you dont use them, your system is getting slower day by day.
thanks, very good explain. But plz reduce the size of webcam circle plzzzzz...and put right top... we dont see your windows console
Great Videos !
index => firewall [ which you set as a rollover alias ] will write the data to 0001 and subsequent indexes that will be active on that particular moment.
Great!
Thanks (y)
nice job man
I have a more complex question, I would like my index pattern not to be today's date, but the date that is in the message line. Because if Logstash does not know how to access the remote elasticsearch if I restart logstash the next day, the lines stored in the logstash queue or disk queue will be indexed the same day, except the index must be based on the true log date in the message .
Hello friend! It would be great if you showed how to send sql database via logstash and filebeat converting them to json. And how to make a full-text search on the site
Nice vid! That Rollover is for data streams and be sure U set Your alias. Based on Your alias build dashboards, search quires, visualizations and never brake. With alias You target all Your indices with the same name. Data streams are great for managing, but for me somehow they are slow on warm on cold nodes. Data streams are like Timescale for Postgresql
Can video "Using Index Lifecycle Management (ILM) with Elasticsearch"+Data Stream? pleas
I am using input beats, i have done exactly all the steps but the problem is after i start logstash i don't nothing coming to the index but i can see doc count and size are increasing but from discover i don't see any. Also it broke other indexes not sure what i missed.
I have a clarification, the same way we did for index gets created everyday also have created only life cycle with deletion of 30 days. Also have assigned same ILM assigned to index but it’s not automatically managed by index when the new index gets created. Please advise
Nice video! I am trying to create a rollover every week. I have created the template and policy just as you have. In the logstash.conf file, if I set ilm_pattern => “{now/day}-000001” just as you have , and the ilm policy max age to be 7 will the index rollover name be the date it is rolled over with the trailing 000001 or will the trailing numbers just keep incrementing when it rolls over and the date stays the same?
@ahmed_mansour5