[Bug] why the same service has two nodes on the topology

[gaoyanyu]

Search before asking

• I had searched in the issues and found no similar issues.

Apache SkyWalking Component

Python Agent (apache/skywalking-python)

What happened

backgroud:

I use a skywalking-scala plugin in my scala project, and trace id produced in the process 'serviceA(scala) -> serviceB(python)' is like this:

trace id produced in the process 'serviceB(python) -> serviceC(python)' is like this:

And the topolygy is like this:

my question is why serviceB has two nodes on the topology?

What you expected to happen

A service node has one and only one node in the topology graph.

How to reproduce

Service A calls service B as follows:

50051 represents the grpc port of serviceB.
serviceB registers to skywalking like this:
from skywalking import agent as sw_agent from skywalking import config as sw_config sw_config.init( agent_collector_backend_services="skywalking.observability.svc:11800", agent_name="edu-parser-main-api-grpc-staging", agent_instance_name="<pod_name>", agent_trace_ignore_path="/metrics/,/health", agent_log_reporter_level="INFO", ) sw_agent.start()

Anything else

No response

Are you willing to submit a pull request to fix on your own?

• Yes I am willing to submit a pull request on my own!

Code of Conduct

• I agree to follow this project's Code of Conduct

[wu-sheng]

This is not our plugin. We don't take responsibility for others.

[wu-sheng]

If that plugin reject wrong info inti header, or report data logically wrong.
The topo could be broken.
So, ask the one writing the plugin

[gaoyanyu]

If that plugin reject wrong info inti header, or report data logically wrong. The topo could be broken. So, ask the one writing the plugin

OK，thanks