We're using a different date/timestamp format to the default provided by HoneyPy, which has meant some rejigging of the logger code local to us. It's horrible and I'll never submit it back.
It would be good if we could find a way to support multiple types of date/timestamp format.
The default: %Y-%m-%d %H:%M:%S,%L,%z && "%Y-%m-%d %H:%M:%S,%f,"
ours: %Y-%m-%dT%H:%M:%S,%L,%z && "%Y-%m-%dT%H:%M:%S,%f,"
The problem comes when we call honeypy_logtail.py and uses the split function on the logline. In my example above we have replaced the space with a 'T' character, so the logger's element ordering is knocked off.
My thinking is rather than fix for just this use case we should fix in a format agnostic way.
We're using a different date/timestamp format to the default provided by HoneyPy, which has meant some rejigging of the logger code local to us. It's horrible and I'll never submit it back.
It would be good if we could find a way to support multiple types of date/timestamp format.
The default: %Y-%m-%d %H:%M:%S,%L,%z && "%Y-%m-%d %H:%M:%S,%f,"
ours: %Y-%m-%dT%H:%M:%S,%L,%z && "%Y-%m-%dT%H:%M:%S,%f,"
The problem comes when we call honeypy_logtail.py and uses the split function on the logline. In my example above we have replaced the space with a 'T' character, so the logger's element ordering is knocked off.
My thinking is rather than fix for just this use case we should fix in a format agnostic way.