Service graph server/client kind?

[fede843]

Hi, we are using OTEL over NGINX.
Before we used a third party module that created several spans, the root one kind server, and the child ones client. It was all good when it came to the server graph.
Then we migrated to the official NGINX OTEL implementation. It works fine, but we detected service graph got screwed. Investigating further the new implementation uses only one span, at the root level, kind server, and then jumps to the next service. And that important link is not created, since the origin is kind server.
Is there any workaround to this?