# Elastic Stack for workflow tracing architecture

**URL:** <https://discuss.elastic.co/t/elastic-stack-for-workflow-tracing-architecture/179204>\
**Category:** Elasticsearch\
**Created:** [May 1, 2019, 1:12pm UTC](https://discuss.elastic.co/t/elastic-stack-for-workflow-tracing-architecture/179204 "2019-05-01T13:12:09Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Mark\_Harwood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_harwood/32/10538_2.png) [@Mark\_Harwood](https://discuss.elastic.co/u/Mark_Harwood)\
**Post date:** [May 1, 2019, 2:34pm UTC](https://discuss.elastic.co/t/elastic-stack-for-workflow-tracing-architecture/179204/2 "2019-05-01T14:34:13Z")

</div>

Hi Ben,

There's an approach using logstash and an "elapsed" plugin which can join related records together. We got into some of the architectural concerns over that [here](https://discuss.elastic.co/t/using-painless-to-calculate-durations/119495/4)

Another approach is to use an entity centric index -[example scripts and discussion here](https://twitter.com/elasticmark/status/1009380268409610240?s=20)

---

_[View the full topic](https://discuss.elastic.co/t/elastic-stack-for-workflow-tracing-architecture/179204)._