Logs from Fastly delayed or missing

 Problem:

When sending logs from Fastly to a Sumo Logic HTTP Source you may notice missing logs or delays when sending low amounts of data with time gaps. This can cause Sumo Logic to have connection timeouts and not ingest the data sent once the connection is timed out.

Sumo Logic Support can confirm this issue by checking the Source. The related error shows an exception thrown due to an end of file error, which indicates that when reading the data the connection ended. Like this:

error reading from input stream at byte 0, input x, blade x
org.eclipse.jetty.io.EofException: early EOF

Resolution: 

Fastly has been able to adjust their service to not cause the connection timeouts. Please contact Fastly's support team to have them adjust your account. You can provide the Fastly case number '12877' for their reference.