About Jaeger

Jaeger, inspired by Dapper and OpenZipkin, is a distributed tracing system released as open source by Uber Technologies. It is used for monitoring and troubleshooting microservices-based distributed systems, including:

• Distributed context propagation

• Distributed transaction monitoring

• Root cause analysis

• Service dependency analysis

• Performance/latency optimization

Week 5

After week 4 we thought to start the critical path implementation. We also thought to implement the algorithm in the front end itself instead of the backend. Curious to know what is Critical Path? Check out this. This week I made a new PR to implement the Critical Path algorithm and implemented the algorithm somehow.

Week 6

After reviewing Mentor Yuri Shkuro said, "It requires a lot of Unit Tests". And practically speaking I never wrote unit tests. So I started learning about Unit testing this week. I read a lot of blogs and watched a few tutorials about unit testing. And I wrote unit tests for my project for better understanding. And then I began writing unit tests for the critical path algorithm, with the guidance of Mentor Yash Sharma, who helped me improve the quality of the unit tests significantly.

Week 7

This week we thought to handle the edge cases of the Critical Path Algorithm. I modified the algorithm to handle the edge cases and added more unit tests. This week I learned a lot, not a new technology but I learned how to write better quality code which is more understandable and maintainable. As I am a beginner sometimes I wrote redundant codes. But mentors reviewed my changes and helped me to write better-quality code. And we also thought to start a critical path visualization PR to avoid blocking the workflow when Algorithm PR is waiting for review.

Week 8

This Week I worked simultaneously on both PRs. And finally, Algorithm PR is ready to merge and is under review. And I am not able to do much work as I am in travelling this week. And in the upcoming weeks after the merging of these 2 PRs maybe I should do some documentation changes and explain the Critical Path implementation in a blog.

Related Links

Are you curious to know about my work?

• CriticalPath Algorithm PR

• CriticalPath visualization PR

Conclusion

In the upcoming weeks, I should make some documentation changes to explain the CriticalPath feature. And maybe also to work on stretch goals.

Thank you for reading this blog😊.

Hoping that sharing my experience gives you valuable insights.

I will back with a new blog

Feel free to connect with me on LinkedIn, Twitter and Instagram.

About Jaeger

Jaeger, inspired by Dapper and OpenZipkin, is a distributed tracing system released as open source by Uber Technologies. It is used for monitoring and troubleshooting microservices-based distributed systems, including:

• Distributed context propagation

• Distributed transaction monitoring

• Root cause analysis

• Service dependency analysis

• Performance/latency optimization

What should I do in this mentorship?

To add support for Critical Path analysis to Jaeger UI. By Implementing a Critical path determination algorithm in the backend and adding critical path visualization in the Trace Timeline view and other views(graph, table, flame chart).

What I learned for applying to this project

Previously I also applied to LFX in Term 1 this year for Harbor but my application was rejected. That is because I do not have an outstanding resume. But this time I have decent projects in my resume but still no open-source contributions. I joined the Jaeger Slack channel and I got to know that we should also write a proposal(similar to GSOC) and attach it to the cover letter. Initially, I do not know anything about Jaeger, distributed tracing, or critical path. But eventually, upon investigating and reading documentation and several blogs, I also set up the Jaeger on my laptop and tried to solve some good first issues but was not able to solve them due to less time and not being able to understand the code base. But still, I wrote a good proposal with the knowledge gained. And I learned new topics in writing this proposal. And finally, this time my application was selected, Thanks to the mentors Yuri Shkuro and Yash Sharma for selecting me. And my mentorship period from Jun 1st - Aug 31st

Week 1

After getting the result I was excited to start my journey as an LFX mentee. In the 1st week, I completed all paperwork related to the LFX mentorship program(like filling in details and signing the offer letter etc..). And mentors said we will start working from the next week until then get familiar with Jaeger. But this week I was so pressurized not because of work but because I am not able to understand anything in the codebase(i.e., not able to solve any good first issue also). And I also felt worried to ask doubts because I am thinking like if I ask any silly or basic doubts how they will think about me. That's about the 1st week

Week 2

This week I attended a 1:1 video call with mentor Yash Sharma, and he assigned me some good first issues in both the Frontend and Backend codebases of Jaeger to get familiar with Repos. And told to work on refining the algorithm I wrote in the proposal.

Initially I can't able to solve any good first issue But with the help of the mentors, I solved a good first issue. The interesting thing about this issue is it took a 2days time to solve this issue and the changes done in the code base are just one line.

I felt happy about this but still not confident but now I am not worried about asking my doubts because in open source every one tries to help you nothing to worry about asking doubts.

Week 3

I loved this week because in this week I worked on this issue. And both my mentors guided me in solving this issue. And this is the first medium-level codebase change I contributed to in the open source journey and in the Jaeger. And I felt very excited when my PR is merged. And after solving this I felt somewhat confident like now I can understand the codebase. And I also attended some 1:1 calls with mentor Yash Sharma In which we discussed the workflow of the project and planned the tasks to do.

Week 4

This week I am working on making a design doc like to identify what changes should I do in the backend or frontend. And in refining the critical path algorithm. Majorly this week we gave time to make the design doc and in the meanwhile, mentor Yash Sharma told us to work on some issues from the Backen Repo of Jaeger to get familiar with the backend. And I am excited to do this work and I loved the community and mentors I was working with.

Related Links

Are you curious to know more about Jaeger, Distributed Tracing or our LFX project

Checkout this blogs

1. Evolving Distributed Tracing at Uber Engineering

2. CRISP: Critical Path Analysis for Microservice Architectures

Jaeger Documentation: Jaeger Documentation

LFX project: Visualize the Critical Path of a trace

Conclusion

In the upcoming weeks, I should implement the critical path algorithm in the backend and visualization in the front end. And soon I will get back with another blog about my upcoming week's experience.

Thank you for reading this blog😊.

Hoping that sharing my experience gives you valuable insights.

Feel free to connect with me on LinkedIn, Twitter and Instagram.