You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description: Jaeger is an open-source, distributed tracing platform designed to monitor and troubleshoot transactions in distributed systems. In its basic deployment it allows to collect tracing data, store it in a database, and query & analyze individual traces in the UI. This workflow is great for deep-diving into individual requests, but it does not answer some higher level questions like “which endpoints in my service are the slowest?” To address those questions Jaeger has a special feature called SPM (Service Performance Management), which allows the user to see the trends of performance of services and endpoints and to drill down into the outliers. However, this feature requires a more complicated deployment where a special real-time processor is running and extracting metrics from the traces and storing those metrics in a Prometheus-compatible remote storage. Some of the storage backends supported by Jaeger, such as Elasticsearch & OpenSearch, can provide the same aggregate answers directly from the trace data, which can significantly simplify the deployment.
Expected Outcome:
Support SPM functionality directly in Elasticsearch / OpenSearch backends by implementing the metrics query API
Enhance existing e2e integration tests to continuously test this new capability
Recommended Skills: Go, basic familiarity with Elasticsearch
Expected project size: large (~350 hour projects)
The text was updated successfully, but these errors were encountered:
Hellooo @yurishkuro 👋 , I am Ahmed Kamal, open source contributor in the night and devops engineer, computer engineering student in the day, I am interested in this project and what it adds to the community, willing to solve this issue under your mentorship as a gsoc25 contributor 🚀
Hey, I have been wanting to contribute to jaeger for a while now and I would love to contribute to this for gsoc 2025. I will spend the next few weeks to few months familiarizing myself with the codebase by contributing to other issues. I hope I get the opportunity to work under you. And if there are any more ideas for gsoc 2025 from jaeger, I would love to contribute to those as well.
The text was updated successfully, but these errors were encountered: