Is your feature request related to a problem? Please describe.
Currently when enabling virtual nodes in servicegraphs, we can provide a list of attributes that allow a client span to create a virtual server node based on the attribute present. This request is to provide support for similar action for server spans, i.e., a new configuration option that allows us to provide a list of attributes that allow a server span to create a virtual client node based on the attribute present.
This option does not currently exist, so any server span that does not have a corresponding client span gets assigned a generic user node as client, which hides how services are called.
Server spans that have the attribute of peer.service (or client.address) will list the peer.service (or client.address) in the client node in the node graph, instead of the generic user.
Component(s)
connector/servicegraph
Is your feature request related to a problem? Please describe.
Currently when enabling virtual nodes in servicegraphs, we can provide a list of attributes that allow a client span to create a virtual server node based on the attribute present. This request is to provide support for similar action for server spans, i.e., a new configuration option that allows us to provide a list of attributes that allow a server span to create a virtual client node based on the attribute present.
This option does not currently exist, so any server span that does not have a corresponding client span gets assigned a generic
user
node as client, which hides how services are called.Describe the solution you'd like
With a config like the below:
Server spans that have the attribute of
peer.service
(orclient.address
) will list thepeer.service
(orclient.address
) in the client node in the node graph, instead of the genericuser
.Describe alternatives you've considered
No response
Additional context
No response