Describe the question/issue
I thought this was not the case but it turns out our code does not actually take the log timestamp and use it to set the file name. Customers likely expect that a S3 file with a certain timestamp would have the first log entry to have that timestamp and then for all subsequent logs in the same S3 file to be afterwards.
Since this is not the case, it may be difficult to find specific logs in files.
See the code here:
The timestamp is always just the current time at which out_s3 started creating the file on disk for buffering. Not the upload time. And not a timestamp from the logs.
Describe the question/issue
I thought this was not the case but it turns out our code does not actually take the log timestamp and use it to set the file name. Customers likely expect that a S3 file with a certain timestamp would have the first log entry to have that timestamp and then for all subsequent logs in the same S3 file to be afterwards.
Since this is not the case, it may be difficult to find specific logs in files.
See the code here:
The timestamp is always just the current time at which out_s3 started creating the file on disk for buffering. Not the upload time. And not a timestamp from the logs.