Handling API Gateway route-paths in traces

[btastic]

Hi,

we are using Aspire for a few weeks now, and generally we are very happy with the experience it provides for us.

My team recently asked me whether it was possible to see the real Url in the traces window, when we are sending requests via our API gateway.

Our API gateway is a "almost" single controller ASP.NET core web API, which has only endpoints for routing and middlewares to check for things we need before sending a request downstream to the requested microservice backend.

Most of the controller methods are annotated like this:
[HttpGet("{subsystem}/{**path}")]

subsystem is the requested microservice, the name gets resolved during runtime to the service host name, and the path is appended to it. We are then building a http-request using the provided information and sending that request downstream.

When looking at requests that go, for example to our customer-service, we only see this in the traces dashboard:

But we would rather see the true path that was used, like it shows when a microservice is contacted directly, without the use of the API Gateway.

Is that possible to do somehow?

Thanks!

[davidfowl]

AFAIK this is what the gateway is tracing. There's nothing that aspire can do. IF you are using YARP then file an issue here https://github.com/dotnet/yarp/.

[btastic]

Hey David,

thanks. That makes sense. I just disabled the tracing for our gateway and it is much better now. Thank you!