Web API log info missing out of the box

[Depechie]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

When running the default starter template, drilling down into a trace, the API will show no logs. Only the frontend will have logs available.

Expected Behavior

I would expect that when the frontend calls the weather info from the API, this should also result in log info of that GET call in the API logs.

Steps To Reproduce

Run dotnet new aspire-starter --output AspireSample
Start the AppHost
Open the frontend and select the weather tab
After the weather info is shown navigate to the traces tab in the aspire dashboard
Drill down to the API logs of the given trace, it will show no structured logs found

Exceptions (if any)

No response

.NET Version info

.NET SDK:
 Version:           9.0.100
 Commit:            59db016f11
 Workload version:  9.0.100-manifests.054dcb45
 MSBuild version:   17.12.7+5b8665660

Anything else?

No response

[davidfowl]

Can you show a visual of what you are expecting to see and what is not there? AFAIK there haven't been any changes here.

[Depechie]

Maybe this should be converted to a discussion, rather then being an issue...

So it's because I just noticed the difference between my own demo project that I run for .NET Aspire versus the default starter template, that I wanted to add it to the repo as a remark.
Do note that my demo is running Serilog instead of the build in logger.

But let's compare...
The starter template shows the trace info, web hitting api.

Drilling into the logs, we only get web logs

Now my demo app we see api hitting message bus, hitting worker, hitting other api

If we drill down to logs, we get acknowledgement from all api's in the logs too... what we do not see in the default starter template

[davidfowl]

Sorry I don't understand. Are you saying that there are logs that should be showing up that don't show up or something else?

[Depechie]

So let me try this again... with the Aspire starter, from the trace view, pressing the API span ( the lowest one in yellowish tint )

You get the popup with span details, pressing on view logs of that span alone

Will show nothing for the API log lines for that span within the trace

On my demo on the other hand, the api will put out info of the span within the trace, being that the API got called on the GET endpoint

And to be honest I have no clue why this difference is there and hence my question about it.
Because with the starter there is also a GET being called on the API to retrieve json data.