-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Description
My application runs 20 pods, with Vector deployed via DaemonSet to collect logs via file source. Randomly, 2-3 nodes become unresponsive. During the unresponsive state, a truncated log entry suddenly appears. After comparison, I found these logs are always from the latter half of the last line of a rotated/compressed log file. Please advise on the root cause and how to fix it. the vector version is 0.50.0-distroless-libc
here is vector file source config
xx-common-log: fingerprint: strategy: device_and_inode ignore_older_secs: 300 include: - >- /var/lib/kubelet/pods/*/volumes/kubernetes.io~empty-dir/accesslogs/xx/monitor.log oldest_first: false read_from: beginning rotate_wait_secs: 60 type: file
and here is app logconfig
<RollingFile name="RollingFileMonitor" fileName="${FILE_PATH}/${MONITOR_FILE}.log" filePattern="${FILE_PATH}/${MONITOR_FILE}-%d{yyyy-MM-dd}_%i.log.gz"> <ThresholdFilter level="info" onMatch="ACCEPT" onMismatch="DENY"/> <PatternLayout pattern="%date{yyyy-MM-dd HH:mm:ss.SSS} %msg %n"/> <Policies> <TimeBasedTriggeringPolicy interval="1"/> <SizeBasedTriggeringPolicy size="100MB"/> </Policies> <DefaultRolloverStrategy max="14"/> </RollingFile>