# Gather timing data needed to troubleshoot latency problems in microservice architectures

**URL:** <https://discuss.elastic.co/t/gather-timing-data-needed-to-troubleshoot-latency-problems-in-microservice-architectures/112570>\
**Category:** Elasticsearch\
**Created:** [December 20, 2017, 7:12am UTC](https://discuss.elastic.co/t/gather-timing-data-needed-to-troubleshoot-latency-problems-in-microservice-architectures/112570 "2017-12-20T07:12:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nitulkukadia](https://avatars.discourse-cdn.com/v4/letter/n/9de0a6/32.png) [@nitulkukadia](https://discuss.elastic.co/u/nitulkukadia)\
**Post date:** [December 20, 2017, 7:12am UTC](https://discuss.elastic.co/t/gather-timing-data-needed-to-troubleshoot-latency-problems-in-microservice-architectures/112570/1 "2017-12-20T07:12:46Z")

</div>

How can I gather timing data needed to troubleshoot latency problems in microservice architectures?  
It could provide details same as zipkin ([https://zipkin.io/](https://zipkin.io/)).

---

<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 17, 2018, 7:16am UTC](https://discuss.elastic.co/t/gather-timing-data-needed-to-troubleshoot-latency-problems-in-microservice-architectures/112570/2 "2018-01-17T07:16:26Z")

</div>

Closed on January 17, 2018, 7:16am UTC

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