# \[Threat Intelligence\]: Avoid redundancy of information in the same index

**URL:** https://discuss.elastic.co/t/threat-intelligence-avoid-redundancy-of-information-in-the-same-index/260303
**Category:** Logstash
**Created:** [January 6, 2021, 9:04am UTC](https://discuss.elastic.co/t/threat-intelligence-avoid-redundancy-of-information-in-the-same-index/260303 "2021-01-06T09:04:54Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)
#### Post date: [January 6, 2021, 4:50pm UTC](https://discuss.elastic.co/t/threat-intelligence-avoid-redundancy-of-information-in-the-same-index/260303/4 "2021-01-06T16:50:14Z")

</div>

To generate a fingerprint use a filter

```
fingerprint {
    concatenate_sources => true 
    method => "SHA256" 
    source => ["url"] # And possibly other fields
    target => "[@metadata][fingerprint]"
}

```

then reference it in the elasticsearch output using a sprintf reference

```
document_id => "%{[@metadata][fingerprint]}"
```

---

_[View the full topic](https://discuss.elastic.co/t/threat-intelligence-avoid-redundancy-of-information-in-the-same-index/260303)._