-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support mapping of ClientService to an exposed list of attributes #36503
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
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
The text was updated successfully, but these errors were encountered: