Closed g3kr closed 3 years ago
@cosmo0920 Any thoughts here?
Was able to resolve this finally. The documentation is not clear and it does it not explicitly say if you use use_entire_record
you still need to use use_record_as_seed
.
The below config works
<filter **>
@type elasticsearch_genid
hash_id_key _hash # storing generated hash id key (default is _hash)
use_record_as_seed true
record_keys []
use_entire_record true
separator _
hash_type sha256
include_time_in_seed false
include_tag_in_seed false
</filter>
(check apply)
Problem
We are using the elasticsearch_genid filter to hash each record so duplicate records do not appear in ES.
However, we see that the filter is generating new hash ids for the same log message
...
Steps to replicate
The log message that was sent
Expected Behavior or What you need to ask
Instead of treating this as duplicates, a hash id is generated for each of this message and 3 records are inserted to ES. What am I missing?
Using Fluentd and ES plugin versions
Fluentd v1.11.4 ES plugin 4.0.7 Elasticsearch 7.6.1