# Chaining log events

**URL:** <https://discuss.elastic.co/t/chaining-log-events/156855>\
**Category:** Logstash\
**Created:** [November 15, 2018, 12:36pm UTC](https://discuss.elastic.co/t/chaining-log-events/156855 "2018-11-15T12:36:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![deivkk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/deivkk/32/37669_2.png) [@deivkk](https://discuss.elastic.co/u/deivkk)\
**Post date:** [November 15, 2018, 12:36pm UTC](https://discuss.elastic.co/t/chaining-log-events/156855/1 "2018-11-15T12:36:19Z")

</div>

I have a requirement to create a fingerprint per log and chain it with the fingerprint of the previous log entry. So far I have been able to do something closer by using the "aggregate filter" and using a common task for all the logs, so I can update each entry based on a mapped value before the timeout is triggered. However, this approach is not valid for chaining logs from different "aggregate" executions per timeout.

I have been also thinking on redirecting the output to Elastic Search so I can then use it as input, but I have no idea on how to get the previous log entry.

Is there any way to achieve this?

Thanks

---

<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:** [December 13, 2018, 12:49pm UTC](https://discuss.elastic.co/t/chaining-log-events/156855/2 "2018-12-13T12:49:23Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.