You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
container runtime (dockerd at least) may split long (>32K?) lines, split line does not include a newline character at the end of the "log" value:
here:
{"log":"01.08.2023 11:47:25.018 [INFO] [com.teragrep.k8s_01.KubernetesLogReader] [main] Found 1 monitored logfile definitions, reading them with maximum of 2 threads each.\n","stream":"stdout","time":"2023-08-01T11:47:25.018743252Z"}
I am not sure if rlo_13 can detect this as it requires processing from k8s_01 to read the log, figure out if it ends in newline and then stitch it with the next one. But what if the log timestamps mismatch on these two events as that is fairly precise? How are the events actually combined?
container runtime (dockerd at least) may split long (>32K?) lines, split line does not include a newline character at the end of the "log" value:
here:
if this is missing the lines should be merged.
it may require support from https://github.com/teragrep/rlo_13 because k8s_01 is stateless in that sense.
The text was updated successfully, but these errors were encountered: