我有两个包含多行日志语句的日志文件。他们两个在每个日志语句的开头都有相同的日期时间格式。配置是这样的:CloudWatch日志表现怪异
state_file = /var/lib/awslogs/agent-state
[/opt/logdir/log1.0]
datetime_format = %Y-%m-%d %H:%M:%S
file = /opt/logdir/log1.0
log_stream_name = /opt/logdir/logs/log1.0
initial_position = start_of_file
multi_line_start_pattern = {datetime_format}
log_group_name = my.log.group
[/opt/logdir/log2-console.log]
datetime_format = %Y-%m-%d %H:%M:%S
file = /opt/logdir/log2-console.log
log_stream_name = /opt/logdir/log2-console.log
initial_position = start_of_file
multi_line_start_pattern = {datetime_format}
log_group_name = my.log.group
的CloudWatch的日志代理正确发送log1.0日志我的日志组对CloudWatch的,然而,它不发送日志文件的log 2-的console.log。
awslogs.log说:
2016-11-15 08:11:41,308 - cwlogs.push.batch - WARNING - 3593 - Thread-4 - Skip event: {'timestamp': 1479196444000, 'start_position': 42330916L, 'end_position': 42331504L}, reason: timestamp is more than 2 hours in future.
2016-11-15 08:11:41,308 - cwlogs.push.batch - WARNING - 3593 - Thread-4 - Skip event: {'timestamp': 1479196451000, 'start_position': 42331504L, 'end_position': 42332092L}, reason: timestamp is more than 2 hours in future.
虽然服务器的时间是正确的。另外奇怪的是start_position中提到的行号和end_position在实际的日志文件被推入时不存在。
任何其他人遇到此问题?
我有同样的效果,仍然在寻找解决方案。重新启动服务没有帮助。 BTW:start_position和end_position不是行号,而是字节位置。 –