FileBeat EOF Error

Elastic Stack Beats
36

here it is!

 beats {
                port => 5044
                client_inactivity_timeout => 300
        }

nothing in logstash side :frowning:

this is part of last night: from 22 to 3

{:timestamp=>"2016-10-09T22:48:59.983000+0200", :message=>"Elapsed, 'end event' received", :end_tag=>"dsc_start_finished", :unique_id_field=>"thread_id", :level=>:info}
{:timestamp=>"2016-10-09T22:49:00.012000+0200", :message=>"Elapsed, 'start event' received", :start_tag=>"dsc_start_called", :unique_id_field=>"thread_id", :level=>:info}
{:timestamp=>"2016-10-10T03:00:07.358000+0200", :message=>"Elapsed, 'start event' received", :start_tag=>"dsc_start_called", :unique_id_field=>"thread_id", :level=>:info}
{:timestamp=>"2016-10-10T03:00:11.354000+0200", :message=>"Elapsed, 'start event' received", :start_tag=>"dsc_start_called", :unique_id_field=>"thread_id", :level=>:info}

During night your idea might hold, but during lunch time we are not at absolute zero, today we received 3 EOF but logs arrived at an average rate of 30 of logs per second. below the trend on the machine, the EOF arrived at 13.55.50 after 2 minutes at 30 l/s

Pasted image1111×666 17.7 KB

in this topic https://discuss.elastic.co/t/filebeat-file-is-falling-under-ignore-older/61210/4 @ruflin says that the ignore_older error might be related to this error, but if this error is not important then what about that one?

I don't get why they are marked as ERR then