Hi ,
I have deleted the 2014 indices from indices and restarted the elastic search service . But the index logstash-2014.06.27 reappeared . Deleted the file from both the nodes but i can see the 2014 for the date 27 reappeared after restarting the service
Nagios Log server logstash behaving crazy
Re: Nagios Log server logstash behaving crazy
I'd like to take a closer look. Please open a ticket and we can setup a time for a remote.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: Nagios Log server logstash behaving crazy
can you please let me know the procedure to raise the ticket with Nagios Support.
Re: Nagios Log server logstash behaving crazy
You can email customersupport@nagios.com. If your email address is not in our system then you will receive a bounce back and will have to email sales@nagios.com to be added. Feel free to PM me if you have any issues creating a case.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: Nagios Log server logstash behaving crazy
The issue got resolved after updating the NTPD on both the nodes and then restarting the services . Thanks for help
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Nagios Log server logstash behaving crazy
Excellent.
Yes, Log Server will create indexes in the past/future if it is receiving logs from a different time that contain their own timestamp. This can actually be quite useful because you can load historical logs into Log Server and have them on the correct dates.
Yes, Log Server will create indexes in the past/future if it is receiving logs from a different time that contain their own timestamp. This can actually be quite useful because you can load historical logs into Log Server and have them on the correct dates.