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
Server
在导出的trace链路json数据里,resource_spans里的spans的traceId每个都不相同,这个虽然符合Otel格式规范,但是traceId不同,导入其他符合Otel规范的数据展示层时,无法关联出链路,这个是导出的trace的json数据 deepflow_trace.txt
通过配置Exporter导出到指定的可以解析Otel规范的程序中,然后该程序将数据写入到Kafka,在另一端消费时,发现一条数据的instrumentation_library_spans里的spans的trace_id不相同,通过 io.opentelemetry:opentelemetry-proto:1.7.1-alpha这个依赖将数据转成对象,获取到一批resource_spans,resource_spans->instrumentation_library_spans->spans->trace_id,Otel里的TraceId一条数据的TraceId应该是相同的, 如果不相同应该不符合Otel规范吧,
No response
The text was updated successfully, but these errors were encountered:
你好,这里的导出仅作为导出功能,数据之间并不会相互关联,例如:并不会做到同一个调用链的 span 统一导出,即导出的数据并不一定是同一个 trace 的
Sorry, something went wrong.
请问这个如何自己实现同一链路的数据进行trace的关联呢?
No branches or pull requests
Search before asking
DeepFlow Component
Server
What you expected to happen
在导出的trace链路json数据里,resource_spans里的spans的traceId每个都不相同,这个虽然符合Otel格式规范,但是traceId不同,导入其他符合Otel规范的数据展示层时,无法关联出链路,这个是导出的trace的json数据
deepflow_trace.txt
How to reproduce
通过配置Exporter导出到指定的可以解析Otel规范的程序中,然后该程序将数据写入到Kafka,在另一端消费时,发现一条数据的instrumentation_library_spans里的spans的trace_id不相同,通过 io.opentelemetry:opentelemetry-proto:1.7.1-alpha这个依赖将数据转成对象,获取到一批resource_spans,resource_spans->instrumentation_library_spans->spans->trace_id,Otel里的TraceId一条数据的TraceId应该是相同的, 如果不相同应该不符合Otel规范吧,
DeepFlow version
No response
DeepFlow agent list
No response
Kubernetes CNI
No response
Operation-System/Kernel version
No response
Anything else
No response
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: