Lukasz Podolak

+1. I realised that by having these 2 spans, we are not able to filter traces by values that are present in both spans. For example, the aspnet_core.request span contains...

What solved the problem in my case is (as @fjmorel suggested) to keep the reference to the root span (aspnet_core.request) and use it later in the MVC pipeline. My only...

I have also mixed feelings about these duplicated spans. I think they are the source of problems that I observe: I discovered that it matters at which stage of processing...

Here's a screenshot with our custom metadata landing on the 2nd span and so - being not searchable anymore. 

Upgrading Octopus Deploy to latest version (2024.01) helped in my case!