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 2022/12/16 08:57:12 UTC

[GitHub] [skywalking] wu-sheng commented on pull request #10169: Enhance service topology to support multiple components of a service

wu-sheng commented on PR #10169:
URL: https://github.com/apache/skywalking/pull/10169#issuecomment-1354410330

   The component ID in service and process topology are sharing the same mechanism from the kernel level now. 
   
   After this is merged, I would consider removing the component ID from the instance topology. If you have any concerns, please let me know.
   My idea is, we never show this, and as an `n pods(ServA) * m pods(ServB)` size topology, there is pointless to show the component of each node.
   This would be only a logical level change, I will add a notice to the GraphQL file to declare these cases. And will keep those type/component fields as empty strings only.


-- 
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-unsubscribe@skywalking.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org