# Log tracing with ELK

**URL:** https://discuss.elastic.co/t/log-tracing-with-elk/86367
**Category:** Elasticsearch
**Created:** [May 19, 2017, 7:02am UTC](https://discuss.elastic.co/t/log-tracing-with-elk/86367 "2017-05-19T07:02:39Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![dmi3zkm](https://avatars.discourse-cdn.com/v4/letter/d/54ee81/32.png) [@dmi3zkm](https://discuss.elastic.co/u/dmi3zkm)
#### Post date: [May 19, 2017, 7:02am UTC](https://discuss.elastic.co/t/log-tracing-with-elk/86367/1 "2017-05-19T07:02:39Z")

</div>

Hi all.  
Is there any guidelines how to implement log tracing using elk stack?  
I have a bunch of microservices which produce logs to elk. Let's suppose I have a request passing through a number of microservices and some unique request identifier which is inserted into each log entry. I want to group log entries by the request identifier and count the difference between first log entry (request start time) and last one (request end time), and aggregate those information to count some percentiles.  
Any thoughts how to implement that?

---

<div class="post-metadata">

### Author: ![mohan\_s](https://avatars.discourse-cdn.com/v4/letter/m/e95f7d/32.png) [@mohan\_s](https://discuss.elastic.co/u/mohan_s)
#### Post date: [May 19, 2017, 10:27am UTC](https://discuss.elastic.co/t/log-tracing-with-elk/86367/2 "2017-05-19T10:27:37Z")

</div>

For log tracing use [zipkin.io](http://zipkin.io) we can send the log events from log file to  
ES using LogStash.

Also you can look following extended implementations all are inspired from  
google dapper

1. [https://uber.github.io/jaeger/](https://uber.github.io/jaeger/)

2. [https://github.com/zalando/tracer](https://github.com/zalando/tracer)

3. [https://github.com/Nike-Inc/wingtips](https://github.com/Nike-Inc/wingtips)

---

<div class="post-metadata">

### Author: ![dmi3zkm](https://avatars.discourse-cdn.com/v4/letter/d/54ee81/32.png) [@dmi3zkm](https://discuss.elastic.co/u/dmi3zkm)
#### Post date: [May 19, 2017, 10:54am UTC](https://discuss.elastic.co/t/log-tracing-with-elk/86367/3 "2017-05-19T10:54:28Z")

</div>

Introducing zipkin will bring more complexity and my thought was to use what I already have.  
Analyzing logs in elk seems like justified solution to solve my problem.

---

<div class="post-metadata">

### Author: ![mohan\_s](https://avatars.discourse-cdn.com/v4/letter/m/e95f7d/32.png) [@mohan\_s](https://discuss.elastic.co/u/mohan_s)
#### Post date: [May 19, 2017, 1:18pm UTC](https://discuss.elastic.co/t/log-tracing-with-elk/86367/4 "2017-05-19T13:18:13Z")

</div>

Wrongly understand your question.

---

<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: [June 16, 2017, 1:18pm UTC](https://discuss.elastic.co/t/log-tracing-with-elk/86367/5 "2017-06-16T13:18:42Z")

</div>

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