Found a similar question to this. And fixed this issue by adding a timezone property.
date {
match => [ "timestamp", "ISO8601" ]
timezone => "Asia/Shanghai"
target => "timestamp"
}
Found a similar question to this. And fixed this issue by adding a timezone property.
date {
match => [ "timestamp", "ISO8601" ]
timezone => "Asia/Shanghai"
target => "timestamp"
}
© 2020. All Rights Reserved - Elasticsearch
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.