You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by GitBox <gi...@apache.org> on 2019/12/07 11:20:15 UTC

[GitHub] [skywalking] wu-sheng commented on issue #4020: How should we handle the cross-cloud invocation scenario?

wu-sheng commented on issue #4020: How should we handle the cross-cloud invocation scenario?
URL: https://github.com/apache/skywalking/issues/4020#issuecomment-562841888
 
 
   As what you are doing, we don't expect have trace, topology and metrics across cloud, then why don't you simply use namespace to isolate two env?
   
   > Make sure of the cross-cloud invocation has the same treaceId.
   
   You just sync the metadata across cloud, sharing traceid doesn't change the fact, the trace saved in different Clouds. What is the point of this?
   
   BTW, what do you want the SkyWalking community to take part in? I just read the contents, all are about what you did. I assume what you did, defintely makes sense to you. 
   Do you intend to share your change? Or something else?

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services