# Fingerprint unable to fingerprint @timestamp

**URL:** https://discuss.elastic.co/t/fingerprint-unable-to-fingerprint-timestamp/29855
**Category:** Logstash
**Created:** [September 23, 2015, 5:27pm UTC](https://discuss.elastic.co/t/fingerprint-unable-to-fingerprint-timestamp/29855 "2015-09-23T17:27:05Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![cpattonj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cpattonj/32/4365_2.png) [@cpattonj](https://discuss.elastic.co/u/cpattonj)
#### Post date: [September 23, 2015, 5:27pm UTC](https://discuss.elastic.co/t/fingerprint-unable-to-fingerprint-timestamp/29855/1 "2015-09-23T17:27:05Z")

</div>

With input lines like:

```
{"count":10, "timestamp":"2015-09-22T00:00:00.000Z"}

```

I am unable to fingerprint based off of the date extracted by my date filter. For fingerprint, it's exactly the same for all of my messages when based off of @timestamp but it is in-fact unique when I use the timestamp field (or count for that matter).

I was able to confirm that the @timestamp field is being created successfully off of the date filter so hopefully I'm just missing something here syntactically?

My config:

```
filter {
  date {
    match => ['timestamp', 'ISO8601']
  }
# also played with checksum
# checksum {
# algorithm => 'md5' # works as expected
# }
  fingerprint {
    method => 'MD5'
    key => '00000000'
    target => 'fingerprint'
    #source => ['timestamp'] ## works!
    #source => ['count'] ## works!
    source => ['@timestamp'] #does not work!
  }
}

output {
  stdout {
    codec => 'json'
  }
  elasticsearch {
    host => '127.0.0.1'
    cluster => 'logstash'
    document_id => '%{fingerprint}'
  }
}
```

---

<div class="post-metadata">

### Author: ![cpattonj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cpattonj/32/4365_2.png) [@cpattonj](https://discuss.elastic.co/u/cpattonj)
#### Post date: [September 23, 2015, 5:37pm UTC](https://discuss.elastic.co/t/fingerprint-unable-to-fingerprint-timestamp/29855/2 "2015-09-23T17:37:39Z")

</div>

After posting this I did some more testing and found that the only instance in which fingerprint is not unique is when the timestamps differ in their milliseconds. Fingerprint bug?

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [September 24, 2015, 2:01am UTC](https://discuss.elastic.co/t/fingerprint-unable-to-fingerprint-timestamp/29855/3 "2015-09-24T02:01:32Z")

</div>

> [@cpattonj](#):
>
> the timestamps differ in their milliseconds

You mean between `timestamp` and `@timestamp` aren't the same values?

---

<div class="post-metadata">

### Author: ![cpattonj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cpattonj/32/4365_2.png) [@cpattonj](https://discuss.elastic.co/u/cpattonj)
#### Post date: [September 24, 2015, 11:34am UTC](https://discuss.elastic.co/t/fingerprint-unable-to-fingerprint-timestamp/29855/4 "2015-09-24T11:34:53Z")

</div>

Sorry, no, I mean to say that a timestamp of 2015-09-22T00:00:00.000Z and 2015-09-22T00:00:00.001Z or 2015-09-22T00:00:00.980Z all share the same fingerprint result.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 5:28am UTC](https://discuss.elastic.co/t/fingerprint-unable-to-fingerprint-timestamp/29855/5 "2017-07-06T05:28:10Z")

</div>


