wu-sheng commented on issue #1941: URL: https://github.com/apache/skywalking/issues/1941#issuecomment-1987882220
> > > I think the toolkit should have many rich APIs, so that we can easily get, modify, reset, stop traceId etc. > > > > > > There is no such thing about modify and reset. Once we do that, this is not a distributed tracing system. Don't consider SkyWalking to trace your business flow. It is out of our landscape. I know many users thought they could, but we don't provide that. > > Our current system generates traceId and spanId through Spring-cloud-sleuth. In the case of mobile devices, traceId and spanId are generated by the mobile device. The entire link and log are concatenated by sleuth's traceId. Now we want to introduce skywalking to visualize the entire request link and replace the default traceId-segmentId generated by skywalking with the original traceId-spanId, So Skywalking is still a distributed link tracking system, I'm not sure if there's a problem with what I described. > > Based on the scenario I mentioned above, can Skywalking support custom traceIDs, so that our logging system and Skywalking can be unified. @wu-sheng If the trace ID is generated in the downstream, then you need to follow [SkyWalking Cross Process Propagation Headers Protocol](https://skywalking.apache.org/docs/main/latest/en/api/x-process-propagation-headers-v3/). This is not about customizing the trace ID. We asked more than that. Please open a new discussion if you want to do further discussion. This discussion is irrelative. This discussion was only about using x-request-id, but not link the traces from skywalking with the ones from your systems(such as Mobile). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
