We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
基于 issue#8378 的评论:comment#2443765811 有一个如下场景:
graph LR client --> ingress --> gateway --> business
其中,ingress 默认开启了 x_request_id 能力,在 gateway 里透传,且,gateway 中开启了插桩,关联上后端服务以及 gateway 本身的 Client Process Span;
问题:由于 gateway 的 S-p 接到请求后通过进程池模型转发到后端,所以 gateway s-p / c-p 无法关联,使得如 comment#2443765811 所示,在 gateway 内产生空行。
期望:不要产生空行, 使得 gateway 内部可互相关联起来。
修改方案:1. 对于同一个进程的s-p/c-p,当找到了 x_request_id 关联,但 syscall_trace_id 上没有关联关系,在时间覆盖的前提下,允许构建关联关系
The text was updated successfully, but these errors were encountered:
taloric
Successfully merging a pull request may close this issue.
基于 issue#8378 的评论:comment#2443765811
有一个如下场景:
其中,ingress 默认开启了 x_request_id 能力,在 gateway 里透传,且,gateway 中开启了插桩,关联上后端服务以及 gateway 本身的 Client Process Span;
问题:由于 gateway 的 S-p 接到请求后通过进程池模型转发到后端,所以 gateway s-p / c-p 无法关联,使得如 comment#2443765811 所示,在 gateway 内产生空行。
期望:不要产生空行, 使得 gateway 内部可互相关联起来。
修改方案:1. 对于同一个进程的s-p/c-p,当找到了 x_request_id 关联,但 syscall_trace_id 上没有关联关系,在时间覆盖的前提下,允许构建关联关系
The text was updated successfully, but these errors were encountered: