Skip to content
New issue

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

parentSegmentId question #3094

Closed
zou79189747 opened this issue Jul 16, 2019 · 4 comments
Closed

parentSegmentId question #3094

zou79189747 opened this issue Jul 16, 2019 · 4 comments
Labels
question End user question and discussion.
Milestone

Comments

@zou79189747
Copy link

a request pass 3 node , first node use java agent ,second node use nodejs agent, third node use java agent。but on trace page the chart is incomplete。I found the nodejs agent sent span data have a problem that the parentSegmentId in refs equal trace_id , I think parentSegmentId should be the first node sent segmentId , but it's not ,why?

@wu-sheng
Copy link
Member

Ask this at nodejs agent project. It isn't skywalking issue.

@wu-sheng wu-sheng added this to the 6.3.0 milestone Jul 16, 2019
@wu-sheng wu-sheng added the question End user question and discussion. label Jul 16, 2019
@wu-sheng
Copy link
Member

Header has two versions protocol. I don't know whether it upgraded in nodejs agent. SkyWalking java agent has compatible mode with v5 header.

Read setup document.

@zou79189747
Copy link
Author

In Java agent the config agent.active_v2_header default is true , I want to check SkyAPM-nodejs config ,but
so many page url return 404 in SkyAPM-nodejs document ,I can't find the config list ,I create a new issue in nodejs agent project , but that project looks like inactive,I'm not sure I will get answer. And can you show me the url about v5 header

@wu-sheng
Copy link
Member

In java agent, v5 header is agent.active_v1_header. cc @ascrutae

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question End user question and discussion.
Projects
None yet
Development

No branches or pull requests

2 participants