jaegertracing/jaeger

Document multi-zone / multi-region setup

Open

#1,833 建立於 2019年10月5日

在 GitHub 查看
 (11 留言) (5 反應) (0 負責人)Go (18,974 star) (2,326 fork)batch import
documentationhelp wanted

描述

Requirement - what kind of business use case are you trying to solve?

Application is spread out across multiple clusters and traffic is routed to a cluster based on client location. How to have one Jaeger UI to see traces in all the clusters?

Is it possible to have collector,db,query and ui all in one cluster where all agents running in multiple clusters send their traces to? And if so is there a way to tag/label the span with cluster/region name?

Problem - what in Jaeger blocks you from solving the requirement?

There is no documentation on what the possible/best patterns are.

貢獻者指南

技術棧
gokubernetes
領域
documentationobservability
議題類型
documentation
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic knowledge of JaegerKubernetes multi cluster experienceDistributed tracing concepts
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
Start by reviewing the existing Jaeger documentation on deployment and architecture to understand current patterns. Look at related issues and discussions in the repository for any prior work or proposals. Then, outline a document describing multi zone/multi region setup, including considerations for collecting traces from multiple clusters and labeling spans with region information. Finally, gather feedback from the community via a draft PR.