We are seeing sporadic issues with stack traces not being pulled in with the body of their respective error level messages. In the splunkd.logs, the only issue that even occurs around the time of this occurring is the general `INFO WatchedFile - Checksum for seekptr didn't match, will re-read entire file` message.
Rolled over logs are stored in the same location as the files being written to, but these issues are not just occurring at the time of rollover, so it is not clear what is causing the stack traces to not be pulled in since it isn't happening consistently.
Any help or insight would be greatly appreciated.
↧