ASP.NET Core traces may not be captured in SaaS clusters with a certain OA version

We are currently investigating an issue in which some ASP.NET Core PurePaths might not be captured for SaaS clusters in version 1.287 with OneAgent equal or higher than 1.273.

We will continue to provide updates here as we troubleshoot this issue.

#Scope: SaaS clusters in 1.287 with OA +1.273 are affected.

We have identified the root cause of the issue and are currently working on a short-term fix, that we aim to make available in the next hours.

We will continue to provide updates as soon as we have them.

Thank you for your patience.

We continue to work on a fix for this issue and we'll announce it once it is applied to all SaaS clusters.

In the meantime, impacted customers can also workaround the issue by manually disabling the ".NET AspNetCore SingleMiddleware [Opt-In]" feature, in Settings > Preferences > OneAgent features, on the affected process groups or tenant-wide, and then restarting the affected processes. This is an opt-in feature that does not need to be enabled by default, and disabling it should allow the .NET Core services to begin reporting correctly once again.

A fix (1.287.119.20240322-155025) for this issue has been released and is being deployed. We will announce once all SaaS clusters have completed being updated.

Please note affected customers will need to restart their .NET Core applications once their tenant has been updated.