# Correlating Asynchronous Requests

**URL:** <https://discuss.elastic.co/t/correlating-asynchronous-requests/113312>\
**Category:** Logstash\
**Created:** [December 27, 2017, 12:14pm UTC](https://discuss.elastic.co/t/correlating-asynchronous-requests/113312 "2017-12-27T12:14:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Samuel\_Lima1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/samuel_lima1/32/101372_2.png) [@Samuel\_Lima1](https://discuss.elastic.co/u/Samuel_Lima1)\
**Post date:** [December 27, 2017, 12:14pm UTC](https://discuss.elastic.co/t/correlating-asynchronous-requests/113312/1 "2017-12-27T12:14:36Z")

</div>

Hi,  
I have a situation where many requests and responses are sent over Logstash and I have to correlate each pair request/response.  
I don't know when neither wheather the response is coming, but when and if it comes I'm able to correlate them with an ID which I can use as a Join field.

My question is:

`Is the Elasticsearch join datatype the best way to do this?`

But the doc says:

> The only case where the join field makes sense is if your data contains a one-to-many relationship where one entity significantly outnumbers the other entity.

Which is not my case because I going to have millions of one-to-zero\_or\_one relationship.

If not, is there better ways?

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:** [January 24, 2018, 12:14pm UTC](https://discuss.elastic.co/t/correlating-asynchronous-requests/113312/2 "2018-01-24T12:14:48Z")

</div>

Closed on January 24, 2018, 12:14pm UTC

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