Is Observability still relevant if Aspire has built-in distributed logs?

[stijnmoreels]

The Aspire provides connected transactional logging for requests/dependencies. I'm wondering if the things for built-in Microsoft components is still relevant for us to have in the library.

https://learn.microsoft.com/en-us/dotnet/core/diagnostics/observability-with-otel

[fgheysels]

As far as I know, Aspire makes it easy to create distributed applications and it offers a .NET 'wrapper' above the cloud-native tooling. (At least, that's what I understood about it; I haven't played with it yet).
From the documentation, I read that Aspire makes it easy to provide observability for distruted applications.

As far as I can see, I think Arcus Observability is still relevant, as it offers functionality for easily writing custom events / metrics / .... But I think I 'll only be able to really give a useful answer once I've played with Aspire.

But maybe @gverstraete has an interesting opinion as well, as he has already more experience with Aspire then I do.

[gverstraete]

Aspire seems to work with OpenTelemetry & the use of a different methodology for Metrics & Events. Sent you a sample last friday :).

I think the real question is: should we align to use the OpenTelemetry methodology instead of the AppInsights SDK directly...