The service name of the application created by shadow service controller is the same as the source service， so it cannot be clearly identified on the topology graph. In the topology diagram, we can only distinguish whether the shadow service is running normally through the different middleware used by the service.
The expected result is that when the new ShadowService is created and traffic is generated, the corresponding nodes can also be seen on the topology graph like this.
For this purpose, I think we need:
- The shadow service controller injects the serviceName environment variable when generating the service deployment.
- JavaAgent modifies the tracing log based on the env value of the serviceName.
The service name of the application created by shadow service controller is the same as the source service， so it cannot be clearly identified on the topology graph. In the topology diagram, we can only distinguish whether the shadow service is running normally through the different middleware used by the service.
The expected result is that when the new ShadowService is created and traffic is generated, the corresponding nodes can also be seen on the topology graph like this.
For this purpose, I think we need: