I understand.
This data is a Apache Tomcat console log, we used Splunk to read those files
As I see it, a nomal log appears like this:
INFO | jvm 1 | main | 2018/10/05 20:37:46.463 | [m[0;32mINFO Log Info message
INFO | jvm 1 | main | 2018/10/05 20:37:46.463 | [m[0;32mDEBUG Log debug message
INFO | jvm 1 | main | 2018/10/05 20:37:46.463 | [m[0;32mERROR Log Error message
INFO | jvm 1 | main | 2018/10/05 20:37:46.463 | [m[0;32mWARNING Log Warning message
But I see several occurrences of, as I named it, empty log entries
INFO | jvm 1 | main | 2018/10/05 20:37:39.157 | [m
INFO | jvm 1 | main | 2018/10/05 20:37:38.290 | [m
INFO | jvm 1 | main | 2018/10/05 20:37:37.455 | [m
INFO | jvm 1 | main | 2018/10/05 20:37:36.755 | [m
INFO | jvm 1 | main | 2018/10/05 20:37:36.389 | [m
I've got no idea what they could mean. I tried a local Splunk installation to read my Apache Tomcat local server and i encountered this kind on "empty log events". I would dare say it is a server issue, because we don't log subsequent empty logs in our application.
I hope this helps a little. Thank you for the remark about not enough information.
... View more