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/11/06 07:31:27 UTC

[GitHub] [skywalking] webb2019 opened a new issue #3792: The topology does not agree with the actual situation

webb2019 opened a new issue #3792: The topology does not agree with the actual situation
URL: https://github.com/apache/skywalking/issues/3792
 
 
   Please answer these questions before submitting your issue.
   
   - Why do you submit this issue?
   - [ ] Question or discussion
   - [x] Bug
   - [ ] Requirement
   - [ ] Feature or performance improvement
   
   ___
   ### Question
   Our experimental deployment environment is as follows:
   ![image](https://user-images.githubusercontent.com/52440226/68276681-770bf700-00a8-11ea-85e9-31d4a487b48e.png)
   
   After running for some time, we looked at the topology of skywalking and found that it was not consistent:
   ![image](https://user-images.githubusercontent.com/52440226/68276508-25fc0300-00a8-11ea-992e-735e9b12651d.png)
   I checked the agent.config 's agent.service_name of each service without any problem.
   
   The skywalking topoloy display  that "chegndu-t1-api"  call "foshan-s1-wms", "jiahu-s1-wms" ,  ... etc .  In fact, "chegndu-t1-api"  can only call  "chegndu-t1-wms".  "chegndu-t1-api" can't call other services.
   
   It's strange that  I  just find skywalking traces of   "chegndu-t1-api" call  "chegndu-t1-wms" ,not others.
   
   I think skywalking trace is right ,  topoloy maybe wrong in some situations. 
   
   
    
   
   
   
   

----------------------------------------------------------------
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